Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 345811

Summary:	Major problems during headless boot.
Product:	[Eclipse Project] Platform	Reporter:	Thomas Hallgren <thomas>
Component:	Runtime	Assignee:	platform-runtime-inbox <platform-runtime-inbox>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	major
Priority:	P3	CC:	henrik.lindberg, jeffmcaffer, Kenn.Hussey, tjwatson, yevshif
Version:	3.7
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:	stalebug

Description Thomas Hallgren

2011-05-14 11:18:34 EDT

Buckminster uses the simpleconfigurator and there's no specific magic to how it's configured. Our headless product booted without problems with the 3.7M6 platform. When built with the 3.7RC1 however, we run into some major problems.

The first problem seems to be related to the org.eclipse.core.contenttype bundle not being activated in time. I get the following exception:

Caused by: java.lang.NullPointerException
	at org.eclipse.core.internal.resources.CharsetDeltaJob.startup(CharsetDeltaJob.java:187)
	at org.eclipse.core.internal.resources.CharsetManager.startup(CharsetManager.java:491)
	at org.eclipse.core.internal.resources.Workspace.startup(Workspace.java:2511)
	at org.eclipse.core.internal.resources.Workspace.open(Workspace.java:2251)
	at org.eclipse.core.resources.ResourcesPlugin.start(ResourcesPlugin.java:439)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
	at java.security.AccessController.doPrivileged(Native Method)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)

AFAICS, the exception indicates that there's no service registered for the IContentTypeManager so I tweaked the bundles.info file to force a start of the contenttype bundle and that got me further. Now I get this exception instead:

java.lang.NullPointerException
	at org.eclipse.core.internal.registry.BufferedRandomInputStream.seek(BufferedRandomInputStream.java:130)
	at org.eclipse.core.internal.registry.TableReader.goToInputFile(TableReader.java:368)
	at org.eclipse.core.internal.registry.TableReader.loadExtensionPoint(TableReader.java:338)
	at org.eclipse.core.internal.registry.TableReader.loadExtensionPointTree(TableReader.java:309)
	at org.eclipse.core.internal.registry.RegistryObjectManager.load(RegistryObjectManager.java:421)
	at org.eclipse.core.internal.registry.RegistryObjectManager.basicGetObject(RegistryObjectManager.java:270)
	at org.eclipse.core.internal.registry.RegistryObjectManager.getObject(RegistryObjectManager.java:262)
	at org.eclipse.core.internal.registry.BaseExtensionPointHandle.getExtensionPoint(BaseExtensionPointHandle.java:106)
	at org.eclipse.core.internal.registry.BaseExtensionPointHandle.getConfigurationElements(BaseExtensionPointHandle.java:66)
	at org.eclipse.core.internal.registry.ExtensionRegistry.getConfigurationElementsFor(ExtensionRegistry.java:302)
	at org.eclipse.core.internal.registry.ExtensionRegistry.getConfigurationElementsFor(ExtensionRegistry.java:290)
	at org.eclipse.buckminster.core.CorePlugin$2.run(CorePlugin.java:544)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

My guess is that this exception somehow stems from that the reader is accessed after it's been closed. I can't see any other reason for the NPE.

I'm marking this as a blocker because it renders our headless product completely unusable.

Comment 1 Thomas Watson

2011-05-16 08:31:08 EDT

Could you provide a testcase to reproduce?  It appears the platform has been shutdown.  Are there no other errors in the log?

Comment 2 Thomas Hallgren

2011-05-16 08:39:21 EDT

It seems to be intermittent. AFAIK, I haven't changed my setup but now I'm no longer able to reproduce the error. I'll keep testing and provide more info.

Comment 3 Eclipse Genie

2018-09-30 15:48:40 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.