activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Shepherd (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMQ-4382) jdbcPersistenceAdapter does not use lockCreateStatement value
Date Mon, 18 Mar 2013 05:44:15 GMT
Jason Shepherd created AMQ-4382:
-----------------------------------

             Summary: jdbcPersistenceAdapter does not use lockCreateStatement value
                 Key: AMQ-4382
                 URL: https://issues.apache.org/jira/browse/AMQ-4382
             Project: ActiveMQ
          Issue Type: Bug
          Components: Message Store
    Affects Versions: 5.7.0
         Environment: 5.7.0.fuse-71-047-s023
Oracle Database
            Reporter: Jason Shepherd
            Priority: Minor


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

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message