activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Gomes (JIRA)" <j...@apache.org>
Subject [jira] Closed: (AMQNET-48) Submitting NMS Message with Expiration set to timespan fails
Date Wed, 13 Feb 2008 00:32:35 GMT

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

Jim Gomes closed AMQNET-48.
---------------------------

    Resolution: Fixed

> Submitting NMS Message with Expiration set to timespan fails
> ------------------------------------------------------------
>
>                 Key: AMQNET-48
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-48
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: ActiveMQ Client
>         Environment: Windows XP .NET 2.0
>            Reporter: Jim Gomes
>            Assignee: James Strachan
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message