Darren Kukulka wrote: > Hi, > > > > We've got a Tomcat 6.0.13 server running a single application under > 64-bit windows with 64-bit SUN JDK 1.6_03 > > > > It runs into situations where a large number of blocked threads appear > that seem to relate to hibernate functions unable to obtain database > connections/resources. This leads to the application slowing down > considerably to the point where we need to restart Tomcat to restore > service. > > > > At the moment we are having a performance review of the back-end > database which runs separately on a SQL Server 2005 server. We thought > it would be prudent to see if there is any tuning we could do within > Tomcat to help alleviate the pain felt by the users. > > > > Is anybody aware of any parameters that can be utilised, either > programmatically or through Tomcat configuration?
Sounds like you have a connection leak. There are various techniques for tracking these down. One I like is setting the connection pool size to 1 in your dev environment and then running your tests. Mark --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
