[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1451) Make the logging more verbose so that a entry is written to the log when messages are moved to the DLQ.
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1451?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1451:
-----------------------------------------
in ClientConsumer.checkExpiredOrReachedMaxdeliveries() change the log level to warn.
if (expired)
{
log.warn(proxy.getMessage() + " has expired, cancelling to
server");
}
else
{
log.warn(proxy.getMessage() + " has reached maximum delivery number
" + maxDeliveries +", cancelling to server");
}
In ServerSessionEndpoint.cancelDeliveryInternal(), add warn messages:
if (expired)
{
//Sent to expiry queue
log.warn("Sending expired message: " + rec.del.getReference() +
" to expiry queue " + rec.expiryQueue);
JBossMessage copy = makeCopyForDLQOrExpiry(true, del);
moveInTransaction(copy, del, rec.expiryQueue, false);
}
else
{
//Send to DLQ
log.warn("Sending message: " + rec.del.getReference() + " to
dlq " + rec.dlq);
JBossMessage copy = makeCopyForDLQOrExpiry(false, del);
moveInTransaction(copy, del, rec.dlq, true);
}
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