[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-2090) ConcurrentModificationException occurs during the Seam validation

Victor Rubezhny (JIRA) jira-events at lists.jboss.org
Tue Apr 22 12:27:44 EDT 2008


    [ http://jira.jboss.com/jira/browse/JBIDE-2090?page=comments#action_12410062 ] 
            
Victor Rubezhny commented on JBIDE-2090:
----------------------------------------

Snjezana, 

One more question: How do you "edit files" while the Seam Validation is working? 
(I mean, what do you type in? Are you using the Content Assistant?) 

Will the deadlock occure even if you aren't using the content assistant at all. By typing just a letters, but not "#{" combinations (which start the Content Assistant).

I see the deadlocks in my environment, but I cannot dump a stacktrace like you do to see what thread is deadlocked and where it happened (Win2k + eclipse). Even when I pause execution in the debugger it shows me just one element in the stack (Object.wait()).

Also I see deadlocks even if I do not use the Content Assistant.... This may mean that the initial Issue is not a reason for these deadlocks and probably another issue is to be open.

If you would like to repeat the testing make your environment up-to-date first.

Thanks again.



> ConcurrentModificationException occurs during the Seam validation
> -----------------------------------------------------------------
>
>                 Key: JBIDE-2090
>                 URL: http://jira.jboss.com/jira/browse/JBIDE-2090
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Seam
>    Affects Versions: 2.1.0.beta1
>         Environment: I got the exception a few times on Linux, but I am not sure if this is a Linux specific issue
>            Reporter: Snjezana Peco
>         Assigned To: Victor Rubezhny
>            Priority: Critical
>             Fix For: 2.1
>
>         Attachments: s1.txt, s2.txt, StringIndexOutOfBoundsException.txt
>
>
> Sometimes when executing the Seam validation, I get ConcurrentModificationException.
> Steps to reproduce:
> - create a large Seam project (as described in http://jira.jboss.com/jira/browse/JBIDE-1105#action_12394448 , for instance)
> - open a few files in the VPE editor 
> - select the WebContent directory and choose Source>Format
> - edit  files during the Seam validation
> Stack trace:
> java.util.ConcurrentModificationException
>         at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372)
>         at java.util.AbstractList$Itr.next(AbstractList.java:343)
>         at org.jboss.tools.common.model.util.TypeInfoCollector.getProperties(TypeInfoCollector.java:843)
>         at org.jboss.tools.common.model.util.TypeInfoCollector.getPropertyPresentations(TypeInfoCollector.java:883)
>         at org.jboss.tools.seam.internal.core.el.SeamELCompletionEngine.resolveSeamELOperand(SeamELCompletionEngine.java:620)
>         at org.jboss.tools.seam.internal.core.el.SeamELCompletionEngine.resolveSeamELOperand(SeamELCompletionEngine.java:330)
>         at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validateElOperand(SeamELValidator.java:293)
>         at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validateEl(SeamELValidator.java:271)
>         at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validateString(SeamELValidator.java:260)
>         at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validateNodeContent(SeamELValidator.java:240)
>         at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validateChildNodes(SeamELValidator.java:221)
>         at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validateChildNodes(SeamELValidator.java:225)
>         at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validateChildNodes(SeamELValidator.java:225)
>         at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validateDom(SeamELValidator.java:194)
>         at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validateFile(SeamELValidator.java:153)
>         at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validate(SeamELValidator.java:106)
>         at org.jboss.tools.seam.internal.core.validation.SeamValidatorManager.validate(SeamValidatorManager.java:79)
>         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

        



More information about the jbosstools-issues mailing list