[ openjms-Bugs-1217952 ] Clock drift between client and server affects msg expiration

Bugs item #1217952, was opened at 2005-06-10 14:21
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=1217952&group_id=54559

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: client
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Tim Anderson (tanderson)
Assigned to: Jim Alateras (jalateras)
Summary: Clock drift between client and server affects msg expiration

Initial Comment:
If there is a significant system clock mismatch between 
client and server hosts, messages sent with a time-to-live 
set will expire at times different to that indicated by their 
JMSExpiration property.
The expiration time is an absolute time expressed in 
milliseconds (i.e the JMSExpiration message property), 
and is determined in the client.
However, the server is responsble for expiring messages. 
If the server host's clock is advanced relative  to the client's, 
then messages will expire sooner than expected.
If the server host's clock is retarded relative to the client's, 
then messages will expire later than expected.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=1217952&group_id=54559


-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.  
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20