jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From smjain <jain...@gmail.com>
Subject Re: javax.jcr.InvalidItemStateException: Item cannot be saved because it has been mo dified externally: node /
Date Fri, 29 Oct 2010 02:24:06 GMT

Thanks for the prompt reply.
I am generating a unique name for every request. Also synchronized the call
to the save. but I still see this error.

What I tried is to create some structure like this

root/test/1 
root/test/2
root/test/3 
...

root/test/10

And then just allowing threads to write into 1 ,2 ,3 and not under root/test
directly. That reduced the occurances but still its there..
Thoughts?

Thanks
Shashank

-- 
View this message in context: http://jackrabbit.510166.n4.nabble.com/javax-jcr-InvalidItemStateException-Item-cannot-be-saved-because-it-has-been-mo-dified-externally-no-tp3017490p3018367.html
Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.

Mime
View raw message