glassfish
  1. glassfish
  2. GLASSFISH-20707

GlassFish V3 Embedded Broker fails to use DAS GF JMX port (RmiRegistry) when its secured

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: jms
    • Labels:
      None
    • Environment:
      • GFv3122
      • OS any
      • JDK any

      Description

      In GFv3, for the Admin-Connector (JMX connector) enable security-enable from false to true. When this is done, the the GlassFish MQ JMX will dynamically create a new RMIRegistry and unable to use GlassFish JMX port (8888)

      Testcase:
      ---------
      [Baseline]
      1. Use a stock GF with embedded MQ.
      2. Enable logger for javax.enterprise.resource.resourceadapter
      & javax.enterprise.resource.jms.level to be FINE
      3. Access the MQ by say "telneting to the MQ portmapper port 7676)
      (since by default MQ is lazy initialized)
      4. Now, you can see the MQ JMX port

      1. imq list jmx -b :7676
        should give you something like
        "service:jmx:rmi://<host>/jndi/rmi://<host>:8888/<host>/7676/jmxrmi"
        • Notice that the GF DAS RMI registry 8888 is used.

      [JMX Admin-service security enabled] Now, secure the GF JMX connector

      1. Restart, and redo step 3 & 4
      2. # imq list jmx -b :7676 shows
      "service:jmx:rmi://<host>/jndi/rmi://<host>:7776/<host>/7676/jmxrmi"

          • Note port 7776 (which is 7676+100 is created for the MQ rmi registry)

      Concerns:
      ----------
      a) More ports are used than needed.
      b) The MQ port itself is +100 of the MQ portmapper (not changeable unless
      using undocumented option).
      Not settable too (always default to +100)

      ====
      Logs:
      ====
      [#|2013-07-17T12:17:55.167+0000|FINE|oracle-glassfish3.1.2|javax.enterprise.resource.jms.com.sun.enterprise.connectors.jms.system|_ThreadID=29;_ThreadName=Grizzly-kernel-thread(1);ClassName=com.sun.enterprise.connectors.jms.system.ActiveJmsResourceAdapter;MethodName=logFine;|isASRmiRegistryPortAvailable - JMSService Type:EMBEDDED|#]

      [#|2013-07-17T12:17:55.170+0000|FINE|oracle-glassfish3.1.2|javax.enterprise.resource.jms.com.sun.enterprise.connectors.jms.system|_ThreadID=29;_ThreadName=Grizzly-kernel-thread(1);ClassName=com.sun.enterprise.connectors.jms.system.ActiveJmsResourceAdapter;MethodName=isASRmiRegistryPortAvailable;|Attempting to list rmi://0.0.0.0:8888|#]

      [#|2013-07-17T12:17:55.181+0000|FINE|oracle-glassfish3.1.2|javax.enterprise.resource.jms.com.sun.enterprise.connectors.jms.system|_ThreadID=29;_ThreadName=Grizzly-kernel-thread(1);ClassName=com.sun.enterprise.connectors.jms.system.ActiveJmsResourceAdapter;MethodName=isASRmiRegistryPortAvailable;|non-JRMP server at remote endpoint rmi://0.0.0.0:8888|#]

          • Due to securing GFv3.x RMIRegistry, the testing of this fails
            with non-JRMP hence MQ create a new RMIRegistry for the MQ JMX.

        Issue Links

          Activity

          gfuser9999 created issue -
          David Zhao made changes -
          Field Original Value New Value
          Link This issue depends on MQ-326 [ MQ-326 ]
          David Zhao made changes -
          Link This issue blocks GLASSFISH-20714 [ GLASSFISH-20714 ]
          David Zhao made changes -
          Tags MQ GF RMIRegistry extra port jms jmx 4_0_1-review GF MQ RMIRegistry extra jms jmx port
          alan42 made changes -
          Tags 4_0_1-review GF MQ RMIRegistry extra jms jmx port GF MQ RMIRegistry extra jms jmx port
          alan42 made changes -
          Tags GF MQ RMIRegistry extra jms jmx port 4_0_1-reviewed GF MQ RMIRegistry extra jms jmx port

            People

            • Assignee:
              David Zhao
              Reporter:
              gfuser9999
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: