[jboss-jira] [JBoss JIRA] (WFLY-1548) Add fallback querry to jconsole plugin

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789731#comment-12789731 ] 

RH Bugzilla Integration commented on WFLY-1548:
-----------------------------------------------

Darran Lofthouse <darran.lofthouse at redhat.com> made a comment on [bug 901311|https://bugzilla.redhat.com/show_bug.cgi?id=901311]

As I have said above I do not agree this is even a valid change.

The change being requested here is exactly the kind of change that works around one very specific issue only to lead to more support cases and bug reports against subsequent releases with very minor configuration changes.

For EAP 6.2 I believe the correct approach would be to update the CLI integration as describe above - provide the end user with an option to request a connection and appropriate GUI components to allow end user interaction should authentication be 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.Alpha3
>
>
> 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