[ https://issues.jboss.org/browse/WFLY-4925?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-4925: ----------------------------------- Description: This should not work, as the Monitor role is not allowed to do anything that modifies any state: {code} [standalone@localhost:9990 data-source=ExampleDS] :test-connection-in-pool{roles=Monitor} { "outcome" => "success", "result" => [true] } {code} I believe the problem is PoolOperations L75: {code} final ServiceController<?> managementRepoService = context.getServiceRegistry(false).getService( ConnectorServices.MANAGEMENT_REPOSITORY_SERVICE); {code} The parameter to context.getServiceRegistry(...) must be 'true' if the operation is going to use the returned service registry to perform any form of state modification. So I believe all the PoolOperation subclasses should provide a param to PoolOperation's constructor that can be used to set this value. I believe in all subclasses except DumpQueuedThreadInPool this param should be 'true'. was: This should not work, as the Monitor role is not allowed to do anything that modifies any state: {code} [standalone@localhost:9990 data-source=ExampleDS] :test-connection-in-pool{roles=Monitor} { "outcome" => "success", "result" => [true] } {code} I believe the problem is PoolOperations L75: {code} final ServiceController<?> managementRepoService = context.getServiceRegistry(false).getService( ConnectorServices.MANAGEMENT_REPOSITORY_SERVICE); {code} The parameter to context.getServiceRegistry(...) must be 'true' if the operation is going to use the returned service registry to perform any form of state modification. So I believe all the PoolOperation subclasses should provide a param to PoolOperation's constructor that can be used to set this value. I believe in all subclasses except DumpQueuedThreadInPool this param should be 'true'. -- This message was sent by Atlassian JIRA (v6.3.15#6346)