I'm using the journaled JDBC approach to message persistence, with Oracle. It seems to work well most of the time. However, I'm finding that even after a normal shutdown a lock occasionally appears to be held on the activemq_lock table. This prevents ActiveMQ from starting up again on the next attempt.
Has anyone else seen this? Is there a way to avoid it? <bean id="broker" class="org.apache.activemq.broker.BrokerService" init-method="start" destroy-method="stop"> <property name="useJmx" value="true"/> <property name="persistent" value="true"/> <property name="transportConnectorURIs"> <list> <value>tcp://${host.name}:${jms.broker.port}</value> </list> </property> <property name="managementContext"> <bean class="org.apache.activemq.broker.jmx.ManagementContext"> <property name="connectorPort" value="${jms.jmx.port}"/> </bean> </property> <property name="persistenceAdapter"> <bean class="org.apache.activemq.store.PersistenceAdapterFactoryBean"> <property name="journalLogFiles" value="5"/> <property name="dataDirectory" value="${path.tomcat.home}/activemq-data"/> <property name="dataSource" ref="dataSource"/> </bean> </property> </bean> -- View this message in context: http://www.nabble.com/lock-on-Oracle-activemq_lock-table-tf4576911s2354.html#a13064911 Sent from the ActiveMQ - User mailing list archive at Nabble.com.