-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 David,
David Wood wrote: > Ok, I have found the problem. A firewall between my tomcat server and a > MySQL server was closing the database connection. [snip] > The execution continued and an exception was thrown, > where in the catch{} section I was then calling System.exit(), which I > thought would shut down the web service only, but it is actually shutting > down the whole JVM, causing tomcat to stop too. Heh, well /there's/ yer problem. Firewalls are known for terminating "idle" TCP/IP connections after a certain period of time, which is unfortunate, as many deployments put the database behind the firewall and the app servers out front. Are you using any kind of database connection pooling? If so, perhaps there is an auto-reconnect feature available for that component. For instance, Jakarta Commons DBCP includes such a feature. Once you are using DBCP, your code doesn't have to know how to handle unexpected disconnects like that, since the connection pool handles the automatic reconnection for you. Hope that helps, - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFffjT9CaO5/Lv0PARAl6EAJ4haR5ZfDodrGTK3oF3gdkotulG3ACgha8t wozRXyBuzTQDxPakjMFeqgI= =O8Fy -----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]