Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-20205

[QE](7.3.z) WFCORE-5136 - NPE in ModelControllerMBeanHelper

    XMLWordPrintable

Details

    • False
    • False
    • +
    • Undefined
    • Hide

      Issue can be reproduced by invoking the addJndi operation on a JMS queue via JMX.
      For example on jboss.as:subsystem=messaging-activemq,server=default,jms-queue=ExpiryQueue from the default standalone-full configuration.

      Show
      Issue can be reproduced by invoking the addJndi operation on a JMS queue via JMX. For example on jboss.as:subsystem=messaging-activemq,server=default,jms-queue=ExpiryQueue from the default standalone-full configuration.

    Description

      The fix for JBEAP-19870 causes a NPE being thrown for some JMX calls.

      15:50:42,596 WARN  [org.jboss.remotingjmx.protocol.v2.ServerCommon] (pool-13-thread-1) Unexpected internal error: java.lang.NullPointerException
	at org.jboss.as.jmx.model.ModelControllerMBeanHelper.invoke(ModelControllerMBeanHelper.java:556) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
	at org.jboss.as.jmx.model.ModelControllerMBeanHelper.invoke(ModelControllerMBeanHelper.java:487) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
	at org.jboss.as.jmx.model.ModelControllerMBeanServerPlugin.invoke(ModelControllerMBeanServerPlugin.java:193) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
	at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:727) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
	at org.jboss.as.jmx.BlockingNotificationMBeanServer.invoke(BlockingNotificationMBeanServer.java:168) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
	at org.jboss.as.jmx.AuthorizingMBeanServer.invoke(AuthorizingMBeanServer.java:258) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
	at org.jboss.remotingjmx.protocol.v2.ServerProxy$InvokeHandler.handle(ServerProxy.java:950)
	at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1$1.run(ServerCommon.java:153)
	at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:71) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
	at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:66) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
	at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:313) [wildfly-elytron-auth-server-1.10.8.Final-redhat-00001.jar:1.10.8.Final-redhat-00001]
	at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:270) [wildfly-elytron-auth-server-1.10.8.Final-redhat-00001.jar:1.10.8.Final-redhat-00001]
	at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254) [wildfly-controller-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
	at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225) [wildfly-controller-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
	at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor.handleEvent(ServerInterceptorFactory.java:66) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
	at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:149)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_265]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_265]
	at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_265]

      This is a regression against EAP 7.3.2, so setting priority to blocker for now.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-5136 NPE in ModelControllerMBeanHelper

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is caused by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-19870 [GSS](7.3.z) WFCORE-5037 - EJB Stats MBeans do not return method stats via JMX, but does via CLI

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Activity

            People

              spyrkob Bartosz Spyrko-Smietanko
              pmackay@redhat.com Peter Mackay
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: