I recently had a problem with a multi-threaded application that would hang after I created and disposed of around 128 threads. I suspected the threads were somehow causing the problem, so I switched to a Thread Pool for my threads and the problem went away. I was going to forget about this problem, but I was lucky enough to stumble across this previous email:
http://www.mail-archive.com/[email protected]/msg00026.html It sounds like the same problem I had and it sounds like I'm not closing the sessions with the Thread Pool, I'm just side-stepping the problem by reusing the same threads. I would like to actually close the sessions properly to avoid any problems in the future. However, I don't think I can use the solution offered in that email thread, because I don't explicitly open and close sessions in my code. I'm using declarative transactions in Spring along with its SqlMapClientTemplate, so I don't really have direct access to the sessions. I would think Spring's SqlMapClientTemplate would take care of this. Is there a bug in Spring that isn't properly closing sessions? Could I not be configuring Spring correctly to do this properly? _________________________________________________________________ Shed those extra pounds with MSN and The Biggest Loser! http://biggestloser.msn.com/
