[embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-330) EJB3 Restart operation -> org.jboss.seam.ConcurrentRequestTimeoutException: Concurrent call to conversation

[Ondrej Zizka (JIRA)]

     [ https://jira.jboss.org/browse/EMBJOPR-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ondrej Zizka updated EMBJOPR-330:
---------------------------------

    Description: 
Similar to EMBJOPR-236, if not the same.

STR (or, better said, happened after this was done):

1) Install and run EAP 5.1.0.CR3.5 -c default
2) Deploy some EJB3 (attached)
3) Run it's Stop operation
4) Run it's Restart operation
5) That caused the attached exception to be thrown.

Or simply Stop and Start several times, it happens quite often.
Sometimes an exception page is shown, sometimes it's only visible in logs.
I haven't noticed this before, so I'd say it's a regression. 

  was:
STR (or, better said, happened after this was done):

1) Install and run EAP 5.1.0.CR3.5   -c default
2) Deploy some EJB3 (attached)
3) Run it's Stop operation
4) Run it's Restart operation
5) That caused the attached exception to be thrown. From the nature of the bug, it's not easily reproducible.

Similar to EMBJOPR-236, if not the same.





> EJB3 Restart operation -> org.jboss.seam.ConcurrentRequestTimeoutException: Concurrent call to conversation
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: EMBJOPR-330
>                 URL: https://jira.jboss.org/browse/EMBJOPR-330
>             Project: Embedded Jopr
>          Issue Type: Bug
>    Affects Versions: 1.3.4
>            Reporter: Ondrej Zizka
>         Attachments: BasicEJB3-good.jar, EMBJOPR-concbug.txt
>
>
> Similar to EMBJOPR-236, if not the same.
> STR (or, better said, happened after this was done):
> 1) Install and run EAP 5.1.0.CR3.5 -c default
> 2) Deploy some EJB3 (attached)
> 3) Run it's Stop operation
> 4) Run it's Restart operation
> 5) That caused the attached exception to be thrown.
> Or simply Stop and Start several times, it happens quite often.
> Sometimes an exception page is shown, sometimes it's only visible in logs.
> I haven't noticed this before, so I'd say it's a regression. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira