[ 
https://issues.apache.org/jira/browse/JCR-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12872914#action_12872914
 ] 

Stefan Guggisberg commented on JCR-2433:
----------------------------------------

@paul:

google is your friend... ;)

FWIW,

> "INFO: Waiting for N instance(s) to be deallocated" where N is some large 
> number like >100. 

this is a tomcat specific message. i don't know whether it's actually caused by 
a jackrabbit problem
in your case, but google returns lots of hits, e.g. 
http://markmail.org/message/6edcdicnknwdqjxc

> "A property claimed to start before zero, at -512! Resetting it to zero, and 
> hoping for the best" 

http://tinyurl.com/2w3n85f ;)

> 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.

Reply via email to