activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rodrigo Ramos <crackdu...@gmail.com>
Subject Timer already cancelled and KahaDB: Recovering checkpoint thread after death
Date Wed, 22 Jan 2014 23:21:31 GMT
I´m getting this error from my brokers:

10.142.176.106:40672@61617

2014-01-21 19:52:00,507 | WARN  | Transport Connection to: tcp://
10.142.176.106:40701 failed: java.io.IOException: Unexpected error occured:
java.lang.IllegalStateException: Timer already cancelled. |
org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ
Transport: tcp:///10.142.176.106:40701@61617

2014-01-21 19:52:01,508 | WARN  | Transport Connection to: tcp://
10.142.176.106:40726 failed: java.io.IOException: Unexpected error occured:
java.lang.IllegalStateException: Timer already cancelled. |
org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ
Transport: tcp:///10.142.176.106:40726@61617

2014-01-21 19:52:02,508 | WARN  | Transport Connection to: tcp://
10.142.176.106:40754 failed: java.io.IOException: Unexpected error occured:
java.lang.IllegalStateException: Timer already cancelled. |
org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ
Transport: tcp:///10.142.176.106:40754@61617

2014-01-21 19:52:06,508 | WARN  | Transport Connection to: tcp://
10.142.176.106:40848 failed: java.io.IOException: Unexpected error occured:
java.lang.IllegalStateException: Timer already cancelled. |
org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ
Transport: tcp:///10.142.176.106:40848@61617

2014-01-21 19:52:06,744 | INFO  | KahaDB: Recovering checkpoint thread
after death | org.apache.activemq.store.kahadb.MessageDatabase | ActiveMQ
Transport: tcp:///10.142.176.106:37672@61617


does somebody know these error?

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message