Hi, I don't know if what I'll say applies to your situation but here goes: What is it your test client is trying to do? Is it only creating more and more of BeanA, or is it doing updates on them? Is createNew() the only method being called?
These deadlocks that occur, are they only in the db, or do you get them in the application as well (with Jboss giving ApplicationDeadLockExceptions)? It is quite easy to end up in a deadlock situation. I don't know if this is your case but anyway: Thread 1 (client 1) has a lock on bean A and is about to update bean B and at the same time Thread 2 (client 2) has a lock on bean B and is about to update bean A This would result in a deadlock. If you've got the for-pay documentation, you could read chapter 5 of the Jboss Admin and Devel guide. It's got a section on avoiding deadlocks. One of the tips is to order your bean access , that is first update bean A, then bean B, then C etc. It could also have something to do with your db connection's isolation level. Hope this helps, /fredrik View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3844938#3844938 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3844938 ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
