Bug 1215278 - [GSS](6.4.z) JConsole fails if trying to connect using Local Process to a standalone EAP instance running with offset ports or different management port
Summary: [GSS](6.4.z) JConsole fails if trying to connect using Local Process to a sta...
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: CLI
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: CR2
: EAP 6.4.3
Assignee: Ivo Studensky
QA Contact: Petr Kremensky
Depends On:
Blocks: 1231259
TreeView+ depends on / blocked
Reported: 2015-04-24 21:23 UTC by Brad Maxwell
Modified: 2019-07-11 09:02 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2017-01-17 10:36:30 UTC
Type: Bug

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker AS7-6504 0 Minor Closed jconsole window for an AS 7 server is labeled "JBoss CLI" 2018-05-23 01:46:56 UTC
Red Hat Issue Tracker AS7-6911 0 Major Resolved jconsole fails if trying to connect to a standalone EAP instance running with offset ports 2018-05-23 01:46:55 UTC
Red Hat Issue Tracker JBPAPP6-1774 0 Major Closed jconsole.bat fails if trying to connect to a standalone EAP instance running with offset ports 2018-05-23 01:46:56 UTC
Red Hat Issue Tracker WFLY-1548 0 Major Closed Add fallback querry to jconsole plugin 2018-05-23 01:46:56 UTC

Description Brad Maxwell 2015-04-24 21:23:15 UTC
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:

Comment 3 Marek Kopecky 2015-07-30 10:51:46 UTC
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

Comment 4 Marek Kopecky 2015-07-30 13:46:29 UTC
CLI tab in JConsole is available only if default port (9999) is used.

Comment 6 Ivo Studensky 2015-07-31 08:15:21 UTC
It looks like another backport is needed to get this working.

Comment 8 Marek Kopecky 2015-08-06 08:48:19 UTC
Verified on EAP 6.4.3.CP.CR2

Comment 9 Petr Penicka 2017-01-17 10:36:30 UTC
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.

Note You need to log in before you can comment on or make changes to this bug.