jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From krispyjala <krispyj...@yahoo.com>
Subject Re: Problems with repository initialization.
Date Mon, 11 Dec 2006 15:48:20 GMT

Thanks for replying Jukka.  I found the culprit of my problem.  It turns out
we are using multiple applicationContext-*.xml to define our
spring/hibernate definitions, and I defined all the repository settings in
applicationContext-service.xml.  Now, there are other context files that
import applicationContext-service.xml and that's why there's always the
.lock file--the repository's getting initialized twice.  I corrected the
problem by using a separate context file that doesn't import anything and
now it works like a charm.  And yes turning on spring log to DEBUG level
really helps in debugging this problem :)


Jukka Zitting wrote:
> Hi,
> On 12/8/06, krispyjala <krispyjala@yahoo.com> wrote:
>> Does anyone have any clue to this?  I am also running into the same error
>> and I can't get anywhere.  Same as Joan, there is no .lock file when I
>> start
>> my repository but when I wrote code to try to get the jcr session it's
>> saying that the .lock file is locked by another process.  But the thing
>> is I
>> have only one repository! How can this be?
> The problem is most likely that you have more than one Repository
> instance around. Either you have a separate JVM that has an open
> repository running on the same directory, or you already have another
> repository instance in the same JVM.
> Check that the repository is defined as a singleton bean in Spring,
> and that you've defined the bean only once. If that doesn't help, you
> may want to monitor the .lock file or your logs to better understand
> when and why the first repository instance is created.
> BR,
> Jukka Zitting

View this message in context: http://www.nabble.com/Problems-with-repository-initialization.-tf2184034.html#a7797181
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.

View raw message