Have a read of http://mail-archives.apache.org/mod_mbox/activemq-users/201008.mbox/%[email protected]%3E
The lockDataSource attribute on the jdbcpersistence adapter lets you specify a separate source for the lock Also note https://issues.apache.org/jira/browse/AMQ-3654, there is a new lease based locker that replaces the open transaction with a periodic lease update and poll. On 16 July 2012 20:58, bnorton <[email protected]> wrote: > We have HA ActiveMQ 5.5 brokers running against SQL Server 2008. My issue is > that the transaction logs never get cleared out due to an open transaction. > Our logs are growing at a rate of 1 GB per hour since the transaction never > commits. I have to manually fail-over the activeMQ servers so our tranlog > backup process can remove the logs. > > Is there any way to force AMQ to commit the transaction on a schedule? > > Is the database locker keeping the transaction from committing and will > configuring it to use a different database fix the issue? > If that is the case how do I go about configuring activemq to use a separate > datasource specifically a different database for locking? I've been trying > to find an example and can not come up with anything. The only idea I have > is to set my own lockCreateStatement. > > This has been driving me nuts for the last 2 days and I can't come up with > anything concrete. > > Thanks > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-causing-huge-transaction-logs-on-mssql-2008-tp4654069.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://fusesource.com http://blog.garytully.com
