[jboss-jira] [JBoss JIRA] Reopened: (JBMESSAGING-1451) Make the logging more verbose so that a entry is written to the log when messages are moved to the DLQ.

[Tim Fox (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBMESSAGING-1451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Fox reopened JBMESSAGING-1451:
----------------------------------



This needs to be revisited.

Some customers need to expire messages at a very fast rate, so calling log.warn for each message doesn't fly, since log.warn has a significant overhead.

Need to store in a local variable, like we do with trace:

e.g. if (trace) { log.trace(); }

Also warn is not appropriate for all expiries (expiring messages might be a normal thing)

> Make the logging more verbose so that a entry is written to the log when messages are moved to the DLQ.
> -------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1451
>                 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1451
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: Configuration and Management
>    Affects Versions:  1.4.0.SP3.CP04
>            Reporter: Colin Mondesir
>            Assignee: Howard Gao
>             Fix For: 1.4.0.SP3.CP05, 1.4.3.GA
>
>
> At the moment when a message is moved to the expiry or dead letter queue the event is only logged at TRACE level.

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