You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by Costin Leau <co...@gmail.com> on 2005/12/08 19:42:47 UTC

invalid QName literal

Hi guys,

I'm having problem with some tests that run fine on two machines I
have control over (WinXP/JDK 1.5 and Linux/JDK 1.4.2) but on one that
I don't have control I get:

javax.jcr.RepositoryException: failed to read node state: deadbeef-face-babe-cafe-babecafebabe: invalid QName literal: failed to read node state: deadbeef-face-babe-cafe-babecafebabe: invalid QName literal
        at org.apache.jackrabbit.core.version.VersionManagerImpl.<init>(VersionManagerImpl.java:158)
        at org.apache.jackrabbit.core.RepositoryImpl.<init>(RepositoryImpl.java:210)
        at org.apache.jackrabbit.core.RepositoryImpl.create(RepositoryImpl.java:424)

I assume is something related to an XML library but as I don't have
access to the machine ...

Thanks.
-- 
Best regards,
 Costin Leau                          mailto:costin.leau@gmail.com

Re[2]: invalid QName literal

Posted by Costin Leau <co...@gmail.com>.
> it's not xml related. jackrabbit has its own QName class (o.a.j.name.QName).

> my best guess would be incompatibility of serialization formats. the
> format has changed
> a couple of weeks ago. make sure you run the tests on an initially
> empty repository.

> if that doesn't explain your problem please send a full stack trace,
> configuration etc.

> cheers
> stefan


Thanks.
Indeed, we did a library upgrade and probably on the remote
machine the old repository (or tmp file) still exists. I'm using
InMemPersistenceManager:

java.lang.IllegalArgumentException: invalid QName literal
        at org.apache.jackrabbit.name.QName.valueOf(QName.java:635)
        at org.apache.jackrabbit.core.state.util.Serializer.deserialize(Serializer.java:122)
        at org.apache.jackrabbit.core.state.mem.InMemPersistenceManager.load(InMemPersistenceManager.java:378)
        at org.apache.jackrabbit.core.state.SharedItemStateManager.loadItemState(SharedItemStateManager.java:740)
        at org.apache.jackrabbit.core.state.SharedItemStateManager.getNonVirtualItemState(SharedItemStateManager.java:667)
        at org.apache.jackrabbit.core.state.SharedItemStateManager.getItemState(SharedItemStateManager.java:188)
        at org.apache.jackrabbit.core.state.LocalItemStateManager.getNodeState(LocalItemStateManager.java:101)
        at org.apache.jackrabbit.core.state.LocalItemStateManager.getItemState(LocalItemStateManager.java:156)
        at org.apache.jackrabbit.core.version.VersionManagerImpl.<init>(VersionManagerImpl.java:151)
        at org.apache.jackrabbit.core.RepositoryImpl.<init>(RepositoryImpl.java:210)
        at org.apache.jackrabbit.core.RepositoryImpl.create(RepositoryImpl.java:424)

I'll try to clean the directory through the build file and let you
know the results.

-- 
Best regards,
 Costin                            mailto:costin.leau@gmail.com

Re: invalid QName literal

Posted by Stefan Guggisberg <st...@gmail.com>.
hi costin,

On 12/8/05, Costin Leau <co...@gmail.com> wrote:
> Hi guys,
>
> I'm having problem with some tests that run fine on two machines I
> have control over (WinXP/JDK 1.5 and Linux/JDK 1.4.2) but on one that
> I don't have control I get:
>
> javax.jcr.RepositoryException: failed to read node state: deadbeef-face-babe-cafe-babecafebabe: invalid QName literal: failed to read node state: deadbeef-face-babe-cafe-babecafebabe: invalid QName literal
>         at org.apache.jackrabbit.core.version.VersionManagerImpl.<init>(VersionManagerImpl.java:158)
>         at org.apache.jackrabbit.core.RepositoryImpl.<init>(RepositoryImpl.java:210)
>         at org.apache.jackrabbit.core.RepositoryImpl.create(RepositoryImpl.java:424)
>
> I assume is something related to an XML library but as I don't have
> access to the machine ...

it's not xml related. jackrabbit has its own QName class (o.a.j.name.QName).

my best guess would be incompatibility of serialization formats. the
format has changed
a couple of weeks ago. make sure you run the tests on an initially
empty repository.

if that doesn't explain your problem please send a full stack trace,
configuration etc.

cheers
stefan


>
> Thanks.
> --
> Best regards,
>  Costin Leau                          mailto:costin.leau@gmail.com
>
>