Change thread dump location?
jaromir.hamala at gmail.com
Tue Apr 15 07:45:47 UTC 2014
I mean a response to SIGQUIT. I'd like to add an ability to specify a
file/directory where threaddumps will be written to even when stdout/err
are not redirected. I believe having separated threadumps from rest of the
logs might be useful when troubleshooting. It's actually not my idea -
there was a user asking how to do it in other mailing-list.
On Tue, Apr 15, 2014 at 7:21 AM, David Holmes <david.holmes at oracle.com>wrote:
> Hi Jaromir,
> On 11/04/2014 11:34 PM, Jaromir Hamala wrote:
>> I'd like to create a patch allowing to change a location of a threaddump
>> when it's triggered by sending a signal. My understanding is that
>> there is no option to specify a custom path.
> Do you mean the thread-dump in response to SIGQUIT (which goes to the VM's
> output stream) or the hs-err log file produced when the VM crashes?
> The SIGQUIT thread-dump doesn't go to a file unless you happen to be
> redirecting VM output to a file.
> Is this a feature you would consider to accept & eventually merge? I'm
>> aware one could use eg. jstack to save the threaddump into an arbitrary
>> location, but this tooling is not always available as it's part of JDK and
>> not JRE.
“Perfection is achieved, not when there is nothing more to add, but when
there is nothing left to take away.”
Antoine de Saint Exupéry
More information about the hotspot-dev