jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From KÖLL Claus <C.KO...@TIROL.GV.AT>
Subject AW: Persistence Manager in Production Environment
Date Wed, 21 Feb 2007 11:41:04 GMT
hi stefan,

thanks for your information ..
do you prefer to use the j2c adapter in a production environment
to get a xasession (atomic transaction) ? the problem for me is that we are running in a websphere
environemnt
and i'm not able to run the j2c adapter on it @see JCR JCR-743.
Maby somebody has experiences with websphere ??


-----Ursprüngliche Nachricht-----
Von: Stefan Guggisberg [mailto:stefan.guggisberg@gmail.com] 
Gesendet: Mittwoch, 21. Februar 2007 11:34
An: users@jackrabbit.apache.org
Betreff: Re: Persistence Manager in Production Environment

i'd suggest, for now, using jackrabbit's default configuration, i.e.
DerbyPersistenceManager, since it's been extensively tested and since
it is pretty fast (considerably faster than the oracle pm).

cheers
stefan

On 2/21/07, KÖLL Claus <C.KOELL@tirol.gv.at> wrote:
> We are on the road to use jackrabbit in our production environment but i'm not sure
> which persistence manager we should use.
>
> I have made some tests with the j2c adapter in combination with the oracle db pm
> to get a atomar transaction through the pm.
> A reason for db is also the easy way to backup/restore the data.
>
> On the other hand is the filesystem, no atomar transaction but it is fast. we think we
get about 1-2 Million documents in jackrabbit
> and then the backup is no more really possible on filesystem beacuse if i use objectpersistenmanager
i get about
> 6-10 files per node on fs (6*2Million files effectivity). On crash to recover these files
take really long :-)
>
> A good message is that day will offer there pm's, so the node propertys will no more
be stored in seperate files ..
>
> I hope i get some experience ...
> thanks
> claus
>

Mime
View raw message