activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-6765) HttpClientTransport loses exception information
Date Tue, 11 Jul 2017 20:01:00 GMT

    [ https://issues.apache.org/jira/browse/AMQ-6765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16082868#comment-16082868
] 

ASF subversion and git services commented on AMQ-6765:
------------------------------------------------------

Commit 56bed30c6427a1cc6b41e0d289a97c3e5b4582c4 in activemq's branch refs/heads/master from
[~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=56bed30 ]

AMQ-6765 Add trace logging of start failure exception

Log the exception at trace level when start fails.


> HttpClientTransport loses exception information
> -----------------------------------------------
>
>                 Key: AMQ-6765
>                 URL: https://issues.apache.org/jira/browse/AMQ-6765
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.14.3
>            Reporter: Harmen Renkema
>
> In the exception handling in the doStart() method of the HttpClientTransport vital debugging
information is lost.
> On line 282, for any encountered exception an IOException is thrown with the following
message: '"Failed to perform GET on: " + remoteUrl + " as response was: " + e.getMessage()'.
Where e.getMessage() usually returns null.
> It would be nicer if at least he http status code was logged, and maybe the stacktrace
when trace is enabled.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message