[JBoss JIRA] Created: (JBMESSAGING-1451) Make the logging more verbose so that a entry is written to the log when messages are moved to the DLQ.
9:12 a.m.
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: Tim Fox
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
9:30 a.m.
New subject: [JBoss JIRA] Assigned: (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...
]
Tim Fox reassigned JBMESSAGING-1451:
------------------------------------
Assignee: Howard Gao (was: Tim Fox)
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
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
9:32 a.m.
New subject: [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...
]
Tim Fox commented on JBMESSAGING-1451:
--------------------------------------
Also log when moving to the expiry queue.
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
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
8:32 a.m.
New subject: [JBoss JIRA] Updated: (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 updated JBMESSAGING-1451:
------------------------------------
Fix Version/s: 1.4.0.SP3.CP05
1.4.3.GA
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
8:39 a.m.
New subject: [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
3:15 p.m.
New subject: [JBoss JIRA] Closed: (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 closed JBMESSAGING-1451.
-----------------------------------
Resolution: Done
solved.
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
1:21 p.m.
New subject: [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.
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1451?page=com.atlassian.ji...
]
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
3:54 p.m.
New subject: [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:
-----------------------------------------
OK, if expiring is a common use case, then log level for expired messages should stay
trace level. and DLQ should be in DEBUG level, as if the user thinks if the application
has some problems with dead messages, he should turn on DEBUG option.
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
12:48 p.m.
New subject: [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:
-----------------------------------------
actually I think it's fair to use Debug for both DLQ and ExpiryQueues. If using
warning, we can't do the same as we did with trace. The current logger has no way to
tell if the Warn level is enabled or not (there is no method like isWarnEnabled() ).
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
4:52 a.m.
New subject: [JBoss JIRA] Closed: (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 closed JBMESSAGING-1451.
-----------------------------------
Resolution: Done
done.
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
5860
days inactive
5917
days old
9 comments
3 participants
participants (3)
-
Colin Mondesir (JIRA) -
Howard Gao (JIRA)
-
Tim Fox (JIRA)