[
https://issues.apache.org/activemq/browse/AMQNET-268?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_36932
]
Jim Gomes logged work on AMQNET-268:
------------------------------------
Author: Jim Gomes
Created on: 10/Aug/10 07:59 PM
Start Date: 10/Aug/10 07:58 PM
Worklog Time Spent: 1 hour, 30 minutes
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes (was: 1 hour)
Time Spent: 1 hour, 30 minutes
> Add configuration option to have the client ignore the message expiration
> time.
> -------------------------------------------------------------------------------
>
> Key: AMQNET-268
> URL: https://issues.apache.org/activemq/browse/AMQNET-268
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: ActiveMQ
> Affects Versions: 1.3.0
> Reporter: Jim Gomes
> Assignee: Jim Gomes
> Priority: Minor
> Fix For: 1.4.0
>
> Original Estimate: 1 hour
> Time Spent: 1 hour, 30 minutes
> Remaining Estimate: 0 minutes
>
> The local message dispatcher in the ActiveMQ client checks for expired
> messages. If the message is determined to be expired, then it discards the
> message. There are some applications that still want expired messages to be
> passed on. Essentially, by turning off the client's checking of expired
> messages, it is delegating that responsibility to the broker to determine
> whether the message is delivered to the client. The application can then
> perform it's own application level logic to determine whether it wants to
> handle expired messages or not. The JMS spec is fairly loose regarding the
> expiration of messages. The JMS expiration time is more a means of cleaning
> up a broker's disk queues, and not primarily about stopping the routing of
> messages.
> A new configuration option should be added for consumers:
> "ignoreExpiration=true".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
