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 217790 - NumberFormatException: empty String
Summary: NumberFormatException: empty String
Status: RESOLVED INCOMPLETE
Alias: None
Product: connecteddeveloper
Classification: Unclassified
Component: Bugzilla (show other bugs)
Version: 7.2
Hardware: All All
: P3 normal (vote)
Assignee: Tomas Stupka
URL:
Keywords:
: 220040 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-09-04 10:20 UTC by Stepan Zebra
Modified: 2012-10-25 16:15 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 192095

Attachments
stacktrace (4.53 KB, text/plain)
2012-09-04 10:20 UTC, Stepan Zebra 		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 Stepan Zebra 2012-09-04 10:20:33 UTC 
Build: NetBeans IDE 7.2 (Build 201207171143)
VM: Java HotSpot(TM) 64-Bit Server VM, 23.2-b09, Java(TM) SE Runtime Environment, 1.7.0_06-b24
OS: Windows 7

User Comments:
stezeb: loading issues after login to java.net




Stacktrace: 
java.lang.NumberFormatException: empty String
   at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1011)
   at java.lang.Double.parseDouble(Double.java:540)
   at java.text.DigitList.getDouble(DigitList.java:168)
   at java.text.DecimalFormat.parse(DecimalFormat.java:1321)
   at java.text.SimpleDateFormat.subParse(SimpleDateFormat.java:1793)
   at java.text.SimpleDateFormat.parse(SimpleDateFormat.java:1455)
Comment 1 Stepan Zebra 2012-09-04 10:20:36 UTC 
Created attachment 123863 [details]
stacktrace
Comment 2 Tomas Stupka 2012-10-25 15:58:55 UTC 
*** Bug 220040 has been marked as a duplicate of this bug. ***
Comment 3 Tomas Stupka 2012-10-25 16:15:04 UTC 
don't know how to reproduce. 
added more logging info in core-main #985e68fd1c82, we have to wait until somebody reports with a build containing that change.

or somebody please provided a reproducible scenario - e.g. a java.net issue which happens to produce the reported exception.