[
https://issues.apache.org/jira/browse/JCR-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12873146#action_12873146
]
Paul Jara commented on JCR-2433:
--------------------------------
Thanks Stefan. Yes I've Googled both of those error message before but I
figured that it was worth mentioning both of them as they only appeared after
the fixed JARs were in place. Unfortunately, the tomcat deallocation problem is
not one that seems to have one solution. In general, the message appears to
refer to servlets that are still running which would normally not be a
JackRabbit induced problem. My question is, would there be any code in the
specific fix for this problem that might actually induce this sort of problem
with TomCat? I'm trying to isolate all of the variables that changed over the
past two weeks on the production servers to see which change may have brought
about this problem. There weren't very many changes, so this particular JAR
deployment stands out as something I should look at.
> NPE when copying nodes with Workspace.copy()
> --------------------------------------------
>
> Key: JCR-2433
> URL: https://issues.apache.org/jira/browse/JCR-2433
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 1.6.0
> Reporter: Sascha Theves
> Assignee: Jukka Zitting
> Priority: Blocker
> Fix For: 1.6.2
>
>
> I get a NullpointerException when using Workspace.copy():
> java.lang.NullPointerException
> at
> org.apache.jackrabbit.core.BatchedItemOperations.copyNodeState(BatchedItemOperations.java:1834)
> at
> org.apache.jackrabbit.core.BatchedItemOperations.copyNodeState(BatchedItemOperations.java:1806)
> at
> org.apache.jackrabbit.core.BatchedItemOperations.copyNodeState(BatchedItemOperations.java:1806)
> at
> org.apache.jackrabbit.core.BatchedItemOperations.copy(BatchedItemOperations.java:423)
> at
> org.apache.jackrabbit.core.WorkspaceImpl.internalCopy(WorkspaceImpl.java:444)
> at org.apache.jackrabbit.core.WorkspaceImpl.copy(WorkspaceImpl.java:666)
> at xxx.MyClass.myMeth(MyClass.java)
> It seems that it happens not all the time. The error occurs since we use
> Jackrabbit 1.6.0. We do not get the error with previous versions. It seems
> that we only get the error when trying to copy nodes that were created with
> Jackrabbit 1.4 and copied with Jackrabbit 1.6.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
