[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3188) ConcurrentModificationException on flush of ServerConversationContext
[
https://jira.jboss.org/jira/browse/JBSEAM-3188?page=com.atlassian.jira.pl...
]
Jacob Orshalick updated JBSEAM-3188:
------------------------------------
Attachment: JBSEAM-3188-alternative.patch
This alternative patch avoids creation of a new HashSet instance. Kind of a hack though
as it creates a dependency between ServerConversationContext and PersistenceContexts by
ensuring the instance is available in the context. Other ideas?
ConcurrentModificationException on flush of
ServerConversationContext
---------------------------------------------------------------------
Key: JBSEAM-3188
URL: https://jira.jboss.org/jira/browse/JBSEAM-3188
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.0.3.CR1
Environment: 2.0.3.CR1, JBoss 4.2.2, JDK 5
Reporter: Sanne Grinovero
Attachments: JBSEAM-3188-alternative.patch, JBSEAM-3188-example.zip,
JBSEAM-3188.patch
As confirmed by other people on the forum at
http://seamframework.org/Community/ConcurrentModificationExceptionAfterPr...
It is possible for ServerConversationContext to iterate on an EntrySet which is modified
in the iteration block.
I couldn't understand exactly in which scenarios it happens, but it's easy to
patch the code
to iterate on a copy instead (I'll attach the patch).
I can't say if it's correct to make a copy, or if you should actually avoid the
changes.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira