Bugs item #458884, was opened at 2001-09-05 13:34 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=458884&group_id=22866 Category: JBossCMP Group: v2.4 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Neil Buesing (buesing) Assigned to: Nobody/Anonymous (nobody) Summary: [EBn] LOCKING-WAITING (TRANSACTION) Initial Comment: I'm getting a LOCKING-WAITING (TRANSACTION) problem, from EntityInstanceInterceptor, with concurrent access to an entity bean from two threads. The first thread classes a stateless session bean method with a RequiresNew transaction and the second thread calls the stateless session bean (different instance) with a NotSupported transaction. Even though 'NotSupported' is the transaction type for the methods of the entity bean, the second thread is locking until the first transaction is completed. With the following pseudo code I will get this transaction lock to occur, and I don't think it should happen. Consider the two classes: SessionBean : SessionBn // transaction type 'RequiresNew' getEntityStateWithTransaction() { EntityBnHome home = ... // lookup home. EntityBn bean = home.findByPrimaryKey(new EntityBn (1)); EntityBnState bean.getState(); try { Thread.sleep(120000); } catch (Exception e) { } return state; } // transaction type 'NotSupported' getEntityStateWithNoTransaction() { EntityBnHome home = ... // lookup home. EntityBn bean = home.findByPrimaryKey(new EntityBn (1)); EntityBnState state = bean.getState(); return state; } EntityBean : EntityBn // transaction type 'NotSupported' on all methods getState(); My client runs two threads, each thread creates a SessionBn, and the first thread calls getEntityStateWithTransaction(), and the second thread (starting 5 seconds later) calls getEntityStateWithNoTransaction. When I do this, the second thread will get a LOCKING- WAITING (Transaction) message and wait until the first thread is completed (and the transaction ends). I will try to provide a test case, but I thought I would post this right away, since maybe I'm messing something up, or this is desired behavior. I have the same problem in 2.2.1. Thanks, Neil ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=458884&group_id=22866 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
