[jboss-jira] [JBoss JIRA] Commented: (JBAS-3546) Change log level on CachedConnectionManager.closeConnection() to warn

[Weston Price (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBAS-3546?page=comments#action_12341628 ] 
            
Weston Price commented on JBAS-3546:
------------------------------------

Why can't you just change your appender for this category? 

> Change log level on CachedConnectionManager.closeConnection() to warn
> ---------------------------------------------------------------------
>
>                 Key: JBAS-3546
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3546
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: JCA service
>    Affects Versions: JBossAS-4.0.4.GA
>            Reporter: Felipe Leme
>         Assigned To: Weston Price
>            Priority: Trivial
>   Original Estimate: 5 minutes
>  Remaining Estimate: 5 minutes
>
> The feature of the CachedConnectionManager automatically closing connections (and warning about the fact) is pretty useful; in fact, so useful that we would like to receive email notifications when it occurs. But, unfortunatelly, we are not receiving such notifications, as our log4j SMTP appender is set to the WARN threshold, while such warnings are being logged as info:
>             if (e != null)
>                log.info("Closing a connection for you.  Please close them yourself: " + c, e);
>             else
>                log.info("Closing a connection for you.  Please close them yourself: " + c);
>             m.invoke(c, new Object[]{});
>          }
>          catch (Throwable t)
>          {
>             log.info("Throwable trying to close a connection for you, please close it yourself", t);
>          }
>       }
>       catch (NoSuchMethodException nsme)
>       {
>          log.info("Could not find a close method on alleged connection objects.  Please close your own connections.");
>       }
> So, I'm proposing these loggings are changed from info() to warn() - I don't think such change will cause any 'logging havoc', as the messages are only logged when the CachedConnectionManager is set to debug them...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira