[
https://issues.apache.org/jira/browse/JCR-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498198
]
Michael Frericks commented on JCR-938:
--------------------------------------
I experienced this exception toom while using simplenames (instead of prefixed
names) .
I debugged down to the org.apache.jackrabbit.name.NameFormat#parseIgnoreCache()
where changing
try {
uri = resolver.getURI(parts[0]);
} catch (NamespaceException nse) {
throw new UnknownPrefixException(parts[0]);
}
to
try {
if (QName.NS_EMPTY_PREFIX.equals(parts[0]))
{
uri = QName.NS_EMPTY_PREFIX;
}
else
{
uri = resolver.getURI(parts[0]);
}
} catch (NamespaceException nse) {
throw new UnknownPrefixException(parts[0]);
}
solved the problem and makes NameFormat work symmetricly on simplenames
> cluster synchronization JournalException
> ----------------------------------------
>
> Key: JCR-938
> URL: https://issues.apache.org/jira/browse/JCR-938
> Project: Jackrabbit
> Issue Type: Bug
> Affects Versions: 1.3
> Reporter: Xiaohua Lu
>
> We are having a lot of updates on a 4 nodes cluster setup and the following
> exception pops up once a while.
> 12:32:33,275 ERROR ClusterNode:933 - [main] Unable to read revision '242'.
> org.apache.jackrabbit.core.journal.JournalException: Unknown prefix error
> while
> reading name.
> at
> org.apache.jackrabbit.core.journal.AbstractRecord.readQName(AbstractR
> ecord.java:159)
> at
> org.apache.jackrabbit.core.journal.AbstractRecord.readPropertyId(Abst
> ractRecord.java:227)
> at
> org.apache.jackrabbit.core.cluster.ClusterNode.consume(ClusterNode.ja
> va:885)
> at
> org.apache.jackrabbit.core.journal.AbstractJournal.doSync(AbstractJou
> rnal.java:191)
> at
> org.apache.jackrabbit.core.journal.AbstractJournal.sync(AbstractJourn
> al.java:166)
> at
> org.apache.jackrabbit.core.cluster.ClusterNode.sync(ClusterNode.java:
> 283)
> at
> org.apache.jackrabbit.core.cluster.ClusterNode.start(ClusterNode.java
> :229)
> at
> org.apache.jackrabbit.core.RepositoryImpl.<init>(RepositoryImpl.java:
> 308)
> at
> org.apache.jackrabbit.core.RepositoryImpl.create(RepositoryImpl.java:
> 584)
> at
> org.apache.jackrabbit.core.jndi.BindableRepository.createRepository(B
> indableRepository.java:174)
> at
> org.apache.jackrabbit.core.jndi.BindableRepository.init(BindableRepos
> itory.java:138)
> at
> org.apache.jackrabbit.core.jndi.BindableRepository.create(BindableRep
> ository.java:125)
> at
> org.apache.jackrabbit.core.jndi.BindableRepositoryFactory.createInsta
> nce(BindableRepositoryFactory.java:59)
> at
> org.apache.jackrabbit.core.jndi.BindableRepositoryFactory.getObjectIn
> stance(BindableRepositoryFactory.java:81)
> at
> org.apache.naming.factory.ResourceFactory.getObjectInstance(ResourceF
> actory.java:140)
> at
> javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:3
> 04)
> at org.apache.naming.NamingContext.lookup(NamingContext.java:793)
> at org.apache.naming.NamingContext.lookup(NamingContext.java:140)
> at org.apache.naming.NamingContext.lookup(NamingContext.java:781)
> at org.apache.naming.NamingContext.lookup(NamingContext.java:140)
> at org.apache.naming.NamingContext.lookup(NamingContext.java:781)
> at org.apache.naming.NamingContext.lookup(NamingContext.java:140)
> at org.apache.naming.NamingContext.lookup(NamingContext.java:781)
> at org.apache.naming.NamingContext.lookup(NamingContext.java:153)
> at org.apache.naming.SelectorContext.lookup(SelectorContext.java:137)
> at javax.naming.InitialContext.lookup(InitialContext.java:351)
> at
> net.maven.mcr.repository.jackrabbit.JackrabbitContentRepository.start
> up(JackrabbitContentRepository.java:66)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
