I think this is also the cause of the node state getting corrupted as I
reported in another post. After this error, it seems, the property I was
trying to save, is registered in the node but the item state doesn't
exist. The property reports as existing but if I try to set it, it
throws an ItemNotFoundException. Even though the session is not required
to be thread-safe, shouldn't jackrabbit maintain the repository
consistent at all times?
Carlos
Jukka Zitting wrote:
Hi,
On 2/28/06, Carlos Villegas <[EMAIL PROTECTED]> wrote:
Could this error happen if two threads are working simultaneously on the
same session?
This might well be the cause. A Session should only be accessed from a
single thread as it is not required to be thread-safe. See the section
7.5 Thread-Safety Requirements of the JCR specification.
BR,
Jukka Zitting
--
Yukatan - http://yukatan.fi/ - [EMAIL PROTECTED]
Software craftsmanship, JCR consulting, and Java development
