activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-5879) Log full stack trace on transport failure
Date Tue, 14 Jul 2015 13:50:04 GMT

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

Timothy Bish commented on AMQ-5879:
-----------------------------------

Pretty sure it would log the stack trace if the log level is set to debug, many folks find
the full stack trace on those error annoying when they are at warn level as there are valid
cases where the transport can throw out an error such as connection drop.  Can you peek again
at the code and make sure just turning on debug level logging isn't enough?

> Log full stack trace on transport failure
> -----------------------------------------
>
>                 Key: AMQ-5879
>                 URL: https://issues.apache.org/jira/browse/AMQ-5879
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 5.11.1
>            Reporter: Christopher L. Shannon
>            Priority: Minor
>
> The full stack trace should be logged when a transport fails and the exception is unexpected.
 There is a user currently getting an ArrayIndexOutOfBoundsException but the full stack trace
is being hidden.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message