Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <4316645.2361274714333096.JavaMail.jira@thor>
Date: Mon, 24 May 2010 11:18:53 -0400 (EDT)
From: "Timothy Bish (JIRA)" <jira+amqnet@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Resolved: (AMQNET-253) STOMP: Expiration date of message are
 corrupt if the producer 'timestamping' is disabled
In-Reply-To: <21712191.971274447508609.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/activemq/browse/AMQNET-253?page=3Dcom.atla=
ssian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish resolved AMQNET-253.
---------------------------------

    Fix Version/s: 1.3.0
       Resolution: Fixed

I believe I've fixed this in Trunk so that it works the way you'd expect.  =
I also fixed the send methods such that they now honor the TimeToLive setti=
ng in MessageProducer which defaults to Zero of course.

> STOMP: Expiration date of message are corrupt if the producer 'timestampi=
ng' 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=C3=A4ndle
>            Assignee: Timothy Bish
>            Priority: Minor
>             Fix For: 1.3.0
>
>
> Please Note: Since NMS has dependencies between the NMSTimestamp and NMST=
imeToLive 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 whi=
ch has DisableMessageTimestamp=3Dtrue.
> Now take a look at the "expires" field of the transfered message - it's v=
alue is all to small (and so the broker would discard the message immediate=
ly).
> (previous to the fix for https://issues.apache.org/activemq/browse/AMQNET=
-245 the TimeStamp of a message was set during construction - so the interc=
onnection 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 =3D nmsMessage as BaseMessage;
> if (stompMessage !=3D null)
> { stompMessage.Expiration =3D DateUtils.ToJavaTimeUtc(myExpirationDate); =
}=20
> Please let me know if i was unclear or if you need more information.

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