You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by ogroef <og...@gmail.com> on 2012/03/30 18:59:22 UTC
JMSExpiration is set to a relative data starting from 01/01/1970
All
ActiveMQ 5.5.0.
JRE 1.6.0
When a message is send with the topicpublisher the messages are send fine.
My problem has something to do wiht the JMSExpiration Header property.
Method used. topicpublisher -> publish (message, persistence, priority,
*timetolive*)
the timetolive is passed as 5000 millisec (5 seconds)
When the message is consumed the JMSExpiration is having the value:
SYSDATE+5000 millisecs
Example:
TimeToLive: 5000
Expected JMSExpiration: 5000
Actual JMSExpiration: 1333138515018 (this is the amount of millisecs
starting to count from 01/01/1970).
Question:
Is there any way that I can get the 5000 in the JMSExpiration instead of the
1333138515018?
PS: The systemdate is set correctly and pointing to the moment the message
is send.
Kind Regards
--
View this message in context: http://activemq.2283324.n4.nabble.com/JMSExpiration-is-set-to-a-relative-data-starting-from-01-01-1970-tp4519687p4519687.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: JMSExpiration is set to a relative data starting from 01/01/1970
Posted by Gary Tully <ga...@gmail.com>.
http://en.wikipedia.org/wiki/Unix_time
On 5 April 2012 15:54, ogroef <og...@gmail.com> wrote:
> Hi
>
> When I pass (in publish method) as TimeToLive parameter 5000 (5 sec).
>
> The JMS-Expiration time is calculated from 01/Jan/1970 in stead of from the
> send date of the message.
>
> Regards
> Olivier
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/JMSExpiration-is-set-to-a-relative-data-starting-from-01-01-1970-tp4519687p4535074.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
--
http://fusesource.com
http://blog.garytully.com
Re: JMSExpiration is set to a relative data starting from
01/01/1970
Posted by ogroef <og...@gmail.com>.
Hi
When I pass (in publish method) as TimeToLive parameter 5000 (5 sec).
The JMS-Expiration time is calculated from 01/Jan/1970 in stead of from the
send date of the message.
Regards
Olivier
--
View this message in context: http://activemq.2283324.n4.nabble.com/JMSExpiration-is-set-to-a-relative-data-starting-from-01-01-1970-tp4519687p4535074.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: JMSExpiration is set to a relative data starting from 01/01/1970
Posted by Gary Tully <ga...@gmail.com>.
that is in accordance with the jms spec[1] see section: 3.4.9
http://docs.oracle.com/cd/E19957-01/816-5904-10/816-5904-10.pdf
why is it a problem?
On 3 April 2012 10:24, ogroef <og...@gmail.com> wrote:
> Anybody please, I am looking for more input on this.
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/JMSExpiration-is-set-to-a-relative-data-starting-from-01-01-1970-tp4519687p4528235.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
--
http://fusesource.com
http://blog.garytully.com
Re: JMSExpiration is set to a relative data starting from
01/01/1970
Posted by ogroef <og...@gmail.com>.
Anybody please, I am looking for more input on this.
--
View this message in context: http://activemq.2283324.n4.nabble.com/JMSExpiration-is-set-to-a-relative-data-starting-from-01-01-1970-tp4519687p4528235.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.