Hello, We are running into memory usage problems in our Wicket application. The team has identified several areas worth of improving. However we were only able to do that by looking at our code and not by profiling the jvm. This brings me to my actual questions: 1. Is there tool or method to determine Wicket's memory usage/session size? 2. Can anyone suggest a tool or a method to profile a jvm? (We use WebSphere AS and RAD IDE - problem is that WAS simply crashes when attempting to run in memory profiling mode)
I'm open to all suggestions - if anyone could give some hints I would truly appreciate your help. Thanks, Dave
