JDBCPersistenceAdapter lockDataSource property (and other settings) should
appear on the SQLServer persistence page
-------------------------------------------------------------------------------------------------------------------
Key: AMQ-3304
URL: https://issues.apache.org/jira/browse/AMQ-3304
Project: ActiveMQ
Issue Type: Improvement
Components: Documentation
Affects Versions: 5.5.0
Reporter: Arnaud BRAND
Priority: Minor
When using the JDBCPersistenceAdapter with SQLServer the use of the
lockDataSource property is mandatory, or else the transaction log will fill up
(wether the db is in simple or full recovery mode doesn't change anything), and
the broker will eventually crash.
The page http://activemq.apache.org/sqlserver.html should clearly state that
the lockDataSource should be used and should point to another database.
Additionnaly, this page could give another configuration tweak for SQLServer
which results in a sensible performance improvement when queues are quite full
(>50000 messages in our configuration):
{code:xml}
<statements>
<statements findNextMessagesStatement="SELECT TOP 5 ID, MSG FROM
ACTIVEMQ_MSGS WHERE CONTAINER=? AND ID > ? ORDER BY ID"/>
</statements>
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
