[ https://issues.apache.org/activemq/browse/AMQCPP-14?page=all ]
Timothy Bish resolved AMQCPP-14.
--------------------------------
Resolution: Fixed
Changes are applied in trunk to address this issue
The producer now correctly sets the timestamp and expiration value when the
timeToLive value is specified.
The consumer now throws away expired messages when they arrive.
Unit tests and Integration tests are now in that tests this functionality.
> CMSExpiration not handled properly in ActiveMQProducer
> ------------------------------------------------------
>
> Key: AMQCPP-14
> URL: https://issues.apache.org/activemq/browse/AMQCPP-14
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: CMS Impl
> Affects Versions: 1.0
> Environment: All
> Reporter: Nathan Mittler
> Assigned To: Timothy Bish
> Priority: Minor
> Fix For: 1.1
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> ActiveMQProducer.send method is overwriting the CMSExpiration in the message
> with its default timeToLive value. This is incorrect - it should set the
> expiry to (expiry + timeToLive). An example of this is in ActiveMQ's
> ActiveMQSession:
> https://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/ActiveMQSession.java
> A work-around is to specify the timeToLive value in the producer.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
