[
https://issues.apache.org/activemq/browse/AMQNET-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59509#action_59509
]
Timothy Bish commented on AMQNET-253:
-------------------------------------
The best explanation would be an NUnit test case that demonstrates the issue.
I can't comment further until I have some time to look at the code again. We
welcome patches with associated test cases if you have a fix in mind.
> STOMP: Expiration date of message are corrupt if the producer 'timestamping'
> is disabled
> ----------------------------------------------------------------------------------------
>
> Key: AMQNET-253
> URL: https://issues.apache.org/activemq/browse/AMQNET-253
> 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 https://issues.apache.org/activemq/browse/AMQNET-245
> 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.
