Lukasz Kucharski <lkuchars <at> gmail.com> writes: > There are only two frameworks I use in my web app - Hibernate and > Tapestry. Problem is that after a few requests (20-30 requests) tomcat > gets more and more cpu time to actually preform request. It is clearly > visible in my log files when messages are being written slower and > slower. In the end even simple initialization of Class takes ages to > finally stop responding.
I'd direct all the requests to the same page to see if this happens. If yes, then disable part of the functionality (eg, some components) of that page bit by bit and see if it improves the situation. This way you should be able to isolate the problem. Another approch is to run a profiler to get some hints on what's wrong. For example, you may try http://profiler.cougaar.org/ -- Author of an e-Book for learning Tapestry (http://www.agileskills2.org/EWDT) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
