SourceForge.net
2005-06-10 04:21:41 UTC
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
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