activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] Commented: (AMQNET-253) STOMP: Expiration date of message are corrupt if the producer 'timestamping' is disabled
Date Fri, 21 May 2010 13:52:49 GMT


Timothy Bish commented on AMQNET-253:

There were several changes made in the NMS.Stomp trunk for this issue
which may resolve you problem.  

> STOMP: Expiration date of message are corrupt if the producer 'timestamping' is disabled
> ----------------------------------------------------------------------------------------
>                 Key: AMQNET-253
>                 URL:
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: NMS
>    Affects Versions: 1.2.0
>            Reporter: Andreas Ländle
>            Assignee: Jim Gomes
>            Priority: Minor
> Please Note: Since NMS has dependencies between the NMSTimestamp and NMSTimeToLive properties
- Disabling the timestamps on the producer results in corrupted expiration dates of the messages!
> Reproduction:
> Set the TTL of a message to 1 hour - send this message via a producer which has DisableMessageTimestamp=true.
> Now take a look at the "expires" field of the transfered message - it's value is all
to small (and so the broker would discard the message immediately).
> (previous to the fix for the TimeStamp
of a message was set during construction - so the interconnection of Timestamp and TTL wasn't
so obvious)
> Workaround:
> I have worked around this issue with a dirty hack - i just bypass the TTL-Timespan.
> var stompMessage = nmsMessage as BaseMessage;
> if (stompMessage != null)
> { stompMessage.Expiration = DateUtils.ToJavaTimeUtc(myExpirationDate); } 
> Please let me know if i was unclear or if you need more information.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message