Just a thought, I was having the same problem using JNDI for database connection. Our database pool was going crazy due to a lot of connections left unterminated and database memory usage was enormous. Restarting Tomcat would only help for a day or two and than OutOfMemory errors would come up again. Restarting the database, gave us several weeks until the error started coming up again once the memory used by database grew. Thinking that it had something to do with the memory it took to maintain the pool.
Oleg On Mon, 7 Feb 2005 23:02:36 -0600, Caldarale, Charles R <[EMAIL PROTECTED]> wrote: > > From: Dale, Matt [mailto:[EMAIL PROTECTED] > > Subject: RE: outOfMemory exception under high load > > > > It could be your permanent generation that is running out of > > space. Get a hold of jvmstat to determine if this is the case. > > Another possibility is that you're exceeding your limit on the number of open > files. Exceeding any underlying OS limit is usually translated to an > OutOfMemory exception by the JVM. > > - Chuck > > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY > MATERIAL and is thus for use only by the intended recipient. If you received > this in error, please contact the sender and delete the e-mail and its > attachments from all computers. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
