Start JBoss with: -Djboss.socket.binding.port-offset=100 or -Djboss.management.native.port=10000 Run jconsole.sh and select Local Process and try to connect to JBoss, it fails to connect and logs: Exception in thread "AWT-EventQueue-0" java.lang.RuntimeException: Error connecting to JBoss AS. at org.jboss.as.cli.gui.JConsoleCLIPlugin.getTabs(JConsoleCLIPlugin.java:80) 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:672) at java.awt.EventQueue.access$400(EventQueue.java:81) at java.awt.EventQueue$2.run(EventQueue.java:633) at java.awt.EventQueue$2.run(EventQueue.java:631) at java.security.AccessController.doPrivileged(Native Method) at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87) at java.awt.EventQueue.dispatchEvent(EventQueue.java:642) 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) Caused by: java.lang.NullPointerException at org.jboss.as.cli.gui.JConsoleCLIPlugin.connectCommandContext(JConsoleCLIPlugin.java:109) at org.jboss.as.cli.gui.JConsoleCLIPlugin.getTabs(JConsoleCLIPlugin.java:77) ... 19 more It looks like this bug, however the fix does not seem to be in: https://issues.jboss.org/browse/AS7-6911 https://issues.jboss.org/browse/JBPAPP6-1774
1. Start JBoss with: -Djboss.socket.binding.port-offset=100 or -Djboss.management.native.port=10000 2. CLI from JConsole is still unable to connect to server with message: CLI GUI unable to connect to JBoss AS with localhost:9999 ... Port is set in code. But port should be parametrized in JConsole using Local Process
CLI tab in JConsole is available only if default port (9999) is used.
It looks like another backport is needed to get this working.
Verified on EAP 6.4.3.CP.CR2
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.