An internal error occurred during: "Initializing Java Tooling"

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Critical Critical
  • Resolution: Unresolved
  • Affects Version/s: dev
  • Fix Version/s: 0.9.8
  • Component/s: None
  • Labels:
    None
  • Environment:
    Eclipse 3.4.1

Description

Happens on Eclipse restart with the latest dev build

– Error Details –
Date: Mon Jan 05 10:35:00 EST 2009
Message: An internal error occurred during: "Initializing Java Tooling".

Exception Stack Trace:
java.lang.NullPointerException
at org.maven.ide.eclipse.jdt.internal.MavenClasspathContainerInitializer.initialize(MavenClasspathContainerInitializer.java:42)
at org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:2371)
at org.eclipse.jdt.internal.core.JavaModelManager$13.run(JavaModelManager.java:2301)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at org.eclipse.jdt.internal.core.JavaModelManager.initializeAllContainers(JavaModelManager.java:2317)
at org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1679)
at org.eclipse.jdt.core.JavaCore.initializeAfterLoad(JavaCore.java:3398)
at org.eclipse.jdt.internal.ui.InitializeAfterLoadJob$RealJob.run(InitializeAfterLoadJob.java:35)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Igor Fedorenko added a comment -

Is this the only exception? I get this exception too, but for me it always comes with "timed out waiting (5000ms) for thread" OSGi classloader exception. For me the workaround is to close all java editors and restart eclipse.

Show
Igor Fedorenko added a comment - Is this the only exception? I get this exception too, but for me it always comes with "timed out waiting (5000ms) for thread" OSGi classloader exception. For me the workaround is to close all java editors and restart eclipse.
Hide
Permalink
Eugene Kuleshov added a comment -

Igor, you right, there were warnings before that exception been thrown:

While loading class "org.maven.ide.eclipse.jdt.BuildPathManager", 
thread "Thread[Worker-3,5,main]" timed out waiting (5000ms) 
for thread "Thread[main,6,main]" to finish starting bundle
"reference:file:plugins\org.maven.ide.eclipse.jdt_0.9.7.200812302249.jar [880]". 
To avoid deadlock, thread "Thread[Worker-3,5,main]" is proceeding but
"org.maven.ide.eclipse.jdt.BuildPathManager" may not be fully initialized.

While loading class "org.maven.ide.eclipse.jdt.internal.MavenClasspathContainerInitializer",
thread "Thread[Worker-3,5,main]" timed out waiting (5000ms) 
for thread "Thread[main,6,main]" to finish starting bundle
"reference:file:plugins\org.maven.ide.eclipse.jdt_0.9.7.200812302249.jar [880]". 
To avoid deadlock, thread "Thread[Worker-3,5,main]" is proceeding but
"org.maven.ide.eclipse.jdt.internal.MavenClasspathContainerInitializer" may not be fully initialized.

So, we still need to check why it could take long to load these classes. It should start even with opened Java editors.

Show
Eugene Kuleshov added a comment - Igor, you right, there were warnings before that exception been thrown: 
While loading class "org.maven.ide.eclipse.jdt.BuildPathManager", 
thread "Thread[Worker-3,5,main]" timed out waiting (5000ms) 
for thread "Thread[main,6,main]" to finish starting bundle
"reference:file:plugins\org.maven.ide.eclipse.jdt_0.9.7.200812302249.jar [880]". 
To avoid deadlock, thread "Thread[Worker-3,5,main]" is proceeding but
"org.maven.ide.eclipse.jdt.BuildPathManager" may not be fully initialized.

While loading class "org.maven.ide.eclipse.jdt.internal.MavenClasspathContainerInitializer",
thread "Thread[Worker-3,5,main]" timed out waiting (5000ms) 
for thread "Thread[main,6,main]" to finish starting bundle
"reference:file:plugins\org.maven.ide.eclipse.jdt_0.9.7.200812302249.jar [880]". 
To avoid deadlock, thread "Thread[Worker-3,5,main]" is proceeding but
"org.maven.ide.eclipse.jdt.internal.MavenClasspathContainerInitializer" may not be fully initialized.
So, we still need to check why it could take long to load these classes. It should start even with opened Java editors.
Hide
Permalink
Igor Fedorenko added a comment -

I am almost sure this is a deadlock between java editor reconciler thread and classpath container initialization thread.

Show
Igor Fedorenko added a comment - I am almost sure this is a deadlock between java editor reconciler thread and classpath container initialization thread.
Hide
Permalink
Felipe Carvalho added a comment -

Is there any workaround for this bug, besides removing m2eclipse? It's messing up with Eclipse auto-complete, project explorer and several other functionalities.

Show
Felipe Carvalho added a comment - Is there any workaround for this bug, besides removing m2eclipse? It's messing up with Eclipse auto-complete, project explorer and several other functionalities.
Hide
Permalink
Igor Fedorenko added a comment -

For me, the workaround is to close all editors and restart eclipse.

Show
Igor Fedorenko added a comment - For me, the workaround is to close all editors and restart eclipse.

People

  • Assignee:
    Unassigned
    Reporter:
    Eugene Kuleshov
Vote (7)
Watch (7)

Dates

  • Created:
    Updated: