[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-3818) ConcurrentModificationException in seam validator
Alexey Kazakov (JIRA)
jira-events at lists.jboss.org
Wed Feb 18 06:28:44 EST 2009
[ https://jira.jboss.org/jira/browse/JBIDE-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12453057#action_12453057 ]
Alexey Kazakov commented on JBIDE-3818:
---------------------------------------
I don't like locking resources during seam validation either. It could take a long time.
It seems to be a problem only when we have a few builder processes for a few projects. And we try to validate a project that is being built by his own builder.
We already have tried to fix this problem. The fix doesn't work actally.
>> Isn't this the same problem we have received multiple reports about over time ?
There were a few ConcurrentModificationExceptions in different part of Seam Tools. We fixed some of them. So now we should fix this one too.
This issue seems to be a very old one. It is not reproducible all the time.
I think all collections that Seam model return should be thread-safe.
Even if one validate process (from first project) will have incomplete model then next validaton process (that will start after second project is buit) will have full model and revalidate resources.
So I don't think that incomplete model could be a problem in that case.
> ConcurrentModificationException in seam validator
> -------------------------------------------------
>
> Key: JBIDE-3818
> URL: https://jira.jboss.org/jira/browse/JBIDE-3818
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Seam
> Affects Versions: 3.0.0.GA
> Reporter: Denis Golovin
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 3.0.0.GA
>
>
> java.util.ConcurrentModificationException
> [java] at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793)
> [java] at java.util.HashMap$KeyIterator.next(HashMap.java:828)
> [java] at java.util.Collections$UnmodifiableCollection$1.next(Collections.java:1010)
> [java] at org.jboss.tools.seam.internal.core.validation.SeamCoreValidator.validateAll(SeamCoreValidator.java:198)
> [java] at org.jboss.tools.seam.internal.core.validation.SeamValidatorManager.validateAll(SeamValidatorManager.java:88)
> [java] at org.jboss.tools.seam.internal.core.validation.SeamValidatorManager.validateInJob(SeamValidatorManager.java:68)
> [java] at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78)
> [java] at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list