You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2008/12/03 15:05:44 UTC
[jira] Created: (QPID-1504) Poor user feed back with protocol
negotication mismatch on JMX Console
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
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.
[jira] Updated: (QPID-1504) Poor user feed back with protocol
negotication mismatch on JMX Console
Posted by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marnie McCormack updated QPID-1504:
-----------------------------------
Fix Version/s: Eclipse MC M5
Affects Version/s: (was: M3)
Sscoping items for early 2009 release of Java Eclipse Mgt Console
> 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
> Reporter: Martin Ritchie
> Priority: Minor
> Fix For: Eclipse MC M5
>
>
> 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.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Assigned: (QPID-1504) Poor user feed back with protocol
negotication mismatch on JMX Console
Posted by "Robert Gemmell (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Gemmell reassigned QPID-1504:
------------------------------------
Assignee: Robert Gemmell
> 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
> Reporter: Martin Ritchie
> Assignee: Robert Gemmell
> Priority: Minor
> Fix For: Eclipse MC M5
>
>
> 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.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-1504) Poor user feed back with protocol
negotication mismatch on JMX Console
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie updated QPID-1504:
---------------------------------
Component/s: Starter
> 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.
[jira] Commented: (QPID-1504) Poor user feed back with protocol
negotication mismatch on JMX Console
Posted by "Robert Gemmell (JIRA)" <qp...@incubator.apache.org>.
[ 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.
[jira] Resolved: (QPID-1504) Poor user feed back with protocol
negotication mismatch on JMX Console
Posted by "Robert Gemmell (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Gemmell resolved QPID-1504.
----------------------------------
Resolution: Fixed
Resolved previously by QPID-1506
> 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
> Reporter: Martin Ritchie
> Assignee: Robert Gemmell
> Priority: Minor
> Fix For: Eclipse MC M5
>
>
> 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.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org