You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Jim Gomes (JIRA)" <ji...@apache.org> on 2011/02/02 18:09:29 UTC

[jira] Updated: (AMQNET-48) Submitting NMS Message with Expiration set to timespan fails

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

Jim Gomes updated AMQNET-48:
----------------------------

    Parent:     (was: AMQNET-68)

> Submitting NMS Message with Expiration set to timespan fails
> ------------------------------------------------------------
>
>                 Key: AMQNET-48
>                 URL: https://issues.apache.org/jira/browse/AMQNET-48
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: ActiveMQ
>         Environment: Windows XP .NET 2.0
>            Reporter: Jim Gomes
>            Assignee: james strachan
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> There is a bug in the NMSExpiration property of the ActiveMQMessage.  The MessageProducer class deals with the expiration of messages in terms of "time to live" which is a relative timespan.  However, ActiveMQ deals with the expiration of messages in terms of an absolute date/time.  The NMS client API needs to be consistent in dealing with "time to live" timespans.  Additionally, there is a bug in the DateUtils class when converting from .NET date/time format to Java date/time format.
> Symptoms of these bugs may include the inability to submit a message to ActiveMQ when the NMSExpiration field is set to anything other than 0.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira