Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Date: Fri, 3 Sep 2010 11:35:44 -0700 (PDT)
From: vivekmshukla <vshukla@epicor.com>
To: dev@activemq.apache.org
Message-ID: <1283538944922-2526089.post@n4.nabble.com>
In-Reply-To: <1283525299509-2525789.post@n4.nabble.com>
References: <1283525299509-2525789.post@n4.nabble.com>
Subject: Re: ActiveMQ issue across multiple domains
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


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.