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

Posted to dev@activemq.apache.org by Shine <ac...@club.webhop.org> on 2012/02/23 08:58:00 UTC

TimeToLive vs. Expiration

Hi,

I am using the latest version of NMS to connect to an ActiveMQ Server
(version 5.5.1). All messages get a time-to-live of 60 seconds.

if the time on the sender pc is incorrect (more than 60 seconds in the
past), the server drops the messages, because the property NMSTimeToLive is
not really "Time-to-live"; it becomes an expiration date.

Is it possible to set a real "Time-to-live" (Arrivaltime on the server +
NMSTimeToLive)?


--
View this message in context: http://activemq.2283324.n4.nabble.com/TimeToLive-vs-Expiration-tp4413088p4413088.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: TimeToLive vs. Expiration

Posted by Shine <ac...@club.webhop.org>.

hi gtully,

that is what i need .. thanks.

--
View this message in context: http://activemq.2283324.n4.nabble.com/TimeToLive-vs-Expiration-tp4413088p4413720.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: TimeToLive vs. Expiration

Posted by Gary Tully <ga...@gmail.com>.

have a peek at the http://activemq.apache.org/timestampplugin.html

On 23 February 2012 07:58, Shine <ac...@club.webhop.org> wrote:
> Hi,
>
> I am using the latest version of NMS to connect to an ActiveMQ Server
> (version 5.5.1). All messages get a time-to-live of 60 seconds.
>
> if the time on the sender pc is incorrect (more than 60 seconds in the
> past), the server drops the messages, because the property NMSTimeToLive is
> not really "Time-to-live"; it becomes an expiration date.
>
> Is it possible to set a real "Time-to-live" (Arrivaltime on the server +
> NMSTimeToLive)?
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/TimeToLive-vs-Expiration-tp4413088p4413088.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.



-- 
http://fusesource.com
http://blog.garytully.com