Re: Tomcat 6 serious issues on AIX 5.3

2012-09-29 Thread Pid *
On 28 Sep 2012, at 20:00, "vincent.soo...@daimler.com" wrote: > Post your DBCP configuration and let's see what can be > done with it. As above. p - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional c

RE: Tomcat 6 serious issues on AIX 5.3

2012-09-28 Thread vincent . soosai
anism. chuck.caldar...@unisys.com 09/28/2012 10:54 AM Please respond to users@tomcat.apache.org To users@tomcat.apache.org cc Subject RE: Tomcat 6 serious issues on AIX 5.3 > From: vincent.soo...@daimler.com [mailto:vincent.soo...@daimler.com] > Subject: Re: Tomcat 6 serious issues on AI

RE: Tomcat 6 serious issues on AIX 5.3

2012-09-28 Thread Caldarale, Charles R
> From: vincent.soo...@daimler.com [mailto:vincent.soo...@daimler.com] > Subject: Re: Tomcat 6 serious issues on AIX 5.3 > On machines with higher memory Tomcat does not crash but as I indicated we > get SocketException: > [2012-09-25 12:13:35,700] ERROR com.*Action

Re: Tomcat 6 serious issues on AIX 5.3

2012-09-28 Thread vincent . soosai
chultz.net 09/28/2012 10:21 AM Please respond to users@tomcat.apache.org To users@tomcat.apache.org cc Subject Re: Tomcat 6 serious issues on AIX 5.3 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Vincent, On 9/28/12 12:47 PM, vincent.soo...@daimler.com wrote: > We ran our web app on T

Re: Tomcat 6 serious issues on AIX 5.3

2012-09-28 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Vincent, On 9/28/12 12:47 PM, vincent.soo...@daimler.com wrote: > We ran our web app on Tomcat 4 on an AIX 5.3 box Java 5_64 with no > issues for 2 years. Great. > We recently upgraded to Tomcat 6 and we are seeing some unusual > problems. How did

Tomcat 6 serious issues on AIX 5.3

2012-09-28 Thread vincent . soosai
We ran our web app on Tomcat 4 on an AIX 5.3 box Java 5_64 with no issues for 2 years. We recently upgraded to Tomcat 6 and we are seeing some unusual problems. 1) After working for 2-3 days with heavy load One of our functions errors with java.sql.SQLException: java.io.IOException: