activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] [Commented] (AMQ-6581) Change log level from DEBUG to WARN in ActiveMQMessageConsumer.dequeue(long timeout)
Date Sat, 28 Jan 2017 16:30:25 GMT


Timothy Bish commented on AMQ-6581:

Discard of expired messages is normal in cases where message expiration is set and the application
accounts for that such as data that if received after a certain time is no longer timely or
relevant.  The expired messages can be placed in the DLQ or discarded based on broker configuration,
it is up to the user to decide which is most appropriate.  Logging at WARN or even INFO on
the client seems unnecessary as the DEBUG level is for just that debug, so if you need to
debug this I'd recommend setting to debug.  The client of course can also be configured to
not check if messages are expired [consumerExpiryCheckEnabled|]
so if you don't want the client to do this turning that off will sort it. 

> Change log level from DEBUG to WARN in ActiveMQMessageConsumer.dequeue(long timeout)
> ------------------------------------------------------------------------------------
>                 Key: AMQ-6581
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: JMS client
>    Affects Versions: 5.x
>         Environment: Camel 'from' endpoint for ActiveMQ component on Linux servers (ActiveMQ
consumer client)
>            Reporter: Richard O'Sullivan
>            Priority: Minor
>              Labels: easyfix
>   Original Estimate: 1h
>  Remaining Estimate: 1h
> Change the log level from DEBUG to WARN in the consumeExpiredMessage block of the dequeue(long
timeout) method of the ActiveMQMessageConsumer class in the org.apache.activemq package.
> Currently, the consumeExpiredMessage block logs "{} received expired message: {}" at
the DEBUG level when a message is picked from the queue and found to be expired. Other than
the DEBUG log entry, the message is quietly consumed. In a Camel context, the message is not
forwarded to the Camel route and the message appears to be lost because it is common practice
to LOG at INFO or above in production environments.
> Proposed, change consumeExpiredMessage to WARN when a message is consumed and dropped.

> Rationale: Although, the disposition of expired messages should be an occasional occurrence,
the expiration may become systematic when a NTP daemon fails to operate properly. (This is
a real world case that caused a week long outage and is the reason for this request). Changing
the level to WARN will reduce the diagnosis time significantly. When the producer and consumer
are on different servers and are communicating  with a broker over a network, the WARN message
on the consumer will provide quick evidence that the message successfully crossed the network
but was consumed (dropped) by the consumeExpiredMessage block.

This message was sent by Atlassian JIRA

View raw message