[embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-330) EJB3 Restart operation -> org.jboss.seam.ConcurrentRequestTimeoutException: Concurrent call to conversation
Ondrej Zizka (JIRA)
jira-events at lists.jboss.org
Tue Jul 19 14:39:24 EDT 2011
[ https://issues.jboss.org/browse/EMBJOPR-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615162#comment-12615162 ]
Ondrej Zizka commented on EMBJOPR-330:
--------------------------------------
Will this get fixed please?
> EJB3 Restart operation -> org.jboss.seam.ConcurrentRequestTimeoutException: Concurrent call to conversation
> -----------------------------------------------------------------------------------------------------------
>
> Key: EMBJOPR-330
> URL: https://issues.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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the embjopr-issues
mailing list