[ http://issues.apache.org/jira/browse/JCR-425?page=comments#action_12402312 ]
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#internalSetItemReferences > 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
