Cannot start jbosstools 4.4.2 with Neon.1

[jskovjyskebankdk]

We just tried updating from 4.4.1 to 4.4.2 in Neon.1 on Windows 7.

Eclipse hung on two of three workspaces/machines we tested on, and we had to revert back to 4.4.1.

Lots of log output as below.

The workspace where Eclipse did come up was simpler than the others and had no active deployments to the installed runtimes.

I am willing to test stuff if you need more input.

Thanks,

Jesper

!ENTRY org.eclipse.osgi 2 0 2016-12-12 13:04:49.322

!MESSAGE While loading class "org.jboss.ide.eclipse.as.core.server.internal.v7.JBoss7Server", thread "Thread[Worker-6,5,main]" timed out waiting (5001ms) for thread "Thread[Worker-2,5,main]" to finish starting bundle "org.jboss.ide.eclipse.as.core_3.2.2.v20161121-2100 [1034]". To avoid deadlock, thread "Thread[Worker-6,5,main]" is proceeding but "org.jboss.ide.eclipse.as.core.server.internal.v7.JBoss7Server" may not be fully initialized.

!STACK 0

org.osgi.framework.BundleException: Unable to acquire the state change lock for the module: osgi.identity; type="osgi.bundle"; version:Version="3.2.2.v20161121-2100"; osgi.identity="org.jboss.ide.eclipse.as.core"; singleton:="true" [id=1034] STARTED [STARTED]

    at org.eclipse.osgi.container.Module.lockStateChange(Module.java:337)

    at org.eclipse.osgi.container.Module.start(Module.java:401)

    at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:470)

    at org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)

    at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:529)

    at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:325)

    at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:345)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:423)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364)

    at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)

    at java.lang.ClassLoader.loadClass(Unknown Source)

    at org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:564)

    at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:174)

    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.wst.server.core.internal.ServerType.createServerDelegate(ServerType.java:91)

    at org.eclipse.wst.server.core.internal.Server.getDelegate(Server.java:506)

    at org.eclipse.wst.server.core.internal.Server.loadAdapter(Server.java:1612)

    at org.jboss.ide.eclipse.as.wtp.core.server.behavior.AbstractSubsystemController.getControllableBehavior(AbstractSubsystemController.java:54)

    at org.jboss.ide.eclipse.as.wtp.core.server.behavior.AbstractSubsystemController.findDependencyFromBehavior(AbstractSubsystemController.java:74)

    at org.jboss.tools.as.core.server.controllable.subsystems.internal.StandardFileSystemPublishController.getDeploymentOptions(StandardFileSystemPublishController.java:181)

    at org.jboss.tools.as.core.server.controllable.subsystems.internal.StandardFileSystemPublishController.validate(StandardFileSystemPublishController.java:214)

    at org.jboss.tools.as.core.server.controllable.subsystems.internal.StandardFileSystemPublishController.canPublish(StandardFileSystemPublishController.java:226)

    at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.canPublish(ControllableServerBehavior.java:300)

    at org.eclipse.wst.server.core.internal.Server.canPublish(Server.java:1218)

    at org.eclipse.wst.server.core.internal.Server.shouldPublish(Server.java:1231)

    at org.eclipse.wst.server.ui.internal.cnf.ServerDecorator.getServerStatusLabel(ServerDecorator.java:139)

    at org.eclipse.wst.server.ui.internal.cnf.ServerDecorator.decorate(ServerDecorator.java:73)

    at org.eclipse.ui.internal.decorators.LightweightDecoratorDefinition.decorate(LightweightDecoratorDefinition.java:260)

    at org.eclipse.ui.internal.decorators.LightweightDecoratorManager$LightweightRunnable.run(LightweightDecoratorManager.java:100)

    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)

    at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.decorate(LightweightDecoratorManager.java:383)

    at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.getDecorations(LightweightDecoratorManager.java:365)

    at org.eclipse.ui.internal.decorators.DecorationScheduler$1.ensureResultCached(DecorationScheduler.java:367)

    at org.eclipse.ui.internal.decorators.DecorationScheduler$1.run(DecorationScheduler.java:327)

    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Caused by: java.util.concurrent.TimeoutException: Timeout after waiting 5 seconds to acquire the lock.

    at org.eclipse.osgi.container.Module.lockStateChange(Module.java:334)

    ... 37 more

Root exception:

