Bugs item #580207, was opened at 2002-07-11 11:04 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=580207&group_id=22866
Category: JBossMQ Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Gary Capps (gary_capps) >Assigned to: Andreas Schaefer (schaefera) Summary: Message expiration Initial Comment: When a message with a timeToLive value is generated by one workstation but consumed by different workstation, the message will often be incorrectly considered as "expired" by the consuming workstation if the two workstations' clocks are not synchronized. The problem appears to be that it is the *client* and not the *server* that calculates the expiration time and determines if that time has been reached. For example, if workstation "A" places messages in the queue with a 5000ms timeToLiveValue and the messages are consumed by workstation "B" (whose clock is 1 minute slower than workstation "A"'s), the messages will always be discarded as expired by "B". Both the originating time of the message and the determination of expiration should be done by the server, not the client. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=580207&group_id=22866 ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
