activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From khandelwalanuj <khandelwal.anu...@gmail.com>
Subject Durable client removal caused broker to shutdown in replicated leveldb
Date Wed, 19 Aug 2015 07:10:12 GMT
hi,

I am using replicated leveldb with ActiveMQ.5.11.1. We have recently
observed an issue where when client connection removal caused broker to
shutdown. This is very weird. The client is a durable consumer who uses
transactions and calls commit after each 10 messages. 

Can someone suggest what should I do here and what caused this exception ? 

Logs: 


[20150817 18:25:06.016 EDT (ActiveMQ BrokerService[mqbroker] Task-9)
org.apache.activemq.broker.util.LoggingBrokerPlugin#removeConnection 241
INFO] -
Removing Connection: ConnectionInfo {commandId = 1, responseRequired = true,
connectionId = ID:app1.ia55.net-49035-1439207692004-1:3, clientId =
milestoneClient, clientIp = tcp://a.b.c.d:15615, userName = null, password =
*****, brokerPath = null, brokerMasterConnector
= false, manageable = true, clientMaster = true, faultTolerant = true,
failoverReconnect = true}

[20150817 18:25:06.016 EDT (ActiveMQ BrokerService[mqbroker] Task-9)
org.apache.activemq.broker.TransactionBroker#removeConnection 325 WARN] -
ERROR R
olling back disconnected client's transactions: 
org.apache.activemq.broker.SuppressReplyException: ShutdownBrokerInitiated
        at
org.apache.activemq.util.DefaultIOExceptionHandler.handle(DefaultIOExceptionHandler.java:151)
        at
org.apache.activemq.broker.BrokerService.handleIOException(BrokerService.java:2618)
        at
org.apache.activemq.leveldb.LevelDBStore.verify_running(LevelDBStore.scala:521)
        at
org.apache.activemq.leveldb.LevelDBStore.rollback(LevelDBStore.scala:566)
        at
org.apache.activemq.leveldb.LevelDBStore$LevelDBTransactionStore.rollback(LevelDBStore.scala:1124)
        at
org.apache.activemq.transaction.LocalTransaction.rollback(LocalTransaction.java:94)
        at
org.apache.activemq.broker.TransactionBroker.removeConnection(TransactionBroker.java:323)
        at
org.apache.activemq.broker.BrokerFilter.removeConnection(BrokerFilter.java:132)
        at
org.apache.activemq.broker.MutableBrokerFilter.removeConnection(MutableBrokerFilter.java:137)
        at
org.apache.activemq.broker.util.LoggingBrokerPlugin.removeConnection(LoggingBrokerPlugin.java:243)
        at
org.apache.activemq.broker.MutableBrokerFilter.removeConnection(MutableBrokerFilter.java:137)
        at
org.apache.activemq.broker.TransportConnection.processRemoveConnection(TransportConnection.java:862)
        at
org.apache.activemq.broker.TransportConnection.doStop(TransportConnection.java:1187)
        at
org.apache.activemq.broker.TransportConnection$4.run(TransportConnection.java:1117)
        at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.IOException: Not running
        at
org.apache.activemq.leveldb.LevelDBStore.verify_running(LevelDBStore.scala:517)


Thanks,
Anuj



--
View this message in context: http://activemq.2283324.n4.nabble.com/Durable-client-removal-caused-broker-to-shutdown-in-replicated-leveldb-tp4701209.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
View raw message