[seam-issues] [JBoss JIRA] Commented: (JBSEAM-3188) ConcurrentModificationException on flush of ServerConversationContext

[Amar Panigrahy (JIRA)]

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

Amar Panigrahy commented on JBSEAM-3188:
----------------------------------------

Hi everybody,

Can you all please let me know how do i integrate this patch into my code.
I am also getting ConcurrentModificationException in ServerConversationContext.flush().

I am gettihng this problem in live project, Have you all created any jar file with some modification in origial Jar file.
If then , please share that jar file with me, Its very urgent or let me know which steps i need to perform to resolve this issue.

I also updated my Jboss-seam.jar file to 2.1.2.But still this exception exist.

> ConcurrentModificationException on flush of ServerConversationContext
> ---------------------------------------------------------------------
>
>                 Key: JBSEAM-3188
>                 URL: https://issues.jboss.org/browse/JBSEAM-3188
>             Project: Seam 2
>          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
>              Labels: patch
>         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/ConcurrentModificationExceptionAfterProgrammaticLogin
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira