maybe there should be a page in TomEE documentation about submitting
heap dumps to the team?
it could warn them to clean sensitive data using hprof-parser. it could
list preferred methods of receiving the dump, e.g. google drive, dropbox
etc.
also i have found gdb faster than jmap or jstack for getting core
initially which could be mentioned
On 09/01/2019 10:26, Jonathan Gallimore wrote:
Its on my todo list currently - which means "I've had the idea, and I have
a rough idea of how to implement it" :-). I haven't done any more than that
yet. The hprof-parser library (which isn't mine) - yes, that does work.
I've even managed to look at heap dumps with that which have been corrupted
or otherwise unreadable by other tools. If you're interested in what goes
in a heap dump, the source code is worth a look.
Jon
On Wed, Jan 9, 2019 at 8:31 AM Matthew Broadhead
<[email protected]> wrote:
that is a good idea. then i can submit more dumps. does it work?
On 08/01/2019 17:27, Jonathan Gallimore wrote:
One of the things on my todo list is to try and strip sensitive
information
out of heap dumps using this library:
https://github.com/eaftan/hprof-parser.
I'll have to try and get back to that.
Jon
On Tue, Jan 8, 2019 at 4:11 PM exabrial12 <[email protected]> wrote:
Hey Bruno,
I'll contact you privately to get it to you. The heap is a little more
sensitive than the jstack :) You'll have to describe the process you're
doing with it though so we can all learn
--
Sent from:
http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
