If you use some kind of Unix then run: kill -3 <process id of tomcat/jetty/...) This will dump the threads' stack traces in the process standard out (somewhere in the log files). This way you can see whether there are threads waiting for something.
Making 20 requests and stopping responding could mean that your application/setup leaks connections and at some point the web server stops responding to new clients. On Wed, Jan 5, 2011 at 10:41 AM, LucHub <luca.abb...@luchub.com> wrote: > > Hi Martin, > > What do you exactly mean for dump the threads? I am almost a newbie, I > cannot find any document that examplin this. > > I made a few more test logging Wicket. To have the web site going down I > need a few hits (close each other) on a bookmarkablepagelink. > > Here ( http://www.luchub.com/temp/info.txt > http://www.luchub.com/temp/info.txt ) is the log at the INFO level just as > an example. > > > After this, any other hit of the link doesn't produce any row. > > Here I link a debug level log of a 'pretty much the same' situation ( > http://www.luchub.com/temp/example.txt > http://www.luchub.com/temp/example.txt ) > > Thanks in advance > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Wicket-web-site-down-with-a-few-hits-tp3174117p3175105.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 > >
