I've experienced the same thing. Have you got any solutions yet?
I have fixed this in an OK fashion. What I ended up doing it setting the <trans-attribute> for the main session beans involved to 'NotSupported'. This meant that this one TX didn't recruit huge numbers of beans and therefore lock up the system. You have to be careful here because if you are writing to a database you don't want to use 'NotSupported' as I believe your updates won't get written through. I had this problem and for that session bean only I used 'Required' (which will set up many small TXs over the use case).
Interestingly enough as the code was, in 2.4.6 w/Tomcat 4 when you try to invoke another use case from another browser you eventually get a DeadLock exception.
Hi, I finally got it to perform somewhat muti-tasking now.
I am using jboss3 final, and CMP.
I did it by setting the locking policy to org.jboss.ejb.plugins.lock.MethodOnlyEJBLock and set my stateless bean transaction attribute to requiresnew.
It looks like long transactions are not blocking other transactions from the users point view. However, transactions are put in a queue and handled in a single task manner.
I wish someone could tell me how to have these inserts in the transactions happen concurrently.
I basically have one stateless sessionbean that has a method that does a lot of insert in a container managed transaction (RequiresNew) (10minutes). I have 2 clients calling it, it seems server is doing transaction one by one.
Some one please help.