This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 239478 - java.io.IOException: Server returned HTTP response code: 502 for URL: http://www.netbeans.org/dtds/module-status-1_0.dtd
Summary: java.io.IOException: Server returned HTTP response code: 502 for URL: http://...
Status: RESOLVED FIXED
Alias: None
Product: apisupport
Classification: Unclassified
Component: Project (show other bugs)
Version: 8.0
Hardware: All All
: P2 normal (vote)
Assignee: Martin Kozeny
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-13 15:31 UTC by Vladimir Voskresensky
Modified: 2013-12-17 11:24 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 206001

Attachments
stacktrace (5.34 KB, text/plain)
2013-12-13 15:31 UTC, Vladimir Voskresensky 		Details
stacktrace (6.39 KB, text/plain)
2013-12-13 16:33 UTC, Vladimir Voskresensky 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Voskresensky 2013-12-13 15:31:07 UTC 
This bug was originally marked as duplicate of bug 175092, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE Dev (Build 20131213-f41da123be36)
VM: Java HotSpot(TM) 64-Bit Server VM, 24.45-b08, Java(TM) SE Runtime Environment, 1.7.0_45-b18
OS: SunOS

User Comments:
vv159170: reopened IDE




Stacktrace: 
java.io.IOException: Server returned HTTP response code: 502 for URL: http://www.netbeans.org/dtds/module-status-1_0.dtd
   at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1626)
   at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:637)
   at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity(XMLEntityManager.java:1290)
   at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startDTDEntity(XMLEntityManager.java:1257)
   at com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.setInputSource(XMLDTDScannerImpl.java:262)
   at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver.dispatch(XMLDocumentScannerImpl.java:1162)
Comment 1 Vladimir Voskresensky 2013-12-13 15:31:09 UTC 
Created attachment 143163 [details]
stacktrace
Comment 2 Antonin Nebuzelsky 2013-12-13 16:08:03 UTC 
Shouldn't apisupport.project use bundled dtd?
Reassigning.
Comment 3 Antonin Nebuzelsky 2013-12-13 16:08:52 UTC 
Vladimir, is this reproducible problem or was it a random one time incident?
Comment 4 Vladimir Voskresensky 2013-12-13 16:33:50 UTC 
Today it is very reproducible. And there is not just one exception dialog, but a lot of them (have a look at my message.log attached to report)
Comment 5 Vladimir Voskresensky 2013-12-13 16:33:52 UTC 
Created attachment 143167 [details]
stacktrace

open ide again
Comment 6 Jiri Rechtacek 2013-12-13 17:07:58 UTC 
IMHO it's unrelated to netbeans code. HTTP return code 502 means: Bad Gateway
The server was acting as a gateway or proxy and received an invalid response from the upstream server. It should be reported against Oracle Network.
Comment 7 Vladimir Voskresensky 2013-12-13 17:18:20 UTC 
It's up to you not to fix, but as a user I would say 30 modal exceptions dialogs is not user friendly. 
If situation is correct, then you should lower priority of logger to not show modal dialogs at all. And please, report exception once.
Comment 8 Vladimir Voskresensky 2013-12-13 17:42:39 UTC 
Please, suppress 10 modal dialogs. Thanks
Comment 9 Vladimir Voskresensky 2013-12-13 17:43:50 UTC 
The dialog is shown also on each file open :-(
Comment 10 Martin Kozeny 2013-12-16 12:14:46 UTC 
From plenty of modal dialogs should prevent Tomas Zezula's fix: https://netbeans.org/bugzilla/show_bug.cgi?id=239449. I'll investigate what actually happens next.
Comment 11 Jiri Rechtacek 2013-12-16 13:28:39 UTC 
(In reply to Vladimir Voskresensky from comment #7)
> It's up to you not to fix, but as a user I would say 30 modal exceptions
> dialogs is not user friendly. 
> If situation is correct, then you should lower priority of logger to not
> show modal dialogs at all. And please, report exception once.

Based on my investigation of apisupport.ant code, the fact IDE asks for http://www.netbeans.org/dtds/module-status-1_0.dtd is a bug. IDE has to resolve this URL as file:// protocol. There is something wrong in the default lookup. Vladimir, could you try it again with latest Dev build and let us know if it's valid still? Thanks
Comment 12 Vladimir Voskresensky 2013-12-16 16:18:39 UTC 
Jiri, today I don't have any issues, but I couldn't check if the issues has gone. I assume for that something with global network settings should happen.
Comment 13 Jiri Rechtacek 2013-12-17 09:28:32 UTC 
(In reply to Vladimir Voskresensky from comment #12)
> Jiri, today I don't have any issues
Are you running on the same build as you opened the issue?

> gone. I assume for that something with global network settings should happen.
As I wrote in previous comment, the IDE should not make any http connection for that case (module-status-1_0.dtd ). If it does it's the root of this problem.
Comment 14 Vladimir Voskresensky 2013-12-17 11:24:35 UTC 
I used new yesterday's daily build. And I don't have issues. Let's assume bug is gone. Thanks!