[
https://issues.apache.org/jira/browse/JCR-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Mueller resolved JCR-1384.
---------------------------------
Resolution: Duplicate
This problem has the same root cause than JCR-1346, which will be fixed in
1.4.1:
http://issues.apache.org/jira/browse/JCR-1346
It is already fixed in the trunk and in the 1.4.1 branch; to try it out you
need to compile Jackrabbit yourself
> Problems creating versions after upgrading from 1.3.3 to 1.4
> ------------------------------------------------------------
>
> Key: JCR-1384
> URL: https://issues.apache.org/jira/browse/JCR-1384
> Project: Jackrabbit
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 1.4
> Reporter: Dirk Feufel
>
> When creating multiple version on a node, the first one is correctly created
> and can be displayed using the node.getVersionHistory() method. But when the
> second version is created within the same session, the following exception
> occurs:
> javax.jcr.RepositoryException: failed to write property state:
> 412ae673-3616-4ec3-8b48-0c8d85a3d857/{http://www.jcp.org/
> jcr/1.0}data: failed to write property state:
> 412ae673-3616-4ec3-8b48-0c8d85a3d857/{http://www.jcp.org/jcr/1.0}data
> at
> org.apache.jackrabbit.core.version.AbstractVersionManager.checkin(AbstractVersionManager.java:381)
> at
> org.apache.jackrabbit.core.version.VersionManagerImpl$2.run(VersionManagerImpl.java:302)
> at
> org.apache.jackrabbit.core.version.VersionManagerImpl$DynamicESCFactory.doSourced(VersionManagerImpl.java:579)
> at
> org.apache.jackrabbit.core.version.VersionManagerImpl.checkin(VersionManagerImpl.java:298)
> at
> org.apache.jackrabbit.core.version.XAVersionManager.checkin(XAVersionManager.java:162)
> at org.apache.jackrabbit.core.NodeImpl.checkin(NodeImpl.java:2962)
> ....
> Caused by: org.apache.jackrabbit.core.state.ItemStateException: failed to
> write property state:
> 412ae673-3616-4ec3-8b48-0c8d85a3d857/{http://www.jcp.org/jcr/1.0}data
> at
> org.apache.jackrabbit.core.persistence.db.DatabasePersistenceManager.store(DatabasePersistenceManager.java:487)
> at
> org.apache.jackrabbit.core.persistence.AbstractPersistenceManager.store(AbstractPersistenceManager.java:75)
> at
> org.apache.jackrabbit.core.persistence.db.DatabasePersistenceManager.store(DatabasePersistenceManager.java:282)
> at
> org.apache.jackrabbit.core.state.SharedItemStateManager$Update.end(SharedItemStateManager.java:688)
> at
> org.apache.jackrabbit.core.state.SharedItemStateManager.update(SharedItemStateManager.java:857)
> at
> org.apache.jackrabbit.core.state.LocalItemStateManager.update(LocalItemStateManager.java:324)
> at
> org.apache.jackrabbit.core.state.LocalItemStateManager.update(LocalItemStateManager.java:300)
> at
> org.apache.jackrabbit.core.version.AbstractVersionManager$WriteOperation.save(AbstractVersionManager.java:180)
> at
> org.apache.jackrabbit.core.version.AbstractVersionManager.checkin(AbstractVersionManager.java:378)
> ... 42 more
> Caused by: java.lang.NullPointerException
> at java.io.FileInputStream.<init>(FileInputStream.java:103)
> at
> org.apache.jackrabbit.core.value.BLOBInTempFile.getStream(BLOBInTempFile.java:145)
> at
> org.apache.jackrabbit.core.persistence.util.Serializer.serialize(Serializer.java:198)
> at
> org.apache.jackrabbit.core.persistence.db.DatabasePersistenceManager.store(DatabasePersistenceManager.java:476)
> ... 50 more
> Basically , the following code is executed, which worked fine in 1.3.3:
> Version ver = node.checkin();
> node.getVersionHistory().addVersionLabel(ver.getName(), "label",
> true);
> node.checkout();
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
