I have that same error when a process/user/ejb/... of a Connection of the pool puts a lock on objects (records, pages, whole tables!) in the database, and does not release this lock quickly enough. In the meanwhile, other processes/users/ejbs/... try to access these locked resources, and if they don't get it in time you will receive the error you had.
I think the MS SQLServer message isn't quite correct. It is not deadlock, where 2 processes hold reqources that the other needs. It is more like a timeout. However, this situation tends to snowball, having JBoss opening new connections to the DB until the maximum pool size is reached. What I have done until now is rewrite the code (always the first step ;-) )so that the DB is less sollicited, and optimize transactions declaratively so that locks are taken on smaller objects (records rather than tables) and for shorter durations. It's an EJB application. Yours is not, so who is managing YOUR transactions? At this moment we can run 100+ concurrent (i.e. working, not just logged in) users without problems. Another thing to do is optimize your DB: create indexes etc. But start with looking at your code: if you had the same problem on other application servers then JBoss isn't the answer. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3834347#3834347 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3834347 ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
