I would suggest that you use a connection pool instead. They improve performance and can take care of the low-level details such as reconnect after timeout, etc.
I would suggest that you use a connection pool instead. They improve performance and can take care of the low-level details such as reconnect after timeout, etc. A good one is c3p0, but there are others. Spring has support for that, though I don't know all the details.
Here is the configuration of a DataSource for Spring.
I've been using c3p0 for the last 3 years in production and it rocks. – cherouvim Mar 10 '10 at 8:37.
This exception can have 2 causes: You aren't closing the JDBC resources properly. All of the Connection, Statement and ResultSet must be closed in reversed order in the finally block of the try block where they're been acquired. This is regardless of the fact whether you're using a connection pool or not.
You are closing the JDBC resources properly, but using a connection pool with poor settings. You need to make sure that the connection pool don't hold connections open longer than the DB configrured timeout. Decrease the one or increase the other in the configuration.
We needed to set the following properties in order to avoid the timeout even with connection pooling; we use the Apache Commons DBCP. SELECT 1 true.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.