[
https://issues.jboss.org/browse/REMJMX-158?page=com.atlassian.jira.plugin...
]
Richard Opalka commented on REMJMX-158:
---------------------------------------
It is not possible to write automatic test for this bug easily.
I wanted to create one based on GUI jconsole.
The idea was to invoke WildFly's jconsole script
(that is using JDKs jconsole) but I failed to do so.
The reason is if I call WildFly's jconsole script
and will force quit that process just WildFly's shell is terminated
but JDK's jconsole GUI remains opened and so issue cannot be reproduced.
It is known limitation of Java processes that it closes
just parent process but child processes will remain running.
Because of this our QA team should include manual test
described in this JIRA into their release criteria.
Unauthorized access exception when closing JMX console and RBAC is
set on server
--------------------------------------------------------------------------------
Key: REMJMX-158
URL:
https://issues.jboss.org/browse/REMJMX-158
Project: Remoting JMX
Issue Type: Bug
Components: Connection
Reporter: Richard Opalka
Assignee: Richard Opalka
Priority: Major
Fix For: 3.1.0.Beta1
javax.management.JMRuntimeException: WFLYJMX0037: Unauthorized access
at
org.jboss.as.jmx.PluggableMBeanServerImpl.authorizeMBeanOperation(PluggableMBeanServerImpl.java:1204)
at
org.jboss.as.jmx.PluggableMBeanServerImpl.authorizeMBeanOperation(PluggableMBeanServerImpl.java:1190)
at
org.jboss.as.jmx.PluggableMBeanServerImpl.removeNotificationListener(PluggableMBeanServerImpl.java:946)
at
org.jboss.as.jmx.BlockingNotificationMBeanServer.removeNotificationListener(BlockingNotificationMBeanServer.java:243)
at
org.jboss.as.jmx.AuthorizingMBeanServer.removeNotificationListener(AuthorizingMBeanServer.java:352)
at
org.jboss.remotingjmx.protocol.v2.ServerProxy$RemoteNotificationManager.removeNotificationListener(ServerProxy.java:229)
at
org.jboss.remotingjmx.protocol.v2.ServerProxy$RemoteNotificationManager.removeNotificationListeners(ServerProxy.java:239)
at
org.jboss.remotingjmx.protocol.v2.ServerProxy$RemoteNotificationManager.removeNotificationListener(ServerProxy.java:222)
at
org.jboss.remotingjmx.protocol.v2.ServerProxy$RemoteNotificationManager.access$1900(ServerProxy.java:199)
at org.jboss.remotingjmx.protocol.v2.ServerProxy.end(ServerProxy.java:167)
at
org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever.handleEnd(ServerCommon.java:216)
at
org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$notifyEnd$0(RemoteConnectionChannel.java:291)
at
org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:957)
at
org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at
org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
at
org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
at
org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
at java.lang.Thread.run(Thread.java:748)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)