[jboss-jira] [JBoss JIRA] (WFLY-734) Deadlock detection for Entity beans

[Brian Stansberry (JIRA)]

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

Brian Stansberry resolved WFLY-734.
-----------------------------------

    Fix Version/s: 8.0.0.Alpha1
                       (was: Awaiting Volunteers)
       Resolution: Won't Fix


Support for CMP has been dropped for WildFly 8.
                
> 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: 8.0.0.Alpha1
>
>
> 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