Re: [solved] JDBC master/slave failover with DB2 fails due to long-running transaction

[Jarl <ja...@errors.no>]

After browsing code and bug reports for some hours, and doing some testing;
it seems all that is required is to set the (undocumented) configuration
property lockKeepAlivePeriod to 0, thus disabling the frequent updates.

This used to be the default but was changed to 30 seconds in 5.1/5.2. There
seems to be no ill effects in turning it off, so hopefully we're off the
hook.

   <persistenceAdapter>
     <jdbcPersistenceAdapter dataSource="#db2-ds" lockKeepAlivePeriod="0"/>
   </persistenceAdapter>

Thanks!
-Jarl




Jarl wrote:
> 
> We are running ActiveMQ 5.3.0 with a basic master/slave failover with JDBC
> persistence and database locking against a DB2 9.x database.
> 
> It seems DefaultDatabaseLocker gradually fills the transaction log
> (frequent updates, no commits), causing a regular failover. Increasing
> transaction log size to 1GB gives us about 48 hours uptime before
> failover.
> 
> I see this was brought up in april with no apparent resolution. Any
> pointers before we delve in and patch this ourselves? Is there some
> configuration we might have missed out on?
> 
-- 
View this message in context: http://old.nabble.com/-ActiveMQ-Cleanup-Timer--%28org.apache.activemq.store.jdbc.DefaultDatabaseLocker%3AkeepAlive%3A123%29---Failed-to-update-database-lock%3A-tp23252301p27452224.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.