[
https://issues.jboss.org/browse/GTNPORTAL-2801?page=com.atlassian.jira.pl...
]
Marek Posolda commented on GTNPORTAL-2801:
------------------------------------------
Update: It seems that my previous comment could be ignored. The whole issue is eXo JCR
bug, which causes that JBC items with index changes are not properly purged on slave nodes
after applying (just on master node). There is eXo JCR jira here:
https://jira.exoplatform.org/browse/JCR-2269 . After fixing this and update JCR, we
won't need any eviction configuration in JBC config or some hack setups to be
documented in performance guide.
Add eviction to indexer-config.xml
----------------------------------
Key: GTNPORTAL-2801
URL:
https://issues.jboss.org/browse/GTNPORTAL-2801
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JCR integration
Affects Versions: 3.5.0.Final
Reporter: Toshiya Kobayashi
gatein.ear/portal.war/WEB-INF/conf/jcr/jbosscache/cluster/indexer-config.xml doesn't
have eviction configuration. It may cause a memory leak in slave nodes.
{code:xml}
<jbosscache
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="urn:jboss:jbosscache-core:config:3.1">
<locking useLockStriping="false" concurrencyLevel="64"
lockParentForChildInsertRemove="false"
lockAcquisitionTimeout="20000"/>
<!-- Configure the TransactionManager -->
<transaction
transactionManagerLookupClass="org.jboss.cache.transaction.JBossStandaloneJTAManagerLookup"/>
<clustering mode="replication"
clusterName="${jboss.partition.name:DefaultPartition}-${jbosscache-cluster-name}">
<stateRetrieval timeout="20000"
fetchInMemoryState="false"/>
<jgroupsConfig
configFile="jgroups/gatein-${gatein.default.jgroups.stack:udp}.xml"/>
<sync/>
</clustering>
</jbosscache>
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira