You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Nathan Mittler (JIRA)" <ji...@apache.org> on 2006/11/27 02:43:02 UTC
[jira] Commented: (AMQCPP-14) CMSExpiration not handled properly in
ActiveMQProducer
[ https://issues.apache.org/activemq/browse/AMQCPP-14?page=comments#action_37560 ]
Nathan Mittler commented on AMQCPP-14:
--------------------------------------
I have committed changes to trunk. I'd like to create a new integration test to prove that the expiration works properly before I mark this issue as resolved.
> 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: Nathan Mittler
> 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