[weld-issues] [JBoss JIRA] Commented: (WELD-833) ConcurrentModificationException while deactivating conversations

Vetle Roeim (JIRA) jira-events at lists.jboss.org
Tue Mar 22 10:04:46 EDT 2011

    [ https://issues.jboss.org/browse/WELD-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589655#comment-12589655 ] 

Vetle Roeim commented on WELD-833:

Perhaps I should have been more specific: what I was asking for is a workaround that can be applied outside Weld, without upgrading Weld to an unreleased version.
For various reasons it might be difficult to upgrade.

> ConcurrentModificationException while deactivating conversations
> ----------------------------------------------------------------
>                 Key: WELD-833
>                 URL: https://issues.jboss.org/browse/WELD-833
>             Project: Weld
>          Issue Type: Bug
>          Components: Conversations
>    Affects Versions: 1.1.0.CR3, 1.1.0.Final, TBC
>            Reporter: Jan Groth
>            Assignee: Ales Justin
>             Fix For: 1.2.0.Beta1
>         Attachments: fix_deletion_of_conversations.patch
> If a conversation gets deactivated, the code which actually iterates the map of conversations in org.jboss.weld.context.AbstractConversationContext  is erroneous and easily runs into a ConcurrentModificationException if there is more than one conversation. We consider this a pretty serious defect because its not possible to use JBoss AS 6.0 GA for a real-world application.
> See attached patch for a fix.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

More information about the weld-issues mailing list