I don't see any reason why JMS persistence should cause a deadlock. No part of the system should be trying to update the same data at the same time. If it were, it would be a bug.
The most likely cause is that the stupid locking mechanism within MSSQL is taking locks that are not row locks (e.g. full table or column locks). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3859071#3859071 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3859071 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
