RFR: JDK-8177763: Getting an hprof dump via jcmd could benefit from stronger option checking

Chris Plummer chris.plummer at oracle.com
Wed Aug 29 06:21:27 UTC 2018


Hi Gary,

What would be really useful are some before/after examples that 
demonstrate what has changed from the users point of view.

thanks,

Chris

On 8/28/18 5:26 AM, Gary Adams wrote:
> This message may have been lost in the vacation email backlog, so I'm
> sending it again.
>
> On 8/9/18, 2:19 PM, Gary Adams wrote:
>> Thee are several reported problems using jcmd for obtaining heap dumps.
>>
>> Some users are confused by the positional argument for a filename
>> when a similar jfr command uses "key=value" syntax.
>>
>> Some users are confused by the basic nature of the command, where the 
>> jvm
>> executing the heap dump is running in a different current directory than
>> the jcmd itself.
>>
>> This is a proposed fix to report the current directory and the filename
>> when the heap dump is successfully written or if an error occurs. There
>> is also a proposed fix to handle the case when the user provided
>> "key=value" inputs. If the key matches the argument name, then the
>> user intended the value to be used.
>>
>>   Issue: https://bugs.openjdk.java.net/browse/JDK-8177763
>>   Webrev: http://cr.openjdk.java.net/~gadams/8177763/webrev.00/
>>
>>
>




More information about the serviceability-dev mailing list