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 167745

Summary: A java.lang.ExceptionInInitializerError exception has occured
Product: platform Reporter: plisek <plisek>
Component: Module SystemAssignee: Jesse Glick <jglick>
Status: RESOLVED FIXED    
Severity: blocker CC: aaronfouts
Priority: P3    
Version: 6.x   
Hardware: All   
OS: Windows Vista   
Issue Type: DEFECT Exception Reporter:
Bug Depends on:    
Bug Blocks: 164580    
Attachments: Requested content of log directory

Description plisek 2009-06-28 05:28:08 UTC
On starting NetBeans, the message "A java.lang.ExceptionInInitializerError exception has occured" is diplayed.
Reinstalation of NetBeans does not resolve the problem.
Comment 1 plisek 2009-06-28 05:30:29 UTC
Created attachment 84082 [details]
Requested content of log directory
Comment 2 Milan Kubec 2009-06-29 09:42:41 UTC
Please evaluate. Thanks.
Comment 3 Jesse Glick 2009-06-29 15:08:55 UTC
I think your user directory is corrupted; other exceptions in your log file indicate other corruption in your user
directory. Rather than reinstall NetBeans, just delete C:\Users\děda\.netbeans\6.5 (make a backup first). Some file
under config\Preferences\**\*.properties has an invalid Unicode escape in it, for whatever reason (the IDE itself should
never be writing invalid escapes).

I can make the storage of preference more robust against such errors, but you would probably still need a fresh user dir
since your current one is likely trashed. core-main #ee701f2c201d
Comment 4 Quality Engineering 2009-06-30 05:43:45 UTC
Integrated into 'main-golden', will be available in build *200906300200* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main-golden/rev/ee701f2c201d
User: Jesse Glick <jglick@netbeans.org>
Log: #167745: recover from broken config/Preferences/**/*.properties files.
Comment 5 Jesse Glick 2009-07-10 17:17:24 UTC
Root cause seems to be described in issue #164580. The fix in this issue is probably better, but they can coexist, and
the fix there has been verified.
Comment 6 Jesse Glick 2009-11-11 10:24:07 UTC
*** Bug 157695 has been marked as a duplicate of this bug. ***