the first jackrabbit to start up the repository locks the repository by creating a lock file.


From:        "Esmond Pitt" <>
To:        <>
Date:        04/09/2012 10:04 AM
Subject:        Deployment question: is Jackrabbit process-safe?

I have a clustered web-app that uses Jackrabbit. I presently have Jackrabbit
in yet another Tomcat and am using RMI to communicate with it. However it
occurs to me that I could just include the JackRabbit API jars in the webapp
and call it directly, *provided* multiple copies of the Jackrabbit API will
co-operate correctly on the database. Is this the case?