[
https://issues.jboss.org/browse/WFLY-1548?page=com.atlassian.jira.plugin....
]
Darran Lofthouse commented on WFLY-1548:
----------------------------------------
If a user has decided to connect directly to the WildFly process without a Remoting
connection why should we then go ahead and open a Remoting connection?
Secondly this may work whilst the local authentication mechanism is enabled but what about
situations where this is disabled and a username password prompt is now required?
Add fallback querry to jconsole plugin
--------------------------------------
Key: WFLY-1548
URL:
https://issues.jboss.org/browse/WFLY-1548
Project: WildFly
Issue Type: Enhancement
Affects Versions: 8.0.0.Alpha1
Reporter: Bartosz Baranowski
Assignee: Darran Lofthouse
Labels: JConsole, JMX, Plugin
Fix For: 8.0.0.Alpha2
JConsolePlugin connecects to default port, despite chance to use proper info.
Problem:
Unless I miss somethingm JConsole has a bit tight isolation between components. There is
no way for AS7 JConsolePlugin to access "connect dialog" info. Hence it has no
idea what is the content of URL being passed as remote.
AS7 JConsolePlugin checks if MBeanServerConnection is instance of RemotinConnection. If
its not, it fallbacks to default: localhost:9990.
However we can check for socket bindings and try to connect to proper socket.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira