jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Miro Walker" <miro.wal...@cognifide.com>
Subject RE: [jira] Commented: (JCR-425) NPE in VersionManagerImpl
Date Mon, 15 May 2006 13:02:26 GMT
Hi Michael,

Can you expand on this explanation a little further? Do you mean that
you were using the same database for both PMs? How did you change your
config to work around this problem?

Thanks,

miro

-----Original Message-----
From: Michael Frericks (JIRA) [mailto:jira@apache.org] 
Sent: 15 May 2006 13:42
To: dev@jackrabbit.apache.org
Subject: [jira] Commented: (JCR-425) NPE in VersionManagerImpl

    [
http://issues.apache.org/jira/browse/JCR-425?page=comments#action_124023
12 ] 

Michael Frericks commented on JCR-425:
--------------------------------------

The reason was that is uesed two equally configured
DBPersistenceManangers for workspace and versioning.
This both PM accessed the same tables. So they are disturbing each
other.

This issue can be closed.


> NPE in VersionManagerImpl
> -------------------------
>
>          Key: JCR-425
>          URL: http://issues.apache.org/jira/browse/JCR-425
>      Project: Jackrabbit
>         Type: Bug

>   Components: core
>     Reporter: Michael Frericks

>
> Sometimes a NPE occurs in
org.apache.jackrabbit.core.version.VersionManagerImpl#internalSetItemRef
erences because the parameter item is null.
> Up the call hierarchy i would suggest to check item != null in method:
>     public boolean setNodeReferences(NodeReferences refs) {
>         try {
>             InternalVersionItem item = getItem(refs.getTargetId());
>             if (item == null)
>             {
>                 return true;
>             }
>             setItemReferences(item, refs.getReferences());
>             return true;
>         } catch (RepositoryException e) {
>             log.error("Error while setting references: " +
e.toString());
>             return false;
>         }
>     }

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message