"Cannot send, channel has already failed" messages

We are using Version 5.6.0 in an "JDBC Master Slave" configuration. From time to time we get the following messages: tcp://10.55.205.243:35530 failed: org.apache.activemq.transport.InactivityIOException: Cannot send, channel has already failed: tcp://10.55.205.243:35530 Sometime this messages come

Messages about "Store limit" with JDBCPersistenceAdapter

We are using Version 5.6.0 in an "JDBC Master Slave" configuration. When the broker comes up it shows the following log messages: (org.apache.activemq.store.kahadb.plist.PListStore:331) # PListStore:[E:\somepath\activemq-data\jdbcBroker\tmp_storage ] started (org.apache.activemq.broker.BrokerServi

Messages about tmp_storage with JDBCPersistenceAdapter

We are using Version 5.6.0 in an "JDBC Master Slave" configuration. When the broker comes up it shows the following log messages: (org.apache.activemq.store.kahadb.plist.PListStore:331) # PListStore:[E:\somepath\activemq-data\jdbcBroker\tmp_storage ] started (org.apache.activemq.broker.BrokerServi

Broker stops after loosing database connection

We are using Version 5.6.0 in an "JDBC Master Slave" configuration. In the case that the master looses the connection to the database it stops the broker. This is the part of JDBCPersistenceAdapter where it happens: ... protected void databaseLockKeepAlive() { boolean stop = false;