For memory issues - Eclipse Memory Analyzer is what you need. Make a heap dump at the start of your application, then use it for a while and make another dump, then compare the snapshots.
On Thu, Sep 8, 2011 at 2:37 PM, Martin Makundi <[email protected]> wrote: > Try jprofiler ;) > > 2011/9/8 Alex <[email protected]>: >> Hi, >> My Wicket application eats memory. The memory usage constantly increasing. >> So every week it is growing by 500 Mb. Can anyone suggest where can I start >> looking for the reason? >> Can JUnit testing help to figure out the reason? How? >> >> I have following set up: >> Wicket 1.4.9 >> Ubuntu 9.10 >> Tomcat 6 >> >> Dependencies: >> Spring 2.5.6 >> postgresql 8.3-603.jdbc4 >> commons-dbcp 1.4 >> itextpdf 5.0.4 >> log4j 1.2.14 >> slf4j-log4j12 1.4.2 >> >> Alex >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
