You have to make sure the running Guvnor instance is completely stopped
before re-deploying. Jackrabbit only allows for one process to access
the repository at a time. Seems maybe the repository in your case is
still open (even if it's the same process, but with another classloader
-> another webapp that hasnt been stopped yet).
I used Tomcat Manager to un-deploy/deploy Guvnor, so Tomcat is running
all the time. And, when I re-deploy Guvnor on a running instance of
Tomcat, I got the repository lock error. In order to be able to deploy
a new Guvnor build, I have to actually stop Tomcat server. But on that
server I have other applications running, and stopping the server is
not an ideal situation. Best case for my application is to be able to
deploy a new Guvnor build on a running Tomcat server.
--Patricia
--- On *Thu, 8/25/11, Geoffrey De Smet /<[email protected]>/* wrote:
From: Geoffrey De Smet <[email protected]>
Subject: Re: [rules-users] Guvnor - Issues with repository lock on
Tomcat re-deployment
To: [email protected]
Date: Thursday, August 25, 2011, 11:05 AM
Did you close down Tomcat6 normally? So not with kill or kill -9?
Op 25-08-11 16:45, Patricia Bogoevici schreef:
I ran Guvnor 5.1 under Tomcat6. If I am using Tomcat manager to
re-deploy Guvnor, I get this error about the repository lock:
Caused by: org.drools.repository.RulesRepositoryException:
javax.jcr.RepositoryException: The repository home
/MY_SERVER_PATH/guvnor/WEB-INF/classes/repository appears to be
already locked by the current process.
To fix the lock error I had to stop Tomcat, upload the new Guvnor
war, and start Tomcat. It is pretty inconvenient that one has to
restart the whole server, as that would disrupt any other
application that is deployed on the same server.
I noticed that another user on this forum mentioned the same
repository lock error, but on a WebSphere 7 server.
(http://drools.46999.n3.nabble.com/Can-Guvnor-provide-client-management-API-td3283602.html#a3283610)
I also checked the JackRabbit source code, and Wiki, and the
documentation says that this error happens when the repository is
not properly closed.
Can anyone from the Drools-Guvnor team add more details about
this? Is this a JackRabbit issue, or a Drools-Guvnor?
thx,
--Patricia
_______________________________________________
rules-users mailing list
[email protected] </mc/[email protected]>
https://lists.jboss.org/mailman/listinfo/rules-users
--
With kind regards,
Geoffrey De Smet
-----Inline Attachment Follows-----
_______________________________________________
rules-users mailing list
[email protected]
</mc/[email protected]>
https://lists.jboss.org/mailman/listinfo/rules-users
_______________________________________________
rules-users mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/rules-users
_______________________________________________
rules-users mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/rules-users
