[
https://issues.apache.org/jira/browse/QPID-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655669#action_12655669
]
Robert Gemmell commented on QPID-1504:
--------------------------------------
I have attached a patch to QPID-1506 which addresses this by automatically
attempting the JMXMP connection after the RMI based connection fails because
the server is not RMI-JRMP based. If the user does not have the
jmxremote_optional.jar in place this will obviously fail, at which point a
dialogue is displayed asking them to provide it.
> Poor user feed back with protocol negotication mismatch on JMX Console
> ----------------------------------------------------------------------
>
> Key: QPID-1504
> URL: https://issues.apache.org/jira/browse/QPID-1504
> Project: Qpid
> Issue Type: Improvement
> Components: Java Management : JMX Console, Starter
> Affects Versions: M3
> Reporter: Martin Ritchie
> Priority: Minor
>
> Summary:
> If the broker has the jmxremote_optional.jar and <security>true configured.
> When a JMX Console client connects using the standard RMI connector it tells
> the user that:
> 'User authentication has failed'
> Which is poor as the stack trace gives the reason as 'non-JRMP server at
> remote endpoint'. We should use this ConnectIOException and provide better
> feedback.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
