[jira] Updated: (AMQNET-253) STOMP: Expiration date of message are corrupt if the producer 'timestamping' is disabled

["Andreas Ländle (JIRA)" <ji...@apache.org>]

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

Andreas Ländle updated AMQNET-253:
----------------------------------

    Summary: STOMP: Expiration date of message are corrupt if the producer 'timestamping' is disabled  (was: Expiration date of message are corrupt if the producer 'timestamping' is disabled)

> 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
>            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).
> 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.