Our Wicket-1.3.0-based website running on Tomcat 5.5.23 regularly dies after approx. 2 weeks with an OutOfMemoryError. Please excuse my ignorance, but we don't have any experience in profiling/stress testing web applications. What particular steps we could do to detect memory leaks? Thanks in advance for your help.

Tom

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to