You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2017/07/11 20:22:00 UTC

[jira] [Resolved] (AMQ-6765) HttpClientTransport loses exception information

     [ https://issues.apache.org/jira/browse/AMQ-6765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish resolved AMQ-6765.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 5.15.1
                   5.14.6

> 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
>             Fix For: 5.14.6, 5.15.1
>
>
> 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)