> Another option is to use a profiler in your dev environment, or a > production-similar environment and run a jmeter script that simulates users. > You can then create memory dumps and analyze them for leaks.
Definitively a very good idea to use jmeter and a profiler. Might be a bit of a pain to get started, but well worth your time when that lets you find memory leaks. When defining a test in jmeter (using a proxy to record generally works well), be sure you start with a fresh session, and close the session when you end the test. So start a fresh browser instance when you commence testing, and make sure your last action results in a session.invalidate/ session.invalidateNow (typically your logoff functionality, but if you don't have that functionality, simply build a bookmarkable page that does this, just for the test). Also be sure you understand how Wicket's page versioning works before you attempt to build in loops within a session. Good luck, Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
