it sounds like you were leaking DB connections Thread dump easily will show you this problem. You'll see threads trying to acquire a DB connection and will wait until some of the previous acquired connections is returned to the pool.
On Thu, Jan 6, 2011 at 12:27 PM, LucHub <luca.abb...@luchub.com> wrote: > > Hi, I tried to kill the process but I found nothing of strange. Right now I > think that the problem is probably solved. I throw away a library that I > used together with Hibernate (the c3p0 library) that I put ther essentially > for autoReconnection problems of the JDBC mysql driver. Avoiding this > library, the app seems to pass the load stress test. > > More info as I make more test. > > Thanks to all. > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Wicket-web-site-down-with-a-few-hits-tp3174117p3177253.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
