You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Rob Davies (JIRA)" <ji...@apache.org> on 2009/09/04 20:53:12 UTC
[jira] Updated: (AMQ-1384) Exceptions in TransportConnection is
logged in DEBUG level making it non traceable in production
[ https://issues.apache.org/activemq/browse/AMQ-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies updated AMQ-1384:
----------------------------
Fix Version/s: (was: 4.1.3)
5.4.0
> 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: 5.4.0
>
> 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.