the first jackrabbit to start up the repository locks the repository by
creating a lock file.
Ross
From: "Esmond Pitt" <esmond.pitt@bigpond.com>
To: <users@jackrabbit.apache.org>
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?
EJP
|
| Mime |
- Unnamed multipart/mixed (inline, Binary, 0 bytes)
- Unnamed multipart/alternative (inline, None, 0 bytes)
|