I'll try running the app locally first and see if there is anything obvious. If not, I'll spin up another environment like prod and try and get it to do a dump for analysis locally...
Thanks guys On 26 September 2012 11:15, Fabrizio Giudici <[email protected]>wrote: > On Wed, 26 Sep 2012 12:04:19 +0200, Jan Goyvaerts <[email protected]> > wrote: > > 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. >> > > Yep. It can help when for a reason or another you can't connect with > VisualVM, and sometimes I found that even though connection was not a > problem. the application was so hung up (CPU-bound problems other than > OOME) that VisualVM couldn't connect. I saw the admin forced to shut down > the app and restart it, but at that point all the useful information were > lost. I think that the automated dump has more chances to work. > > > > -- > 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.
