[AMQ-4382] jdbcPersistenceAdapter does not use lockCreateStatement value

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 5.7.0
• Component/s: Message Store

Environment

5.7.0.fuse-71-047-s023
Oracle Database

• Assignee: Unassigned
• Reporter: Jason Shepherd
• Created: 18/Mar/13 05:42
• Updated: 24/Jul/13 16:20
• Resolved: 24/Jul/13 16:20

Description

When using a jdbcPersistenceAdaptor and adapter with lockCreateStatements set, this is not used by org.apache.activemq.store.jdbc.DefaultDatabaseLocker.

<persistenceAdapter>
<jdbcPersistenceAdapter createTablesOnStartup="false"
lockKeepAlivePeriod="10000"
lockAcquireSleepInterval="5000"
cleanupPeriod="0"
dataSource="#oracle-ds-tomcat-dbcp"
maxRows="200">
<statements>
<statements lockCreateStatement="SELECT * FROM ACTIVEMQ_LOCK FOR UPDATE NOWAIT" />
</statements>
</jdbcPersistenceAdapter>
</persistenceAdapter>

In activemq.log:

DEBUG | Locking Query is SELECT * FROM ACTIVEMQ_LOCK | org.apache.activemq.store.jdbc.DefaultDatabaseLocker | main

Issue Links

• duplicates: AMQ-4581 JDBCPersistenceAdapter can ignore statements settings depending on configuration order.