You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2015/06/02 00:41:17 UTC
[jira] [Commented] (QPIDJMS-64) Throw a JMSException with a more
consistent error message when connection attempts fail
[ https://issues.apache.org/jira/browse/QPIDJMS-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14568159#comment-14568159 ]
ASF subversion and git services commented on QPIDJMS-64:
--------------------------------------------------------
Commit 6bd44c040f9f4625aae0eb6a57cd01f0995be3b7 in qpid-jms's branch refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=6bd44c0 ]
https://issues.apache.org/jira/browse/QPIDJMS-64
Throw a more consistent error when connections fail to be created,
cleans up the exception support class a bit.
> Throw a JMSException with a more consistent error message when connection attempts fail
> ---------------------------------------------------------------------------------------
>
> Key: QPIDJMS-64
> URL: https://issues.apache.org/jira/browse/QPIDJMS-64
> Project: Qpid JMS
> Issue Type: Improvement
> Components: qpid-jms-client
> Affects Versions: 0.2.0
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Priority: Trivial
> Fix For: 0.3.0
>
>
> When a non-JMSException is caught in the connection factory we init the cause and use the message from the cause, instead we should use a more consistent error message that indicates a connection error and gives the URI that we failed to connect to, the cause will contain additional information that can help.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org