At first we only use the default jdbcPersistenceAdapter (without the lease lock) -> not surviving a network disconnection
Then we tried to change the wrapper.conf to restart the AMQ service -> not working also wrapper.filter.trigger.1=Failed to start Apache ActiveMQ wrapper.filter.action.1=RESTART Then we tried the jdbc lease lock following the configuration found on google but the majority of these posts share the wrong configuration -> the service survived a network disconnection but the master/slave lock flapped every 10 sec. wrong jdbc lease lock: lockAcquireSleepInterval="5000" + lockKeepAlivePeriod="10000" good jdbc lease lock: lockAcquireSleepInterval="10000" + lockKeepAlivePeriod="5000" -- View this message in context: http://activemq.2283324.n4.nabble.com/AMQ-service-stops-on-network-disconnection-tp4728212p4728310.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
