You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by Radu Ana-Maria <ra...@gmail.com> on 2010/02/01 09:44:30 UTC

question regarding .lock file

hello,

i have a question upon this mecanism of locking
i have a was application server(7.0.0.7) with a web application for content
repository (connection is made using a JNDI)

i've tested 2 options:
  1. all .jar's are included in my web application and run on server...and i
get an error : allready using the repository (.lock error)
  2. moved the .jar's on lib/ext path on the application server and when
runing the application it works just fine..why?

10x,
ana

Re: question regarding .lock file

Posted by Thomas Müller <th...@day.com>.
Hi,

Most likely you try to open the repository multiple times then, as
documented in http://wiki.apache.org/jackrabbit/RepositoryLock - To
find out where exactly it is opened, you could run the application in
debug mode and set a breakpoint where the repository is opened.

Regards,
Thomas

Re: question regarding .lock file

Posted by Radu Ana-Maria <ra...@gmail.com>.
nope, i don't get this exception only when i reload, i get it all the time
i've read : http://wiki.apache.org/jackrabbit/RepositoryLock, but it i can't
find any answer.

10x for you answer!
ana r.

On Mon, Feb 1, 2010 at 11:33 AM, Thomas Müller <th...@day.com>wrote:

> Hi,
>
> >  1. all .jar's are included in my web application and run on server...and
> i
> > get an error : allready using the repository (.lock error)
>
> I guess you only get the exception when you reload the application?
> The most likely reason is that the repository is not closed when the
> application is stopped.
>
> See also http://wiki.apache.org/jackrabbit/RepositoryLock
>
> Regards,
> Thomas
>

Re: question regarding .lock file

Posted by Thomas Müller <th...@day.com>.
Hi,

>  1. all .jar's are included in my web application and run on server...and i
> get an error : allready using the repository (.lock error)

I guess you only get the exception when you reload the application?
The most likely reason is that the repository is not closed when the
application is stopped.

See also http://wiki.apache.org/jackrabbit/RepositoryLock

Regards,
Thomas