java.util.concurrent.TimeoutException: Timeout after waiting 5 seconds to acquire the lock.

    at org.eclipse.osgi.container.Module.lockStateChange(Module.java:334)

    at org.eclipse.osgi.container.Module.start(Module.java:401)

    at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:470)

    at org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)

    at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:529)

    at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:325)

    at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:345)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:423)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364)

    at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)

    at java.lang.ClassLoader.loadClass(Unknown Source)

    at org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:564)

    at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:174)

    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.wst.server.core.internal.ServerType.createServerDelegate(ServerType.java:91)

    at org.eclipse.wst.server.core.internal.Server.getDelegate(Server.java:506)

    at org.eclipse.wst.server.core.internal.Server.loadAdapter(Server.java:1612)

    at org.jboss.ide.eclipse.as.wtp.core.server.behavior.AbstractSubsystemController.getControllableBehavior(AbstractSubsystemController.java:54)

    at org.jboss.ide.eclipse.as.wtp.core.server.behavior.AbstractSubsystemController.findDependencyFromBehavior(AbstractSubsystemController.java:74)

    at org.jboss.tools.as.core.server.controllable.subsystems.internal.StandardFileSystemPublishController.getDeploymentOptions(StandardFileSystemPublishController.java:181)

    at org.jboss.tools.as.core.server.controllable.subsystems.internal.StandardFileSystemPublishController.validate(StandardFileSystemPublishController.java:214)

    at org.jboss.tools.as.core.server.controllable.subsystems.internal.StandardFileSystemPublishController.canPublish(StandardFileSystemPublishController.java:226)

    at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.canPublish(ControllableServerBehavior.java:300)

    at org.eclipse.wst.server.core.internal.Server.canPublish(Server.java:1218)

    at org.eclipse.wst.server.core.internal.Server.shouldPublish(Server.java:1231)

    at org.eclipse.wst.server.ui.internal.cnf.ServerDecorator.getServerStatusLabel(ServerDecorator.java:139)

    at org.eclipse.wst.server.ui.internal.cnf.ServerDecorator.decorate(ServerDecorator.java:73)

    at org.eclipse.ui.internal.decorators.LightweightDecoratorDefinition.decorate(LightweightDecoratorDefinition.java:260)

    at org.eclipse.ui.internal.decorators.LightweightDecoratorManager$LightweightRunnable.run(LightweightDecoratorManager.java:100)

    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)

    at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.decorate(LightweightDecoratorManager.java:383)

    at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.getDecorations(LightweightDecoratorManager.java:365)

    at org.eclipse.ui.internal.decorators.DecorationScheduler$1.ensureResultCached(DecorationScheduler.java:367)

    at org.eclipse.ui.internal.decorators.DecorationScheduler$1.run(DecorationScheduler.java:327)

    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

[nickboldt]

When updating, did you do a COLD restart (shut down Eclipse fully, then start it up with -clean flag) or just a WARM restart (let Eclipse restart when prompted, without releasing memory) ?

Did you also try simply installing JBoss Tools 4.4.2 into Neon.1 directly, rather than doing an update ? That might work better.

By the way, these forums are being decommissioned. For future support, please go here:

• http://stackoverflow.com/questions/tagged/jboss-tools
• http://stackoverflow.com/questions/tagged/jboss-developer-studio

[jskovjyskebankdk]

We always do an offline-install.

FWIW I was not really looking for support. I was trying to report an issue - filing directly in Jira was frowned upon before.

Has this changed, or should I just hope that one of you pick up on questions on stackoverflow?

[nickboldt]

If you have an issue, please report it. I'm not sure who told you it was frowned upon: we're more than happy to get reports from anyone and everyone. Please provide as much detail as possible - your OS, JVM version, what you were doing, steps to reproduce, screenshots / console logs, etc.

Here are a few JIRA links:

• https://issues.jboss.org/browse/JBIDE - for JBoss Tools
• https://issues.jboss.org/browse/JBDS - for Red Hat JBoss Developer Studio
• https://issues.jboss.org/browse/JBTIS - for Red Hat JBoss Developer Studio Integration Stack (or JBoss Tools Integration Stack)
• https://issues.jboss.org/browse/RHDEVDOCS - for documentation, eg., on https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio/

[jskovjyskebankdk]

You might want to review and change this text: HelpBugReport

It is linked to from the bug creation form.

I will open a Jira issue. Thanks.

[nickboldt]

Thanks for the pointer. I've updated that doc with this new header.

Are you sure it is a bug?

If NO, please post a question on StackOverflow, tagged with:

• jboss-tools: http://stackoverflow.com/questions/tagged/jboss-tools
• jboss-developer-studio: http://stackoverflow.com/questions/tagged/jboss-developer-studio
• jboss-wildfly-10: http://stackoverflow.com/questions/tagged/wildfly-10 (see also wildfly)
• jboss-eap-7: http://stackoverflow.com/questions/tagged/jboss-eap-7 (see also jboss-eap-6)
• ... or some other relevant tag

If YES, please report your bug in JIRA:

• https://issues.jboss.org/browse/JBIDE - for JBoss Tools
• https://issues.jboss.org/browse/JBDS - for Red Hat JBoss Developer Studio
• https://issues.jboss.org/browse/JBTIS - for Red Hat JBoss Developer Studio Integration Stack (or JBoss Tools Integration Stack)
• https://issues.jboss.org/browse/RHDEVDOCS - for documentation, eg., on https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio/
• https://issues.jboss.org/browse/WFLY - for WildFly
• https://issues.jboss.org/browse/JBEAP - for JBoss Enterprise Application Server
• ... or some other relevant project

[heruan]

I'm on Neon.2 and I'm experiencing the same issue. Did you solve this? Or did you report the bug on Jira? In that case, can you please provide a link to follow it? Thank you!

[jskovjyskebankdk]

The problem did not appear the day after, so we decided just to push ahead and use it.

For the same reason, I did not report it in Jira; I could not reproduce the next day.

[jskovjyskebankdk]

We got it again this morning.

I found this, and followed the suggestion. Seemed to fix the problem.

Eclipse Community Forums: Newcomers » [SOLVED]error while opening eclipse Luna