-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Clay,
Clay Collier wrote: | 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. But you are probably still running out of connections -- you said that prod works fine for a while and then tanks. My guess is that you have a piece of code that leaks connections, but it's rarely used in development or test. Try turning on the debugging options for reporting connection leaks in DBCP and see if it catches anything. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkeeAoMACgkQ9CaO5/Lv0PA7tACeLUUW8OCQDivKYtnYJ2gh9lno 5zkAnA83xF/mWXSsqrB2SlIQToZzQ015 =yrf7 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
