On 8/30/07, Jacco van Weert <[EMAIL PROTECTED]> wrote: > On 8/30/07, Stefan Guggisberg <[EMAIL PROTECTED]> wrote: > > > > On 8/30/07, Jacco van Weert <[EMAIL PROTECTED]> wrote: > > > Hi Stefan > > > > > > > > > I use Jackrabbit 1.3.1 with Java 1.6.0_02 (Linux). > > > I have a servlet application which uses the TransientRepository. There > > is > > > one "admin" session which is used for e.g. expiring objects and every > > > incoming call has it's own Session. > > > > is the 'admin' session possibly shared among multiple threads? > > > > Yes, some actions are done by the admin session.... I guess I should > synchronize on the admin session?
yes. javax.jcr.Session is, per spec, not thread-safe. while sharing a read-only session among multiple threads could probably work (yet untested), sharing a r/w session might lead to corrupt data. > > > > > > > > > > > > > I have no extensions (except for the extractor). I do have my own > > > AccesManager. > > > > does your AccesManager access the repository (i.e. read nodes/properties)? > > > Yes but those methods (which pass the accessmanager again) follow a > different code path. see my previous comment.same concern here. cheers stefan > > > what persistence manager are you using? > > > The standard derby db, no change on the default > > > does more than one node cause the above mentioned exception? > > > It's only one node but it prevents any action in that part of the tree. > > > are you able to read the said node(s) by calling Session#getNodeByUuid()? > > > > the exception actually refers to a node that has a 'null' parentId. > > what jcr call > > does cause the exception, i mean how do you access the affected node > > in the first place? > > > I will get back to you on those questions tomorrow. > > > > > Jacco > > > > -- > ------------------------------------- > Jacco van Weert -- [EMAIL PROTECTED] > JCR Controller -- http://www.xs4all.nl/~weertj/jcr >
