jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jared Graber" <jared.gra...@IACcap.com>
Subject RE: Multiple connections to database repository
Date Wed, 25 Jun 2008 13:15:27 GMT
If possible I would prefer to stick with accessing the underlying
database.  Using RMI is an option but with the solution we're using, I
see that as a potential problem as well.  
In one of our environments, the repository will basically be read only -
the database will overwritten with a copy from one of the other
environments, but will restrict access to only reads.  Because the data
is being overwritten from an external source (not through the API) I can
see that causing caching issues with RMI - unless the JCR-RMI server is

In my apps, I don't need to have a constant connection to the repository
backed by the database.  I only need to connect when the app receives a
signal to update its data (this doesn't happen often).  Would shutting
down the repository and reconnecting clear the cache?


-----Original Message-----
From: Jukka Zitting [mailto:jukka.zitting@gmail.com] 
Sent: Wednesday, June 25, 2008 12:54 AM
To: users@jackrabbit.apache.org
Subject: Re: Multiple connections to database repository


On Tue, Jun 24, 2008 at 11:07 PM, Jared Graber <jared.graber@iaccap.com>
> In that case my question comes down to this:

Are you decided about accessing the underlying database from multiple
Jackrabbit clients from different host/JVMs? How about using JCR-RMI
instead of a remote database connection to access the database. Then
you wouldn't need to worry about any caching issues etc.


Jukka Zitting

View raw message