activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r851880 - in /websites/production/activemq/content: cache/main.pageCache pluggable-storage-lockers.html
Date Mon, 25 Feb 2013 14:21:59 GMT
Author: buildbot
Date: Mon Feb 25 14:21:58 2013
New Revision: 851880

Log:
Production update by buildbot for activemq

Modified:
    websites/production/activemq/content/cache/main.pageCache
    websites/production/activemq/content/pluggable-storage-lockers.html

Modified: websites/production/activemq/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/activemq/content/pluggable-storage-lockers.html
==============================================================================
--- websites/production/activemq/content/pluggable-storage-lockers.html (original)
+++ websites/production/activemq/content/pluggable-storage-lockers.html Mon Feb 25 14:21:58
2013
@@ -138,15 +138,15 @@ In addition, where the database supports
 
 <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
 <pre class="code-java">&lt;persistenceAdapter&gt;
-	&lt;jdbcPersistenceAdapter dataDirectory=<span class="code-quote">"${activemq.data}"</span>
dataSource=<span class="code-quote">"#mysql-ds"</span> lockKeepAlivePeriod=<span
class="code-quote">"10000"</span>&gt;
+	&lt;jdbcPersistenceAdapter dataDirectory=<span class="code-quote">"${activemq.data}"</span>
dataSource=<span class="code-quote">"#mysql-ds"</span> lockKeepAlivePeriod=<span
class="code-quote">"5000"</span>&gt;
 		&lt;locker&gt;
-			&lt;lease-database-locker lockAcquireSleepInterval=<span class="code-quote">"5000"</span>/&gt;
+			&lt;lease-database-locker lockAcquireSleepInterval=<span class="code-quote">"10000"</span>/&gt;
 		&lt;/locker&gt;
 	&lt;/jdbcPersistenceAdapter&gt;
 &lt;/persistenceAdapter&gt;</pre>
 </div></div>
 
-<p>The lease based lock is acquired by blocking at start and retained by the keepAlivePeriod.
To retain, the lease is extended by the lockAcquireSleepInterval, so in theory the master
is always (lockAcquireSleepInterval-lockKeepAlivePeriod) ahead of the slave w.r.t the lease.<br
clear="none">
+<p>The lease based lock is acquired by blocking at start and retained by the keepAlivePeriod.
To retain, the lease is extended by the lockAcquireSleepInterval, so in theory the master
is always (lockAcquireSleepInterval-lockKeepAlivePeriod) ahead of the slave w.r.t the lease.
It is imperative that lockAcquireSleepInterval &gt; lockKeepAlivePeriod, to ensure the
lease is always current.<br clear="none">
 In the simplest case, the clocks between master and slave must be in sync for this solution
to work properly. If the clocks cannot be in sync, the locker can use the system time from
the database CURRENT TIME and adjust the timeouts in accordance with their local variance
from the db system time. If maxAllowableDiffFromDBTime is &gt; 0 the local periods will
be adjusted by any delta that exceeds maxAllowableDiffFromDBTime.</p>
           </div>
         </td>



Mime
View raw message