[
https://issues.jboss.org/browse/WELD-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589699#comment-12589699
]
Ales Justin commented on WELD-833:
----------------------------------
We're planning a Weld 1.1.1 release in the next couple of days,
which will include this (and other) fix(es).
> 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
_______________________________________________
weld-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/weld-issues
