Sorry, must have been a bit trigger-happy... ;-) Again: ----->
Hi Daniel (and also Markus, nice to see you, too ;-) )! I haven't experienced your problem although I am using it in a similar manner. But could it be related to this one here: http://issues.apache.org/jira/browse/JCR-912 It sounds a little bit like to me, although I am not really into the actual codebase and stuff... Cheers Hendrik > -----Original Message----- > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Daniel Br?uen > Sent: Friday, August 24, 2007 4:42 PM > To: [email protected] > Subject: Re: Repository Lock Problem in JEE-Environment > > Hi Hendrik! > > > Hendrik Beck (camunda) schrieb: > > > What deployment model do you use? Or do you start and shutdown the > > repository by your own application, e.g. in your beans? > > I am using the shared deployment model and I have registered the jcr as > a custom JNDI-Resource in glassfish (exactly the way it is described in > the wiki). In my beans I simply do something like > > InitialContext ctx = new InitialContext(); > rep = (Repository) ctx.lookup("jcr/repository"); > > or use the @Resource annotation. > > Both ways I regularly get messages like > "javax.jcr.RepositoryException: The repository home > /opt/jackrabbit/repository appears to be already locked by the current > process." > > This message appears whenever I allow the system to idle for a while, or > on redeploy of my bean. > > Cheers, > Dan
