[jbosstools-issues] [JBoss JIRA] (JBIDE-15651) EAP 6.2 cannot be connected to in MBean Explorer

[Martin Malina (JIRA)]

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

Martin Malina commented on JBIDE-15651:
---------------------------------------

Rob said in JBIDE-15614:
{quote}
Martin: It works for me, but only assuming you have already done the following:
1) Added a user via the add-user.sh script
2) Update the username / password in the server editor to match those values
Have you done both of these things?
{quote}

You're right, when I set up an admin user it then works.
But I checked again and for EAP 6.1.0 no user is needed to access JMX on a local server.
So something has changed in EAP 6.2. But I spoke to EAP QE and they say the <local> is still set for the SecurityRealm, so things should work the same. And indeed, jboss-cli.sh is still able to connect to a local running EAP 6.2 without any password.
So can you please check what changed here? It may even be a bug in EAP.
                
> EAP 6.2 cannot be connected to in MBean Explorer
> ------------------------------------------------
>
>                 Key: JBIDE-15651
>                 URL: https://issues.jboss.org/browse/JBIDE-15651
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: jmx
>    Affects Versions: 4.1.1.Alpha2
>         Environment: JBDS 7.1.0.Alpha2 B431
>            Reporter: Martin Malina
>             Fix For: 4.1.1.Beta1
>
>
> When you start EAP 6.2.0.ER4 (or ER5) added manually and then try Show in -> MBean Explorer, it will show the server as [disconnected] and the server won't connect.

--
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