[jboss-jira] [JBoss JIRA] (AS7-5539) JBOSS7 server hangs up completely when a EJB2.1 entity bean business method is called in same transaction in a separate thread from the thread which started the transaction

[Stuart Douglas (JIRA)]

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

Stuart Douglas commented on AS7-5539:
-------------------------------------

1. You need to add the configuration in jbosscmp-jdbc.xml. Alternatively you can configure this by default in standalone.xml:

{code}
<subsystem xmlns="urn:jboss:domain:ejb3:1.3">
  <entity-bean>
    <optimistic-locking enabled="true" />
  </entity-bean>
</subsystem>
{code}

2. Because the transaction is suspended, it has not completed. The lock is held until the transaction either commits or rolls back. If you were using opptimistic locking then you will get a bean per transaction, and this will not be an issue. 

3. see 1. 




                
> JBOSS7 server hangs up completely when a EJB2.1 entity bean business method is called in same transaction in a separate thread from the thread which started the transaction
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AS7-5539
>                 URL: https://issues.jboss.org/browse/AS7-5539
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: EJB, Transactions
>    Affects Versions: 7.1.1.Final, 7.1.3.Final (EAP), 7.2.0.Alpha1
>            Reporter: Mayank Gupta
>            Assignee: jaikiran pai
>
> JBOSS7 server hangs up completely while trying to access a EJB2.1 entity bean method in a specific scenario.
> I am using a session facade pattern in which I call my EntityBean from a Stateless session bean. For moth the beans I have defined the transaction attribute as REQUIRED.
> On debugging the code I found that if the same Entity bean is accessed from two different threads in same transaction then this issue occurs.
> So for the first time my code enters "EntityBeanSynchronizationInterceptor" code is able to take the lock and assign the requester thread as the lock owner. When second time it comes to access the same entity bean from different thread in SAME TRANSACTION (as 2nd required results in joining the transaction), JBOSS7 server code completely stalls in taking the lock. Moreover this time requester thread is not given the owner status of the transaction. 
> Code snippet where code hangs:
>         final Object lockOwner = getLockOwner(transactionSynchronizationRegistry);
>         lock.pushOwner(lockOwner);
>         try {
>             lock.lock();  //line 80 in EntityBeanSynchronizationInterceptor
> and subsequently in:
>     public void lock() {
>         if (compareAndSetState(0, 1))
>             owner = currentRequestor();
>         else
>             acquire(1); //Here line 86 in OwnableReentrantLock
>     }
> This is a completely blocking issue for migrating my application from JBOSS6 to JBOSS7.
> I get this error in numerous places in my application code.

--
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