Heh, I haven't had to worry about connection leaks since I discovered
Spring's JdbcTemplate and Hibernate, so it didn't even cross my mind. But
yeah, if the app is doing it's own JDBC connection management then that
is very much something J should look at.

jk

On Wed, Apr 15, 2009 at 05:58:11PM +0300, Serkan Camurcuoglu wrote:
> if all your threads are waiting for connections with no thread using a 
> db connection, I suspect that you either leak connections (i.e. forget 
> to free some connections) or each thread uses (requires) multiple 
> connections during a transaction and at some point all threads need at 
> least one more db connection to continue..
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to