> What version of Tomcat are you running? If (as is likely currently) > it is one that bundles Commons Pool 1.3, there is something funny > going on because the line number where wait on borrowObject is > occurring in the thread dumps would indicate that > > a) the pool is exhausted and > b) the maxWait parameter is set at the default, which is to wait indefinitely > > Is it possible that your production config is missing maxWait? > > Phil
I'm running Tomcat 5.5.25, but I think I've found the problem. When I deployed the application onto the production server, the server was unable to set up the connection pool until I added an additional Resource entry to a context.xml file in the web applications META-INF directory. The production server seems to use that entry an ignore the server.xml entry and use context.xml; the test environment, launched from Eclipse, ignores the context.xml file and uses the server.xml entry. Not sure why that's the case- it may just be something in the docs or the Eclipse setup I've missed- but that at least explains why the maxWait and other settings were being ignored on the prod server. Thanks Phil- I think that put me onto the right answer. Clay --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
