You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Nick Tuckett (JIRA)" <ji...@apache.org> on 2012/07/12 12:20:35 UTC
[jira] [Commented] (JCR-3173) InvalidItemStateException if
accessing VersionHistory before checkin()
[ https://issues.apache.org/jira/browse/JCR-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13412669#comment-13412669 ]
Nick Tuckett commented on JCR-3173:
-----------------------------------
Getting the same result as Vitali and Roland mention above, using version 2.4.0.
For my use cases, this means that transactions containing changes to versionable nodes are broken.
The workaround works for me, but introduces undesirable dependencies on Jackrabbit implementation classes. So I wanted to add my weight to asking for a fix for this!
> InvalidItemStateException if accessing VersionHistory before checkin()
> ----------------------------------------------------------------------
>
> Key: JCR-3173
> URL: https://issues.apache.org/jira/browse/JCR-3173
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 2.2.10
> Reporter: Matthias Reischenbacher
> Attachments: UserTransactionCheckinTest.java
>
>
> A checkin operation fails during a transaction if the VersionHistory of a node is accessed previously. See the attached test case for further details.
> -------------------------------------------------------------------------------
> Test set: org.apache.jackrabbit.core.version.UserTransactionCheckinTest
> -------------------------------------------------------------------------------
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 4.072 sec <<< FAILURE!
> testRestoreWithXA(org.apache.jackrabbit.core.version.UserTransactionCheckinTest) Time elapsed: 3.858 sec <<< ERROR!
> javax.jcr.InvalidItemStateException: Could not find child e77834ee-244c-441f-ab94-19847c769fa4 of node 03629609-8049-46ee-9e80-279c70b3a34d
> at org.apache.jackrabbit.core.ItemManager.getDefinition(ItemManager.java:207)
> at org.apache.jackrabbit.core.ItemData.getDefinition(ItemData.java:99)
> at org.apache.jackrabbit.core.ItemManager.canRead(ItemManager.java:421)
> at org.apache.jackrabbit.core.ItemManager.createItemData(ItemManager.java:843)
> at org.apache.jackrabbit.core.ItemManager.getItemData(ItemManager.java:391)
> at org.apache.jackrabbit.core.ItemManager.getItem(ItemManager.java:328)
> at org.apache.jackrabbit.core.ItemManager.getItem(ItemManager.java:622)
> at org.apache.jackrabbit.core.SessionImpl.getNodeById(SessionImpl.java:493)
> at org.apache.jackrabbit.core.VersionManagerImpl$1.perform(VersionManagerImpl.java:123)
> at org.apache.jackrabbit.core.VersionManagerImpl$1.perform(VersionManagerImpl.java:1)
> at org.apache.jackrabbit.core.session.SessionState.perform(SessionState.java:200)
> at org.apache.jackrabbit.core.VersionManagerImpl.perform(VersionManagerImpl.java:96)
> at org.apache.jackrabbit.core.VersionManagerImpl.checkin(VersionManagerImpl.java:115)
> at org.apache.jackrabbit.core.VersionManagerImpl.checkin(VersionManagerImpl.java:101)
> at org.apache.jackrabbit.core.NodeImpl.checkin(NodeImpl.java:2830)
> at org.apache.jackrabbit.core.version.UserTransactionCheckinTest.testRestoreWithXA(UserTransactionCheckinTest.java:35)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira