[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

[Mayank Gupta (JIRA)]

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

Mayank Gupta edited comment on AS7-5539 at 9/12/12 7:58 AM:
------------------------------------------------------------

Sorry, transaction attribute I am using for MDB's is "REQUIRED".

Yes it is joining the same transaction, but the thread is different because JMS is asynchronous and it starts it own thread stack.
What all I said is by interpreting and debugging the code in EntityBeanSynchronizationInterceptor.
When my Entity Bean is accessed before the message is put on JMS Queue, it assigns owner as currentRequester.

But when the entity bean business method is called again in same transaction (after MDB picked the message from JMS Queue) it did not assigned owner as currentRequestor but went to else part of code to acquire the lock where it hanged completely, till the transaction was rolled back by TM. Moreover this is a issue as same code is working on JBOSS6.  

    public void lock() {
        if (compareAndSetState(0, 1))
            owner = currentRequestor();
        else
            acquire(1);
    }
                
      was (Author: ion_mayank):
    Sorry, transaction attribute I am using for MDB's is "REQUIRED".

What all I said is by interpreting and debugging the code in EntityBeanSynchronizationInterceptor.
When my Entity Bean is accessed before the message is put on JMS Queue, it assigns owner as currentRequester.

But when the entity bean business method is called again in same transaction (after MDB picked the message from JMS Queue) it did not assigned owner as currentRequestor but went to else part of code to acquire the lock where it hanged completely, till the transaction was rolled back by TM. Moreover this is a issue as same code is working on JBOSS6.  

    public void lock() {
        if (compareAndSetState(0, 1))
            owner = currentRequestor();
        else
            acquire(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