[jboss-jira] [JBoss JIRA] (WFLY-734) Deadlock detection for Entity beans
Brian Stansberry (JIRA)
jira-events at lists.jboss.org
Tue Apr 23 18:21:53 EDT 2013
[ https://issues.jboss.org/browse/WFLY-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Stansberry updated WFLY-734:
----------------------------------
Assignee: (was: Brian Stansberry)
> Deadlock detection for Entity beans
> -----------------------------------
>
> Key: WFLY-734
> URL: https://issues.jboss.org/browse/WFLY-734
> Project: WildFly
> Issue Type: Feature Request
> Components: EJB
> Environment: Windows 7 64 bit, Java 1.7.0 64 bit
> Reporter: Christian Inzko
> Fix For: Awaiting Volunteers
>
>
> Deadlock detection with EJB 2.1 entity beans and pessimistic locking does not work.
> We are migrating our application from Jboss 4.05 where we used entity beans. This jboss version was able to detect deadlock situations and throw a org.jboss.util.deadlock.ApplicationDeadlockException. This mechanism does no longer work - instead of that both transactions just hang until a transaction timeout is reached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list