[jboss-jira] [JBoss JIRA] (WFCORE-4267) dump-all-threads management operation forces explicit setting of locked-monitors and locked-syncrhonizers

[jaikiran pai (Jira)]

jaikiran pai created WFCORE-4267:
------------------------------------

             Summary: dump-all-threads management operation forces explicit setting of locked-monitors and locked-syncrhonizers
                 Key: WFCORE-4267
                 URL: https://issues.jboss.org/browse/WFCORE-4267
             Project: WildFly Core
          Issue Type: Bug
          Components: Management
    Affects Versions: 7.0.0.Final
         Environment: WildFly server 15.0.0.Final
            Reporter: jaikiran pai
            Assignee: Jeff Mesnil


The {{dump-all-threads}} exposed by {{/core-service=platform-mbean/type=threading}} has this resource operation description:

{code}
....
"request-properties" => {
            "locked-monitors" => {
                "type" => BOOLEAN,
                "description" => "A list of detyped representations java.lang.management.MonitorInfo objects, each of w
hich represents an object monitor currently locked by the thread.",
                "expressions-allowed" => false,
                "required" => false,
                "nillable" => true,
                "default" => false
            },
            "locked-synchronizers" => {
                "type" => BOOLEAN,
                "description" => "A list of detyped representations java.lang.management.LockInfo objects, each of whic
h represents an ownable synchronizer currently locked by the thread.",
                "expressions-allowed" => false,
                "required" => false,
                "nillable" => true,
                "default" => false
            }
...
{code}

The {{locked-monitors}} and {{locked-synchronizers}} both are mentioned as {{required=false}} and with default values. However, when I run this operation as follows on a (standalone) WildFly 15.0.0.Final instance:

{code}
/core-service=platform-mbean/type=threading:dump-all-threads
{code}
I get:

{code}
{
    "outcome" => "failed",
    "failure-description" => "WFLYCTL0155: 'locked-synchronizers' may not be null",
    "rolled-back" => true
}
{code}

when I then pass, locked-synchronizers explicitly as an attribute, it then complains about locked-monitors being absent. The only way to get past this is to specify both those attributes in the operation.

By the way, the description of those attributes isn't too clear, IMO. Is it saying that the attribute represents a "list of detyped representations ...." ? In which case the type of BOOLEAN for that attribute would be incorrect. Or does it mean that if set to true then a "list of detyped representations ...." will be returned?




--
This message was sent by Atlassian Jira
(v7.12.1#712002)