[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-1333) Still seeing ConcurrentExceptions in error logs :(

[Viacheslav Kabanovich (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBIDE-1333?page=all ]

Viacheslav Kabanovich resolved JBIDE-1333.
------------------------------------------

    Resolution: Done

Synchronization added for working with set of variables.

> Still seeing ConcurrentExceptions in error logs :(
> --------------------------------------------------
>
>                 Key: JBIDE-1333
>                 URL: http://jira.jboss.com/jira/browse/JBIDE-1333
>             Project: JBoss Tools
>          Issue Type: Bug
>          Components: Seam
>    Affects Versions: 2.0.0.CR1
>            Reporter: Max Andersen
>         Assigned To: Viacheslav Kabanovich
>            Priority: Critical
>             Fix For: 2.0.0.GA
>
>
> From error logs in JBIDE-1329: user is still getting concurrentmodification exceptions in CR1! - is the seam model not threadsafe or ?
> !ENTRY org.eclipse.wst.validation 4 0 2007-11-19 14:51:29.479
> !MESSAGE 
> *** ERROR ***: Mon Nov 19 14:51:29 EET 2007    java.util.ConcurrentModificationException
>     	at java.util.HashMap$HashIterator.nextEntry(Unknown Source)
>     	at java.util.HashMap$KeyIterator.next(Unknown Source)
>     	at org.jboss.tools.seam.internal.core.SeamProject.getVariables(SeamProject.java:992)
>     	at org.jboss.tools.seam.internal.core.el.SeamExpressionResolver.internalResolveVariables(SeamExpressionResolver.java:65)
>     	at org.jboss.tools.seam.internal.core.el.SeamExpressionResolver.resolveVariables(SeamExpressionResolver.java:53)
>     	at org.jboss.tools.seam.internal.core.el.SeamELCompletionEngine.resolveVariables(SeamELCompletionEngine.java:645)
>     	at org.jboss.tools.seam.internal.core.el.SeamELCompletionEngine.resolveSeamELOperand(SeamELCompletionEngine.java:390)
>     	at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validateElOperand(SeamELValidator.java:277)
>     	at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validateEl(SeamELValidator.java:256)
>     	at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validateString(SeamELValidator.java:245)
>     	at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validateNodeContent(SeamELValidator.java:210)
>     	at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validateDom(SeamELValidator.java:181)
>     	at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validateFile(SeamELValidator.java:138)
>     	at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validateAll(SeamELValidator.java:114)
>     	at org.jboss.tools.seam.internal.core.validation.SeamValidatorManager.validateAll(SeamValidatorManager.java:84)
>     	at org.jboss.tools.seam.internal.core.validation.SeamValidatorManager.validateInJob(SeamValidatorManager.java:64)
>     	at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:75)
>     	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: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira