[Discussion] Expected behavior of combining "all" and "live" options of jmap

Hohensee, Paul hohensee at amazon.com
Wed Aug 19 20:18:01 UTC 2020


I prioritize compatibility, so would go with option 2.

Thanks,
Paul

On 8/18/20, 11:17 PM, "serviceability-dev on behalf of linzang(臧琳)" <serviceability-dev-retn at openjdk.java.net on behalf of linzang at tencent.com> wrote:

    Dear All,
            May I get some suggestions?  so that I can  work out a patch
    base on that.
            Or may be it should not be treated as an issue?
    BRs,
    Lin

    On 17/08/2020 17:17, linzang(臧琳) wrote:
    >  Dear all,
    >           we found the jmap’s histo/dump command could accept "live" and "all" options together, and the specification does not describe what is the expected behavior of it.
    >           I have tried that when these two options used together, the "live" takes effect, no matter what sequences are they in commandline.
    >           IMO, it is a little confused to use "live" and "all" together, and if it is allowed, the specification may need to be updated to state the behavior clearly.
    >           Therefore may I ask your suggestion on which option of the following is prefered:
    >           (option 1.)  disallow using these two options together, I think this is more clear, but I am not sure whether there is backward compatibility risk.
    >           (option 2.)  allow the combination use of "live" and "all", and update the specification to clearly describe the behavior that "live" takes effect in this case.
    >           What do you think?
    >
    > Thanks,
    > Lin
    >
    >
    >




More information about the serviceability-dev mailing list