Menu
▾
▴
#323 An internal error occurred / ConcurrentModificationException
java.util.ConcurrentModificationException
at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:3
72)
at java.util.AbstractList$Itr.next(AbstractList.java:343)
at com.puppycrawl.tools.checkstyle.Checker.fireErrors(Checker.java:512)
at com.puppycrawl.tools.checkstyle.Checker.process(Checker.java:279)
at net.sf.eclipsecs.core.builder.Auditor.runAudit(Auditor.java:157)
at net.sf.eclipsecs.core.builder.CheckstyleBuilder.handleBuildSelection(
CheckstyleBuilder.java:287)
at net.sf.eclipsecs.core.jobs.RunCheckstyleOnFilesJob.runInWorkspace(Run
CheckstyleOnFilesJob.java:96)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(Internal
WorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Please file this over at the Checkstyle core project:
https://sourceforge.net/tracker/?group_id=29721
The checkstyle team has a different opinion on this:
The Checkstyle core engine is single threaded, and should not be called
concurrently by multiple threads. This is inherent in the architecture of
Checkstyle.
It seems from the stack trace that the Eclipse Checkstyle plug-in is
breaking this rule, which implies that it is a bug with the plug-in.
Suggest raising a defect with the plug-in project.
https://sourceforge.net/tracker/?func=detail&atid=397078&aid=3206625&group_id=29721
Thx, reopened - need to investigate further.
Note:
This bug is still present in 5.4.1.
It's occurring every time on the startup of eclipse
on every developer machine.
Is there any plan to fix this issue?
Honestly, I could not even reproduce it once, I am myself using the plugin for my daily work.
Also I am not aware that Eclipse project builders can be invoked concurrently.
On which platform (OS, Eclipse version) do you experience this?
This is strage - here it's totally reproducible within our project.
We are using Windows 7 and Windows XP, and Eclipse 3.6.2.
Note: A ConcurrentModificationException does not necessarily require that there is more than one thread involved.
Could you buiild a small sample workspace which is exhibiting this problem on a clean Eclipse install?
Any news on it? I have the same problem.
A workaround is to close all open files before you close Eclipse. If you have more as 20 files open the error is guaranty. It look like that Eclipse check all open files on starting in different threads.
Ah, finally a good hint where to start looking. With that piece of information I think I can devise a fix soon.
Thanks!
Fixed (finally) in CVS.