problem replicating acl

[roberto_stellon]

I have a problem in replicating acl through two instances of alfresco 2.0 on
a jboss cluster.
We have only an instance of mysql 5.0 shared between the two jboss.
We use shared content and two separated indexes.

If I create a content on a jboss node it's immediately available on the other.
On the other side when I create, modify or remove user in group or create, modify remove an acl I find the operation only on jboss node on which the operation is performed.

I use standard configuration for ehcache
and I add only

index-recovery-context.xml
index-tracking-context.xml

that are the version present on alfresco 2.0 war bundle

could you help me because this point is a milestone for my study project
I'm graduated and I'm working for a project in a small farm in Italy that want to begin use alfresco for its business.

[derek]

Hi,

You need to follow the Wiki: http://wiki.alfresco.com/wiki/High_Availability_Configuration_V1.4_to_V2.1.  Your configuration - presuming that you are sharing the content as well - is exactly described by the page.  Read it thoroughly and feel free to post questions here about anything you don't understand.  It's good to experiment, but you should be aware of what all the beans do and what the various options are on the beans that you enable.  Use the javadocs for that: http://dev.alfresco.com/resource/docs/java/repository/

Regards

[roberto_stellon]

thank you derek for your answer.

We have the configuration present in
http://wiki.alfresco.com/wiki/High_Availability_Configuration_V1.4_to_V2.1
but the problem seems to be in configuration of ehcache.

In repository.jar of alfresco 2.0 community there is a configuration file
ehcache.xml; with this file in repository.jar, the replication of user, group and acl was not good.

We deleted this configuration file from repository.jar and the replication works

Could you tell me what will be this configuation in alfresco 2.1 that is now available ?

[derek]

Hi,

The Wiki is correct.  Removing the ehcache.xml from repository.jar is very wrong.

Regards

[roberto_stellon]

My configuration is with ehcache-custom.xml on extension,
in which I redefine the bold values

<cacheManagerPeerProviderFactory class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory" properties="peerDiscovery=automatic, multicastGroupAddress=[b]228.1.3.3[/b], multicastGroupPort=[b]4446[/b]" /> 

  <cacheManagerPeerListenerFactory class="net.sf.ehcache.distribution.RMICacheManagerPeerListenerFactory" properties="hostName=[b]192.168.0.1[/b], port=[b]43645[/b]" /> ‍‍‍

I deleted ehcache.xml from repository.jar
and the replication works

I decided to do this because I examined the version 2.1 and I didn't find the ehcache.xml in the new version
Could you  explain me why ?

[derek]

That file, ehcache.xml was meant to be unused as it was replaced with ehcache-default.xml, which is also defined in your repository.jar.  The mechanism that looks up the ehcache-custom.xml is the same mechanims that ignores ehcache.xml in favour of ehcache-default.xml, but a bug was introduced during the merge of the WCM code into the main code of V2.0 Open.  The fix went in for the V2.0.1 Enterprise release.

[roberto_stellon]

Thanks derek,

we don't use the V2.0.1 Enterprise release but V2.0 community edition

and seems that the problem was present

have a good day