[gatein-issues] [JBoss JIRA] (GTNPORTAL-3404) The path of JCr index cache is hard coded in configuration.properties

Trong Tran (JIRA) issues at jboss.org
Mon Mar 17 07:20:10 EDT 2014


     [ https://issues.jboss.org/browse/GTNPORTAL-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Trong Tran resolved GTNPORTAL-3404.
-----------------------------------

    Resolution: Done

    
> The path of JCr index cache is hard coded in configuration.properties
> ---------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3404
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3404
>             Project: GateIn Portal
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.7.0.Final
>            Reporter: Racha Touzi
>            Assignee: Tuyen Nguyen The
>            Priority: Minor
>             Fix For: 3.8.0.Final
>
>   Original Estimate: 4 hours
>  Remaining Estimate: 4 hours
>
> The path 's   configuration of the JCR index cache is always configured in cluster mode  "/conf/jcr/infinispan/cluster/indexer-config.xml"  whatever the profil mode ( local or cluster) .
> But in local mode we don't really  need the transport configuration and the clustering configuration 
> {code}
> <infinispan
>       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>       xsi:schemaLocation="urn:infinispan:config:5.2 http://www.infinispan.org/schemas/infinispan-config-5.2.xsd"
>       xmlns="urn:infinispan:config:5.2">
>    <global>
>       <evictionScheduledExecutor factory="org.infinispan.executors.DefaultScheduledExecutorFactory">
>          <properties>
>             <property name="threadNamePrefix" value="EvictionThread"/>
>          </properties>
>       </evictionScheduledExecutor>
>       <globalJmxStatistics jmxDomain="platform.insp.cache.indexer" enabled="true" allowDuplicateDomains="true"/>
>       <transport transportClass="org.infinispan.remoting.transport.jgroups.JGroupsTransport" clusterName="${infinispan-cluster-name}" distributedSyncTimeout="20000">
>          <properties>
>             <property name="configurationFile" value="${gatein.jcr.jgroups.config}"/>
>          </properties>
>       </transport>
>    </global>
>    <default>
>       <clustering mode="replication">
>          <stateTransfer timeout="20000" fetchInMemoryState="false" />
>          <sync replTimeout="20000"/>
>       </clustering>
>       <locking isolationLevel="READ_COMMITTED" lockAcquisitionTimeout="20000" writeSkewCheck="false" concurrencyLevel="500" useLockStriping="false"/>
>       <transaction transactionManagerLookupClass="org.exoplatform.services.transaction.infinispan.JBossStandaloneJTAManagerLookup" syncRollbackPhase="true" syncCommitPhase="true" transactionMode="TRANSACTIONAL"/>
>       <jmxStatistics enabled="true"/>
>       <eviction strategy="NONE"/>
>             <loaders passivation="false" shared="false" preload="false">
>               <loader class="${infinispan-cachestore-classname}" fetchPersistentState="false" ignoreModifications="false" purgeOnStartup="false">
>                 <async enabled="false"/>
>               </loader>
>             </loaders>
>    </default>
> </infinispan>
> {code}
> So , The configuration of JCR Index cache must be one for local mode and one for Cluster mode ,
> the path must be 
> {code}
> gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/${gatein.jcr.config.type}/indexer-config.xml
> {code}
> instead of 
> {code}
> gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/cluster/indexer-config.xml
> {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


More information about the gatein-issues mailing list