[
https://issues.apache.org/jira/browse/AMQ-6765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16082895#comment-16082895
]
ASF subversion and git services commented on AMQ-6765:
------------------------------------------------------
Commit 42e4a6cd9902e63db26f4edc22dfca123df01fc8 in activemq's branch
refs/heads/activemq-5.14.x from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=42e4a6c ]
AMQ-6765 Add trace logging of start failure exception
Log the exception at trace level when start fails.
(cherry picked from commit 56bed30c6427a1cc6b41e0d289a97c3e5b4582c4)
> 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)
