[ https://issues.jboss.org/browse/WFWIP-89?page=com.atlassian.jira.plugin.s... ] Francesco Nigro commented on WFWIP-89: -------------------------------------- I have noticed these logs on the node 2 logs: {code:java} 11:54:36,296 ERROR [org.apache.activemq.artemis.core.server] (AMQ119000: Activation for server ActiveMQServerImpl::serverUUID=00d22eb4-9712-11e8-bc7a-fa163e5855f4) AMQ224000: Failure in initialisation: java.lang.IllegalStateException: java.sql.SQLException: IJ031013: Interrupted attempting lock: org.jboss.jca.adapters.jdbc.local.LocalManagedConnection@6f9f8b97 at org.apache.activemq.artemis.core.server.impl.jdbc.JdbcSharedStateManager.readState(JdbcSharedStateManager.java:338) [artemis-server-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT] at org.apache.activemq.artemis.core.server.impl.jdbc.JdbcNodeManager.readSharedState(JdbcNodeManager.java:523) [artemis-server-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT] at org.apache.activemq.artemis.core.server.impl.jdbc.JdbcNodeManager.awaitLiveNode(JdbcNodeManager.java:380) [artemis-server-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT] at org.apache.activemq.artemis.core.server.impl.SharedStoreBackupActivation.run(SharedStoreBackupActivation.java:77) [artemis-server-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT] at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$ActivationThread.run(ActiveMQServerImpl.java:3236) [artemis-server-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT] Caused by: java.sql.SQLException: IJ031013: Interrupted attempting lock: org.jboss.jca.adapters.jdbc.local.LocalManagedConnection@6f9f8b97 at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.tryLock(BaseWrapperManagedConnection.java:402) at org.jboss.jca.adapters.jdbc.WrappedConnection.lock(WrappedConnection.java:161) at org.jboss.jca.adapters.jdbc.WrappedConnection.setTransactionIsolation(WrappedConnection.java:1007) at org.apache.activemq.artemis.core.server.impl.jdbc.JdbcSharedStateManager.readState(JdbcSharedStateManager.java:316) [artemis-server-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT] ... 4 more {code} It shows that the backup node isn't able to come up because isn't able to read the state of the live node due to an issue of the EAP SQL connection pools. I think that's not a broker issue and it looks like a timing issue with the reaper thread used by the connection pool. I believe that is intermittent, given that is dependent by timing. -- This message was sent by Atlassian JIRA (v7.5.0#75005)