Rodney, Thanks for responding!
At 01:39 PM 1/23/03 -0800, Rodney Waldhoff wrote: >On Thu, 23 Jan 2003, Cindy Ballreich wrote: > >I was unable to find your previous message (in any) in the archives. There wasn't one. I posted a couple on the Tomcat-User list, but I had to move on to other things so I let it drop. >Typically this symptom is caused by a database-level "evict idle >connections" strategy. One solution is to configure a validation query to >ping the database periodically (so that the db knows the connection is >still in use). Another solution is to configure the pool to "test on >borrow", so that connections that are dropped by the database are dropped >by the pool before they are returned to your client code. The precise >configuration of either depends upon the specific pooling approach you're >using (BasicDataSource, JDBC2DataSource, Pooling[Driver|DataSource], etc.) > >Can you give a validation query a try, or provide more details on the >precise problem you're having? I'll give the validation query a try and see if that helps. The setup is more or less what is described here... http://marc.theaimsgroup.com/?l=tomcat-user&m=102225547106556&w=2 It's a little hard to describe the problem since I can see anything in any of the logs that might indicate when the connections were lost or why it happened. I'm no JDBC guru and I would appreciate any examples or working solutions that you (or anyone else) might be able to offer. Thanks again for responding. Cindy -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
