activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino" <hi...@hiramchirino.com>
Subject Re: Client/Server machines synchronization
Date Fri, 28 Sep 2007 15:14:06 GMT
Hi Folamour..

Yes the issue is related.  With the fix described in that issue the
timestamp is set by the broker instead of the clients so there are
fewer machines that need to be in sync.  Now, if multiple brokers are
being used, those brokers still need to keep their time in sync.

On 9/28/07, Folamour <mister.melba@free.fr> wrote:
>
> Dear all,
>
> Whenever the system clock of the host running ActiveMQ is a few minutes
> later than the client machines, the messages sent by the clients generate
> timeout exceptions.
> ActiveMQ seems to consider the incoming messages as already expired when
> they come in.
> Everything's fine when the clients are later than the server.
>
> Is it a configuration issue?
> Is it related to https://issues.apache.org/activemq/browse/AMQ-1160 ?
>
> Thanks in advance
> Rgds
> F.
>
> Environment
> Server: ActiveMQ 4.1.0
> Client: via Lingo 1.3
> Deployment: worldwide, would be very difficult to synchronize all machines
> --
> View this message in context: http://www.nabble.com/Client-Server-machines-synchronization-tf4535027s2354.html#a12942158
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>
>


-- 
Regards,
Hiram

Blog: http://hiramchirino.com

Mime
View raw message