activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AMQ-1384) Exceptions in TransportConnection is logged in DEBUG level making it non traceable in production
Date Mon, 07 Apr 2008 22:22:32 GMT

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

David Jencks updated AMQ-1384:
------------------------------

    Fix Version/s: 4.1.3
                       (was: 4.1.0)
                       (was: 4.1.1)
                       (was: 4.1.2)
                       (was: 5.1.0)
                       (was: 5.2.0)

Did not get fixed in 4.1.2

> Exceptions in TransportConnection is logged in DEBUG level making it non traceable in
production
> ------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-1384
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1384
>             Project: ActiveMQ
>          Issue Type: Bug
>            Reporter: anish pathadan
>             Fix For: 4.1.3
>
>         Attachments: TransportConnection_Log.patch
>
>
>  It seems that the error is only logged in DEBUG mode in the following code in the {{org.apache.activemq.broker.TransportConnection}}
class:
> {code}
>    public void serviceTransportException(IOException e) {
>        if( !disposed.get() ) {
>            transportException.set(e);
>            if( transportLog.isDebugEnabled() )
>                transportLog.debug("Transport failed: "+e,e);
>            ServiceSupport.dispose(this);
>        }
>    }
> {code}
> This makes exception non traceable in production mode.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message