That's another option - cause a heapdump of the jvm when you suspect the leak is happening, transfer the dump file back locally and open it with visualvm.
On Wed, Sep 26, 2012 at 12:00 PM, Fabrizio Giudici < [email protected]> wrote: > On Wed, 26 Sep 2012 11:54:36 +0200, Ricky Clarkson < > [email protected]> wrote: > > I've successfully used an ssh tunnel to debug (rather than profile) an >> application running on a locked-down server, perhaps that would be >> useful here. >> > > +1 to VisualVM, and also add these options to your app: > > -XX:+**HeapDumpOnOutOfMemoryError > -XX:HeapDumpPath=/some/path > > They will produce a heap dump automatically when you have an OOME. > > -- > Fabrizio Giudici - Java Architect, Project Manager > Tidalwave s.a.s. - "We make Java work. Everywhere." > [email protected] > http://tidalwave.it - http://fabriziogiudici.it > > > -- > You received this message because you are subscribed to the Google Groups > "Java Posse" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to javaposse+unsubscribe@** > googlegroups.com <javaposse%[email protected]>. > For more options, visit this group at http://groups.google.com/** > group/javaposse?hl=en <http://groups.google.com/group/javaposse?hl=en>. > > -- You received this message because you are subscribed to the Google Groups "Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
