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 217982 - Not possible to report exception: org.xml.sax.SAXParseException; lineNumber: 2; columnNumber: 2; The markup in the document following the root element must be well-formed.
Summary: Not possible to report exception: org.xml.sax.SAXParseException; lineNumber: ...
Status: VERIFIED DUPLICATE of bug 167163
Alias: None
Product: ide
Classification: Unclassified
Component: Exceptions Reporter (show other bugs)
Version: 7.3
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: Tomas Danek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-07 10:07 UTC by Jiri Skrivanek
Modified: 2013-07-10 10:41 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Stack trace. (1.01 KB, text/plain)
2012-09-07 10:07 UTC, Jiri Skrivanek
Details
IDE log. (70.74 KB, text/plain)
2012-09-07 10:09 UTC, Jiri Skrivanek
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Skrivanek 2012-09-07 10:07:18 UTC
Created attachment 124018 [details]
Stack trace.

It is not possible to report exception (see stack trace). My steps:

- start to create new "Java Web|Web Application" project
- click Add... to add a new server and it throws exception
- click Review and Report Problem but it throws attached exception

Product Version: NetBeans IDE Dev (Build 201209070001)
Java: 1.7.0_07; Java HotSpot(TM) 64-Bit Server VM 23.3-b01
System: Windows 7 version 6.1 running on amd64; Cp1250; en_US (nb)
Comment 1 Jiri Skrivanek 2012-09-07 10:09:28 UTC
Created attachment 124020 [details]
IDE log.
Comment 2 Tomas Danek 2012-09-12 12:32:29 UTC
not reproducible; 

[Fatal Error] :2:2: The markup in the document following the root element must be well-formed.
doShow reading from: http://netbeans.org/nonav/uigestures/error2.html

shows that it was not possible to connect to statistics.nb.org server, network issue?! TODO: better handle such case.
Comment 3 Marian Mirilovic 2013-07-10 10:07:22 UTC
will be also covered by implementation of issue 167163

*** This bug has been marked as a duplicate of bug 167163 ***