[jira] Resolved: (AMQNET-268) Add configuration option to have the client ignore the message expiration time.

["Jim Gomes (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/activemq/browse/AMQNET-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jim Gomes resolved AMQNET-268.
------------------------------

    Resolution: Fixed

A new destination parameter option has been added.  To allow a client application to receive messages that the broker has sent to the client, but may have expired while on the client waiting to be dispatched, use the following parameter on the destination address:

{{queue://msgqueuename?consumer.nms.ignoreExpiration=true}}

The parameter is case-insensitive, and defaults to 'false', which means expired messages will not be dispatched by the NMS client.

> 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
>  Remaining Estimate: 1 hour
>
> 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.