[weld-issues] [JBoss JIRA] Commented: (WELD-833) ConcurrentModificationException while deactivating conversations
[
https://issues.jboss.org/browse/WELD-833?page=com.atlassian.jira.plugin.s...
]
Jan Groth commented on WELD-833:
--------------------------------
Good point then. IMO this issue is blocking _any_ Weld application. Even HelloWorld
crashes with ConcurrentModificationException as soon as you start some dedicated clicking
- and there's no workaround but hand-patching the app server.
Seems like (too) few people using Weld in productive environments.
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