Hi James, Thanks for the reply again!
We've made some progress on the bug in that there was definately a connection that wasn't being closed - in one part of the code. This most certainly accounts for the pool connection problem. However, we still have an ongoing problem whereby these Tomcat thread numbers continue to grow!!!! And eventually the system grinds to a halt. Sometimes described as a "freeze". The strangest thing is - is that there are missing log entries for about 400+ threads (if I am to believe that Thread numbers are allocated in a sequential manner - as appears to be the case in the Tomcat code). I will investigate turning on more debugging within Tomcat. As for your migration idea, we are currently in the process of moving a new version of the code to JBoss 4.0.1. Thanks again James for the sanity check, Cheers, Andy View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3877953#3877953 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3877953 ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
