You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by juanlopez <ju...@gmail.com> on 2013/08/27 16:18:11 UTC

After change time in server the ActiveMQ 5.6 not work

This is the scenario

LSB Version:
:core-4.0-amd64:core-4.0-ia32:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-ia32:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-ia32:printing-4.0-noarch
Distributor ID:	CentOS
Description:	CentOS release 5.8 (Final)


Activemq 5.6 - Mode cluster and fileover crossed, and share the same
filesystem

Act1---Act2Failover
Act2---Act1Failover

Jboss 6.1 & cliente (activemq.ra-ra)

I had 2 Jboss servers with one ActiveMQ per server, the time between them
was syncronized (I had the same time in both servers). On day we changed the
time of Server1 10 seconds, but everything was working well. But when we
decided to re-sync both servers time, ActiveMQ started to fail with the
following error:


2013-08-26 00:00:00,369 ERROR
[org.apache.activemq.ra.ActiveMQEndpointWorker] (pool-1-thread-12) Endpoint
will try to reconnect to the JMS broker in 30 seconds
2013-08-26 00:00:14,885 ERROR
[org.apache.activemq.ra.ActiveMQEndpointWorker] (pool-1-thread-6) Failed to
connect to broker
[failover:(tcp://192.168.10.32:61616?socketBufferSize=131072&ioBufferSize=16348,tcp://192.168.10.33:61617?socketBufferSize=131072&ioBufferSize=16348)?randomize=false&maxReconnectDelay=1000&maxReconnectAttempts=10&timeout=3000&jms.redeliveryPolicy.initialRedeliveryDelay=60000&jms.redeliveryPolicy.redeliveryDelay=60000&jms.redeliveryPolicy.maximumRedeliveries=6]:
Failover timeout of 3000 ms reached.: javax.jms.JMSException: Failover
timeout of 3000 ms reached.

Exist cache or temp folder , wich contains the time of message send to
broker, or any configuration related to communicaction with this Activemq in
mode cluster or failover?

Regards



--
View this message in context: http://activemq.2283324.n4.nabble.com/After-change-time-in-server-the-ActiveMQ-5-6-not-work-tp4670737.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: After change time in server the ActiveMQ 5.6 not work

Posted by Christian Posta <ch...@gmail.com>.
Weird. Have you tried without failover? Can you make any connections to the
brokers?
Or does this happen randomly?


On Tue, Aug 27, 2013 at 7:18 AM, juanlopez <ju...@gmail.com> wrote:

> This is the scenario
>
> LSB Version:
>
> :core-4.0-amd64:core-4.0-ia32:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-ia32:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-ia32:printing-4.0-noarch
> Distributor ID: CentOS
> Description:    CentOS release 5.8 (Final)
>
>
> Activemq 5.6 - Mode cluster and fileover crossed, and share the same
> filesystem
>
> Act1---Act2Failover
> Act2---Act1Failover
>
> Jboss 6.1 & cliente (activemq.ra-ra)
>
> I had 2 Jboss servers with one ActiveMQ per server, the time between them
> was syncronized (I had the same time in both servers). On day we changed
> the
> time of Server1 10 seconds, but everything was working well. But when we
> decided to re-sync both servers time, ActiveMQ started to fail with the
> following error:
>
>
> 2013-08-26 00:00:00,369 ERROR
> [org.apache.activemq.ra.ActiveMQEndpointWorker] (pool-1-thread-12) Endpoint
> will try to reconnect to the JMS broker in 30 seconds
> 2013-08-26 00:00:14,885 ERROR
> [org.apache.activemq.ra.ActiveMQEndpointWorker] (pool-1-thread-6) Failed to
> connect to broker
> [failover:(tcp://
> 192.168.10.32:61616?socketBufferSize=131072&ioBufferSize=16348,tcp://192.168.10.33:61617?socketBufferSize=131072&ioBufferSize=16348)?randomize=false&maxReconnectDelay=1000&maxReconnectAttempts=10&timeout=3000&jms.redeliveryPolicy.initialRedeliveryDelay=60000&jms.redeliveryPolicy.redeliveryDelay=60000&jms.redeliveryPolicy.maximumRedeliveries=6
> ]:
> Failover timeout of 3000 ms reached.: javax.jms.JMSException: Failover
> timeout of 3000 ms reached.
>
> Exist cache or temp folder , wich contains the time of message send to
> broker, or any configuration related to communicaction with this Activemq
> in
> mode cluster or failover?
>
> Regards
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/After-change-time-in-server-the-ActiveMQ-5-6-not-work-tp4670737.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>



-- 
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta