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

Bug 367440

Summary:	ConcurrentModificationException during "Initializing Java Tooling"
Product:	[Eclipse Project] JDT	Reporter:	Mauro Molinari <mauromol>
Component:	Core	Assignee:	JDT-Core-Inbox <jdt-core-inbox>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P3	CC:	bugzilla-eclipse, jarthana, jtk499, loskutov, satyam.kandula, stephan.herrmann
Version:	3.7.1
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Mauro Molinari

2011-12-22 11:26:32 EST

Sometimes when Eclipse starts I have a ConcurrentModificationException during  "Initializing Java Tooling".

Today it happened with the following stack trace:

eclipse.buildId=M20110909-1335
java.version=1.6.0_26
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=it_IT
Command-line arguments:  -os win32 -ws win32 -arch x86_64 -debug -consoleLog -data d:\workspace37-Trunk

Error
Thu Dec 22 17:15:23 CET 2011
An internal error occurred during: "Initializing Java Tooling".

java.util.ConcurrentModificationException
	at java.util.HashMap$HashIterator.nextEntry(Unknown Source)
	at java.util.HashMap$EntryIterator.next(Unknown Source)
	at java.util.HashMap$EntryIterator.next(Unknown Source)
	at org.eclipse.jdt.internal.core.JavaModelManager$9.run(JavaModelManager.java:2796)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344)
	at org.eclipse.jdt.internal.core.JavaModelManager.initializeAllContainers(JavaModelManager.java:2816)
	at org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1873)
	at org.eclipse.jdt.core.JavaCore.initializeAfterLoad(JavaCore.java:3556)
	at org.eclipse.jdt.internal.ui.InitializeAfterLoadJob$RealJob.run(InitializeAfterLoadJob.java:36)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Comment 1 Jay Arthanareeswaran

2011-12-22 11:33:16 EST

This is fixed in 3.8 via bug 351498. Please try one of the recent 3.8 builds.

*** This bug has been marked as a duplicate of bug 351498 ***

Comment 2 Mauro Molinari

2011-12-22 11:35:57 EST

Are you sure bug 351498 is the same?
Its stack trace is totally different and its target milestone is 3.7.1. However, I'm actually seeing my exception in 3.7.1.

Comment 3 Jay Arthanareeswaran

2011-12-22 12:20:12 EST

Satyam, looks like this one is yet to be released in 3.7.x, doesn't it?

Comment 4 Stephan Herrmann

2011-12-22 15:39:10 EST

(In reply to comment #3)
> Satyam, looks like this one is yet to be released in 3.7.x, doesn't it?

Bug 351498 was released into the BETA_JAVA7 branch, which then
become 3.7.1, right?

Comment 5 Jay Arthanareeswaran

2011-12-22 22:31:44 EST

(In reply to comment #4)
> (In reply to comment #3)
> > Satyam, looks like this one is yet to be released in 3.7.x, doesn't it?
> 
> Bug 351498 was released into the BETA_JAVA7 branch, which then
> become 3.7.1, right?

Sorry, I didn't notice that.
Yes, it should have been fixed in 3.7.1.

Comment 6 Satyam Kandula

2011-12-23 00:22:04 EST

The problem is different. Hence, reopening.

Comment 7 Andrey Loskutov

2018-03-11 18:27:21 EDT


*** This bug has been marked as a duplicate of bug 327717 ***