1 of 1 people found this helpful
>> Where is this timeout configured?
<< In conf/gatein/configuration.properties, check the value of the key gatein.jcr.index.cache.config which seems to be war:/conf/jcr/jbosscache/cluster/indexer-config.xml by default so it is located in deploy/gatein.ear/02portal.war/WEB-INF/conf/jcr/jbosscache/cluster/indexer-config.xml. The replication timeout is defined as attribute in the sync block so as you can see it is not set which means that it uses the default value which is 15 seconds, if you want to extend to 20 seconds just replace <sync /> with <sync replTimeout="20000" /> (more details here http://docs.jboss.org/jbosscache/3.2.1.GA/userguide_en/html_single/index.html)
>> What is the JBoss cache excatly trying to do?
<< Is try to replicate the list of jcr node to be indexed or removed from the indexes
>> And what could be the reason for this timeout?
<< A slow or overloaded bandwidth between the cluster nodes