Once the database connections are high with an increased number of threads, they are unable to come back to the normal condition and we have to kill this tomcat as after some time when the load increases,
Why are they unable to come back? Are they not released back into the pool? Do they go bad but not abandoned by the pool?
What type of DB connection pooling are you doing? I had similar problems with a client who had a braindead connection pooling system... lost connections (as in, never returned to the pool), deadlock, and crashes when they allowed the pool to grow indefinately; they ran out of memory.
Also, why are you running three copies of Tomcat on each machine? Why not just the one VM? Oracle connectors take like 50MB each (on the server-size) to handle, so if you have a pool size of 10 connections for each tomcat instance, and 12 tomcat instances total, then your database machine must allocate over half a gig of memory to handle JDBC connections. I realize that your DB machine is a total *monster*, but I figure that the fewer things running, the easier they are to debug.
-chris
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
