Bug 461781 - Nullpointerexception at startup
Summary: Nullpointerexception at startup
Status: RESOLVED WORKSFORME
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Framework (show other bugs)
Version: 4.5.0 Mars   Edit
Hardware: PC Windows 7
: P3 blocker (vote)
Target Milestone: ---   Edit
Assignee: equinox.framework-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-10 04:45 EDT by Thomas Elskens CLA
Modified: 2015-03-10 08:53 EDT (History)
2 users (show)

See Also:

Attachments
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 Thomas Elskens CLA 2015-03-10 04:45:42 EDT 
Java Version : 1.8_40 ea

Since the last update of the target runtime (2.0.0.201503100602), my RCP application does not start any longer but throws an nullpointer exception, as follows :

!ENTRY org.eclipse.equinox.app 4 0 2015-03-10 09:40:04.875
!MESSAGE null values not allowed
!STACK 0
java.lang.NullPointerException: null values not allowed
	at org.eclipse.core.internal.registry.ReferenceMap.put(ReferenceMap.java:351)
	at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.getBundle(RegistryStrategyOSGI.java:151)
	at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:166)
	at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
	at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
	at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:191)
	at org.eclipse.equinox.internal.app.AnyThreadAppLauncher.run(AnyThreadAppLauncher.java:26)
	at java.lang.Thread.run(Unknown Source)
Comment 1 Thomas Schindl CLA 2015-03-10 06:03:34 EDT 
I don't think this is something we can do. This looks like Equinox the only idea I have is that you try to clear the OSGi-cache in your run config (Configuration-Tab in your Launch-Config-Dialog)
Comment 2 Thomas Elskens CLA 2015-03-10 06:50:22 EDT 
Clearing the cache indeed solves the problem. 

Thanks a lot!
Comment 3 Thomas Watson CLA 2015-03-10 08:53:57 EDT 
Hi, this is also seen in bug 443761.  I suspect your RCP application is missing the org.eclipse.osgi.compatibility.state compatibility fragment.