Looking at the logs, I also see something a bit weird: 2011-06-16 11:45:27,308 INFO info.magnolia.cms.beans.config.ContentRepository : Loading workspace clustered 2011-06-16 11:45:27,308 INFO info.magnolia.cms.beans.config.ContentRepository : Loading JCR ucp 2011-06-16 11:45:27,309 INFO info.magnolia.jackrabbit.ProviderImpl : Loading repository at /data/cms/magnolia/author/webapps/magnoliaAuthor/repositories/ucp (config file: /data/cms/magnolia/author/webapps/magnoliaAuthor/WEB-INF/config/repo-conf/jackrabbit-bundle-mysql-search.xml) - cluster id: "<unset>"
I have specified the cluster configuration in the mysql-search.xml file. I tried applying this configuration to a fresh magnolia install and still the same behaviour. No ucp repository created, and the clustered workspace is created under the magnolia repository using H2. Any suggestions? Thanks Rakesh From: Rakesh Vidyadharan <[email protected]<mailto:[email protected]>> Reply-To: Magnolia User-List <[email protected]<mailto:[email protected]>> Date: Wed, 15 Jun 2011 14:59:15 -0500 To: Magnolia User-List <[email protected]<mailto:[email protected]>> Subject: [magnolia-user] Trying to set up clustered workspace Hello, I am experimenting with setting up a clustered workspace (for use by author and public instances) and after going through the JackRabbit and Magnolia documentation came up with the following configuration files: http://sptci.com/uploads/magnolia/jackrabbit-bundle-mysql-search.xml – the public instance does set the cluster id to public http://sptci.com/uploads/magnolia/magnolia.properties http://sptci.com/uploads/magnolia/repositories.xml I started up the instances (author and public running on my test windows 7 machine on same Tomcat) but I notice that the clustered workspace is being created under the default magnolia repository with a H2 database. The MySQL instance also has no tables in it, so obviously the MySQL configuration is not being consulted. I am on the latest 4.4.4 release. A few tests also confirmed this – I created a test folder node through admin interface, and there was nothing visible on the public instance. The JNDI resource is configured as a ResourceLink in the META-INF/context.xml file for both webapps and the resource itself configured as a GlobalNamingResource in tomcat server.xml. Any ideas what I am doing wrong? Thanks Rakesh ________________________________ ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]<mailto:[email protected]>> ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
