Jackrabbit Cluster Configuration

[Jens Mehnert <je...@smeet.de>]

I set up a locale cluster configuration (2 tomcats on one machine) for
testing purposes.
To achieve this I enabled jackrabbit with spring using a custom factory bean
that loads
properties from the WEB-INF folder (avoiding RepositoryConfig.create(...)
method call).
The configuration consists of shared and instance folders.

The shared folders are: 

Datastore : .../jackrabbit clusternodes/shared/blobs
Journal   : .../jackrabbit clusternodes/shared/journal

The configuration looks as follows:

---------------------------------------------------------------------

<DataStore class="org.apache.jackrabbit.core.data.FileDataStore">
  
  
</DataStore>


<FileSystem class="org.apache.jackrabbit.core.fs.local.LocalFileSystem">
  
</FileSystem>

<SearchIndex class="org.apache.jackrabbit.core.query.lucene.SearchIndex">
   
</SearchIndex>

<Security appName="Jackrabbit">
  <AccessManager
class="org.apache.jackrabbit.core.security.SimpleAccessManager"/>
    <LoginModule
class="org.apache.jackrabbit.core.security.SimpleLoginModule">
      
    </LoginModule>
</Security>

<Versioning rootPath="${clusternode.repository.versioning.path}">
  <FileSystem class="org.apache.jackrabbit.core.fs.local.LocalFileSystem">
    
  </FileSystem>
  <PersistenceManager
class="org.apache.jackrabbit.core.persistence.bundle.BundleFsPersistenceManager"/>
</Versioning>

<Cluster id="cluster1">
  <Journal class="org.apache.jackrabbit.core.journal.FileJournal">
    
    
  </Journal>
</Cluster>



All other folders are not shared and belong to the repository (running in
the tomcat).
It's now no problem to start the first tomcat that establishes its
repository correctly.
This is also the case for the second tomcat. But after the second tomcat
cames up an
exception is thrown when he tries to synchronize with the journal:

2008-03-03 15:11:51,687 INFO
[org.apache.jackrabbit.core.cluster.ClusterNode] - <Processing revision:
679>
2008-03-03 15:11:51,703 ERROR
[org.apache.jackrabbit.core.cluster.ClusterNode] - <Unable to read revision
'679'.>
org.apache.jackrabbit.core.journal.JournalException: Parse error while
reading node type definition.
        at
org.apache.jackrabbit.core.journal.AbstractRecord.readNodeTypeDef(AbstractRecord.java:256)
        at
org.apache.jackrabbit.core.cluster.ClusterNode.consume(ClusterNode.java:1024)
        at
org.apache.jackrabbit.core.journal.AbstractJournal.doSync(AbstractJournal.java:198)
        at
org.apache.jackrabbit.core.journal.AbstractJournal.sync(AbstractJournal.java:173)
        at
org.apache.jackrabbit.core.cluster.ClusterNode.sync(ClusterNode.java:303)
        at
org.apache.jackrabbit.core.cluster.ClusterNode.run(ClusterNode.java:274)
        at java.lang.Thread.run(Thread.java:619)
Caused by: org.apache.jackrabbit.core.nodetype.compact.ParseException: Error
while parsing '_x002a_' ((internal), line 6)
        at
org.apache.jackrabbit.core.nodetype.compact.Lexer.fail(Lexer.java:152)
        at
org.apache.jackrabbit.core.nodetype.compact.CompactNodeTypeDefReader.toQName(CompactNodeTypeDefReader.java:653)
        at
org.apache.jackrabbit.core.nodetype.compact.CompactNodeTypeDefReader.doPropertyDefinition(CompactNodeTypeDefReader.java:386)
        at
org.apache.jackrabbit.core.nodetype.compact.CompactNodeTypeDefReader.doItemDefs(CompactNodeTypeDefReader.java:344)
        at
org.apache.jackrabbit.core.nodetype.compact.CompactNodeTypeDefReader.parse(CompactNodeTypeDefReader.java:218)
        at
org.apache.jackrabbit.core.nodetype.compact.CompactNodeTypeDefReader.<init>(CompactNodeTypeDefReader.java:178)
        at
org.apache.jackrabbit.core.nodetype.compact.CompactNodeTypeDefReader.<init>(CompactNodeTypeDefReader.java:162)
        at
org.apache.jackrabbit.core.journal.AbstractRecord.readNodeTypeDef(AbstractRecord.java:248)
        ... 6 more
Caused by: javax.jcr.NamespaceException: No URI for pefix '' declared.
        at
org.apache.jackrabbit.spi.commons.namespace.NamespaceMapping.getURI(NamespaceMapping.java:74)
        at
org.apache.jackrabbit.spi.commons.conversion.NameParser.parse(NameParser.java:116)
        at
org.apache.jackrabbit.spi.commons.conversion.ParsingNameResolver.getQName(ParsingNameResolver.java:62)
        at
org.apache.jackrabbit.spi.commons.conversion.DefaultNamePathResolver.getQName(DefaultNamePathResolver.java:61)
        at
org.apache.jackrabbit.core.nodetype.compact.CompactNodeTypeDefReader.toQName(CompactNodeTypeDefReader.java:646)
        ... 12 more


I really do not know what the problem here is and why the namespace cannot
be resolved.
I would be very grateful for any information.

Kind regards, Jens Mehnert





-- 
View this message in context: http://www.nabble.com/Jackrabbit-Cluster-Configuration-tp16396270p16396270.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.