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 61899 - UnknownHostException messages in ide.log during autoupdate
Summary: UnknownHostException messages in ide.log during autoupdate
Status: CLOSED DUPLICATE of bug 60529
Alias: None
Product: platform
Classification: Unclassified
Component: Autoupdate (show other bugs)
Version: 4.x
Hardware: All All
: P4 blocker (vote)
Assignee: Jiri Rechtacek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-07 19:19 UTC by Unknown
Modified: 2007-04-01 03:19 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Unknown 2005-08-07 19:19:21 UTC
An exception stacktrace is written to ide.log while connecting to uc and there
are connection errors (like proxy not being set, or server is down etc).
Since the ide correctly identifies the error and informs the user to verify the
proxy etc via a dialog box, the stacktrace itself should not appear in ide.log.

Annotation: URL: http://...
java.net.UnknownHostException: www.netbeans.org
	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:153)
	at java.net.Socket.connect(Socket.java:452)
	at java.net.Socket.connect(Socket.java:402)
	at sun.net.NetworkClient.doConnect(NetworkClient.java:139)
	at sun.net.www.http.HttpClient.openServer(HttpClient.java:402)
	at sun.net.www.http.HttpClient.openServer(HttpClient.java:618)
	at sun.net.www.http.HttpClient.<init>(HttpClient.java:306)
	at sun.net.www.http.HttpClient.<init>(HttpClient.java:267)
	at sun.net.www.http.HttpClient.New(HttpClient.java:339)
	at sun.net.www.http.HttpClient.New(HttpClient.java:320)
	at sun.net.www.http.HttpClient.New(HttpClient.java:315)
	at
sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:521)
	at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:498)
	at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:626)
	at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
	at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source)
	at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
	at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
	at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
	at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
	at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
	at org.openide.xml.XMLUtil.parse(XMLUtil.java:283)
[catch] at
org.netbeans.modules.autoupdate.XMLUpdates.parseDocument(XMLUpdates.java:323)
	at org.netbeans.modules.autoupdate.XMLUpdates.access$500(XMLUpdates.java:38)
	at org.netbeans.modules.autoupdate.XMLUpdates$2.run(XMLUpdates.java:186)
	at org.openide.util.Task.run(Task.java:136)
	at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:330)
	at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:686)
Comment 1 Unknown 2005-08-08 18:36:58 UTC
This looks like a duplicate of
http://www.netbeans.org/issues/show_bug.cgi?id=60529. 60529 itself is closed as
will-not-fix because "Informational exception is allowed to be written into
ide.log." But when the issue has been identified and the user correctly
informed, the stacktraces in ide.log themselves do not serve any purpose and
possibly should not be written in such cases. 
The issue also seems to be related to
http://www.netbeans.org/issues/show_bug.cgi?id=51421.
Comment 2 Jaromir Uhrik 2005-10-18 10:09:39 UTC
This issue is duplicate of #60529 - Jirka explained there why it is printed into
the console and I am now sure it is correct.
In issue #51421 was exception printed always (no matter whether successful
connection or not). So this one is not related to #51421.

*** This issue has been marked as a duplicate of 60529 ***
Comment 3 Karthikeyan Rajeswaran 2007-04-01 03:19:29 UTC
> But when the issue has been identified and the user correctly
> informed, the stacktraces in ide.log themselves do not serve any purpose and
> possibly should not be written in such cases. 

I now realise that my above assertion is not correct and jirka is right in
saying "Informational exception is allowed to be written into ide.log" ; and the
execeptions should be written into log, as they provide more info useful for
debugging.