Uploaded image for project: 'JBoss Enterprise Application Platform 6'
  1. JBoss Enterprise Application Platform 6
  2. JBPAPP6-1011

JConsole hangs when we try to access EAP6.0.0 in domain mode via Remoting Port

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: EAP 6.0.0
    • Fix Version/s: EAP 6.0.1 ER 2
    • Component/s: Remoting
    • Labels:
      None
    • Environment:

      All Operating System

    • Steps to Reproduce:
      Hide

      1). start JBoss in domain mode and set the "use-management-endpoint" to "false" in jmx subsystem. So that JBoss MBeans can be accessed via 4447 remoting port.

      2). Start the JBoss Server in a IP Address. like (./domain.sh -b 10.10.10.10 -bmanagement 10.10.10.10)

      3). Open a JConsole on a "Remote" box and then try to access JBoss EAP6 in JConsole Remote connection URL enter the address of your JBoss as following:

      service:jmx:remoting-jmx://10.10.10.10:4447

      4). Collectew thread dumps on JConsole side to see where it hangs.

      Show
      1). start JBoss in domain mode and set the "use-management-endpoint" to "false" in jmx subsystem. So that JBoss MBeans can be accessed via 4447 remoting port. 2). Start the JBoss Server in a IP Address. like (./domain.sh -b 10.10.10.10 -bmanagement 10.10.10.10) 3). Open a JConsole on a "Remote" box and then try to access JBoss EAP6 in JConsole Remote connection URL enter the address of your JBoss as following: service:jmx:remoting-jmx://10.10.10.10:4447 4). Collectew thread dumps on JConsole side to see where it hangs.
    • Affects:
      Release Notes
    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      To avoid this hang create a copy of the jconsole script - e.g. jconsole_nocli and remove the module 'org/jboss/as/cli' from the list of modules.

      This removal will prevent the discovery of the CLI GUI integration so the attempt to connect to the management channel will not be attempted.

      Show
      To avoid this hang create a copy of the jconsole script - e.g. jconsole_nocli and remove the module 'org/jboss/as/cli' from the list of modules. This removal will prevent the discovery of the CLI GUI integration so the attempt to connect to the management channel will not be attempted.

      Description

      While accessing JBoss EAP6 "Remotely" which is running in "Domain Mode" the Client or JConsole hangs without actually connecting to JBoss Instance. Using URL "service:jmx:remoting-jmx://10.10.10.10:4447"

      We enabled the JBoss JMX Access via remoting port(4447) by adding the following configuration in jmx subsystem:
      [code]
      <subsystem xmlns="urn:jboss:domain:jmx:1.1">
      <show-model value="true"/>
      <remoting-connector use-management-endpoint="false" />
      </subsystem>
      [/code]
      In Thread Dump we see the following message:

      [code]
      "AWT-EventQueue-0" prio=10 tid=0x00007f078026c800 nid=0x5c27 in Object.wait() [0x00007f077fe9d000]
      java.lang.Thread.State: WAITING (on object monitor)
      at java.lang.Object.wait(Native Method)

      • waiting on <0x00000007ac7dc2f0> (a java.lang.Object)
        at java.lang.Object.wait(Object.java:485)
        at org.xnio.AbstractIoFuture.await(AbstractIoFuture.java:73)
      • locked <0x00000007ac7dc2f0> (a java.lang.Object)
        at org.xnio.AbstractIoFuture.get(AbstractIoFuture.java:156)
      • locked <0x00000007ac7dc2f0> (a java.lang.Object)
        at org.jboss.as.cli.gui.JConsoleCLIPlugin.connectUsingRemoting(JConsoleCLIPlugin.java:118)
        at org.jboss.as.cli.gui.JConsoleCLIPlugin.connectCommandContext(JConsoleCLIPlugin.java:98)
        at org.jboss.as.cli.gui.JConsoleCLIPlugin.getTabs(JConsoleCLIPlugin.java:76)
        at sun.tools.jconsole.VMPanel.createPluginTabs(VMPanel.java:641)
        at sun.tools.jconsole.VMPanel.propertyChange(VMPanel.java:315)
        at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:339)
        at javax.swing.event.SwingPropertyChangeSupport.firePropertyChange(SwingPropertyChangeSupport.java:75)
        at javax.swing.event.SwingPropertyChangeSupport$1.run(SwingPropertyChangeSupport.java:80)
        at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
        at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:646)
        at java.awt.EventQueue.access$000(EventQueue.java:84)
        at java.awt.EventQueue$1.run(EventQueue.java:607)
        at java.awt.EventQueue$1.run(EventQueue.java:605)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
        at java.awt.EventQueue.dispatchEvent(EventQueue.java:616)
        at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
        at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
        at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
        at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
        [/code]

      ***NOTE: This issue does not happen if we use the Management Port "9999"

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  shelly.mcgowan Shelly McGowan
                  Reporter:
                  jaysensharma Jay SenSharma
                • Votes:
                  1 Vote for this issue
                  Watchers:
                  14 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: