gistfile1.txt

[standalone@localhost:9999 /] /subsystem=messaging/hornetq-server=default/security-setting=#/role=admin:add
{
    "outcome" => "failed",
    "failure-description" => "Operation handler failed: java.lang.IllegalArgumentException",
    "rolled-back" => true
}

15:49:25,754 ERROR [org.jboss.as.controller](HttpManagementService-threads - 18) Operation ("add") failed - address: ([
("subsystem" => "messaging"),
("hornetq-server" => "default"),
("security-setting" => "queue/test"),
("role" => "admin")
]): java.lang.NullPointerException
at org.jboss.as.controller.OperationContextImpl.addResource(OperationContextImpl.java:829) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.as.controller.OperationContextImpl.createResource(OperationContextImpl.java:798) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.as.messaging.SecurityRoleAdd.execute(SecurityRoleAdd.java:66)

The 2nd failure is different than the first. The 2nd happens, I believe, because you didn't first do /subsystem=messaging/hornetq-server=default/security-setting="queue/test":add.

The NPE is the wrong way of dealing with that though. There's logic for a more meaningful exception when you try and skip a level, but it must be being short-circuited.

The 1st one is a different case, as the security setting resource already exists. So two bugs for the price of one JIRA.

It doesn't matter. Even with an existing security setting '#', the error occurs:

10:23:23,245 ERROR [org.jboss.as.controller](HttpManagementService-threads - 15) Operation ("add") failed - address: ([
("subsystem" => "messaging"),
("hornetq-server" => "default"),
("security-setting" => "#"),
("role" => "admin")
]): java.lang.IllegalArgumentException
at org.jboss.dmr.ModelValue.asBoolean(ModelValue.java:66) [jboss-dmr-1.0.0.Final.jar:1.0.0.Final]
at org.jboss.dmr.ModelNode.asBoolean(ModelNode.java:139) [jboss-dmr-1.0.0.Final.jar:1.0.0.Final]
at org.jboss.as.messaging.SecurityRoleAdd.transform(SecurityRoleAdd.java:111)
at org.jboss.as.messaging.SecurityRoleAdd$1.execute(SecurityRoleAdd.java:81)
at org.jboss.as.controller.OperationContextImpl.executeStep(OperationContextImpl.java:353) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]

Yes, that's what I meant in my last post: "The 1st one is a different case, as the security setting resource already exists. So two bugs for the price of one JIRA."

Hmm, but I see your comment re: the persistence issue.