There is also the time stamp broker plugin that can help in this scenario to update the message time stamps to match the brokers clock: see: http://activemq.apache.org/timestampplugin.html
On 3 September 2010 19:35, vivekmshukla <[email protected]> wrote: > > I was able to figure out this issue. I just wanted to share my resolution in > case somebody faces similar situation in future. > > The issue was not related to domain or machine plateform at all. The issue > was due to the time difference in the system clocks on the domains where I > had my publisher and broker. The clock on the broker machine was ahead of > the publisher machine clock. So by the time the topic message was reaching > on the broker, it was already expired and my subscriber never picked the > messages. It worked perfectly fine where clocks on the machines were in > sync. In order to fix the issue, I ensured that machine clocks were in sync. > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-issue-across-multiple-domains-tp2525789p2526089.html > Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. > -- http://blog.garytully.com Open Source Integration http://fusesource.com
