You could use derby (bundled one) but, if you use a linux server, then
you should increase the limits of linux by editing
/etc/security/limits.conf with at least (saying you use the user
"tomcat" for tomcat) :
# just add this
tomcat soft nbproc 2047
tomcat hard nbproc 16384
tomcat soft nofile 1024
tomcat hard nofile 65536
# end of settings
This is to avoid the "Too many open files" error.
You can also use MySQL with the PooledJNDIDatabasePersistenceManager
(former DataSourcePersistenceManager) which is the only "stable" for
using a MySQL database (actually, in jackrabbit, the given
JNDIDatabasePersistenceManager and SimpleDBPersistenceManager only use
one connection to the DB, leading to some "broken pipe" error with MySQL
server).
Finally, you can use the professional CRX (not free) bundled with the
enterprise version of Magnolia. It is said to be quicker than the open
source jackrabbit drivers.
Anthony
Theodore Nguyen-Cao a écrit :
> Hi,
>
> I wanted to reach out to the community and ask what is everyone using
> for their JackRabbit repository persistence layer and how is their
> experience with their choice so far? Most implementations I've read
> about seem to use derby, MySQL, or Oracle. I'd like to get feedback on
> how these solutions have performed and scaled and any issues. I am
> especially interested in any insight to how an Oracle solution has
> performed.
>
> Thanks in advance,
>
> Theo
>
> ----------------------------------------------------------------
> for list details see
> http://www.magnolia.info/en/developer.html
> ----------------------------------------------------------------
>
>
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
