That is a neat little tool. I will have to play around
with it a bit to see whether that functionality would be
worth including in the Wrapper itself.
For now, I was able to build the DLL on Windows using the
instructions at the top of the page. I put the resulting
heapprofile.dll file in the same directory as the wrapper.dll.
Then added the following to my wrapper.conf
set.PATH=%PATH%;../lib
wrapper.java.additional.1=-Xrunheapprofile
Just doing that, the tool seemed to work just fine with the
Wrapper out of the box. It created a heap.dump file on
shutdown in the bin directory.
If you are doing a dump of a large application, you may need
to extent the exit timeout as follows to prevent the Wrapper
from killing the JVM process while it is writing out the file:
wrapper.jvm_exit.timeout
The requested thread dump also seems to work correctly.
When you request it, the regular JVM thread dump is also
displayed.
Is there a reason why you want this included in the Wrapper
rather than using this tool as is? It would be nice if a
binary was provided as building from source is a pain.
I will look into how that tool could be used however.
Cheers,
Leif
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=228081
That is a neat little tool. I will have to play around
with it a bit to see whether that functionality would be
worth including in the Wrapper itself.
For now, I was able to build the DLL on Windows using the
instructions at the top of the page. I put the resulting
heapprofile.dll file in the same directory as the wrapper.dll.
Then added the following to my wrapper.conf
set.PATH=%PATH%;../lib
wrapper.java.additional.1=-Xrunheapprofile
Just doing that, the tool seemed to work just fine with the
Wrapper out of the box. It created a heap.dump file on
shutdown in the bin directory.
If you are doing a dump of a large application, you may need
to extent the exit timeout as follows to prevent the Wrapper
from killing the JVM process while it is writing out the file:
wrapper.jvm_exit.timeout
The requested thread dump also seems to work correctly.
When you request it, the regular JVM thread dump is also
displayed.
Is there a reason why you want this included in the Wrapper
rather than using this tool as is? It would be nice if a
binary was provided as building from source is a pain.
I will look into how that tool could be used however.
Cheers,
Leif