You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by Esteban Franqueiro <ef...@bea.com> on 2007/12/14 19:48:55 UTC
Jackrabbit & MySQL
Hi all.
I wanted to know your experience in using Jackrabbit with MySQL as a
backend. I usually use
Derby+SQL Server for the datastore so I have no experience with MySQL.
Any advice?
Regards,
Esteban Franqueiro
esteban.franqueiro@bea.com
Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.
RE: Jackrabbit & MySQL
Posted by sbarriba <sb...@yahoo.co.uk>.
Hi Esteban,
We've been using both MySql 5 and Oracle as a backend for our Jackrabbit 1.3
deployment for over a year without major issue. MySql has been fast and
reliable plus its replication facilities work well with Jackrabbits
clustering features to provide a fault-tolerant architecture.
The only gotcha at the moment is the connection timeout issue with MySql as
JackRabbit 1.3 does not valid the connection before using it.
Regards,
Shaun
-----Original Message-----
From: Esteban Franqueiro [mailto:efranque@bea.com]
Sent: 14 December 2007 18:49
To: users@jackrabbit.apache.org
Subject: Jackrabbit & MySQL
Hi all.
I wanted to know your experience in using Jackrabbit with MySQL as a
backend. I usually use
Derby+SQL Server for the datastore so I have no experience with MySQL.
Any advice?
Regards,
Esteban Franqueiro
esteban.franqueiro@bea.com
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be confidential, proprietary, copyrighted and/or
legally privileged, and is intended solely for the use of the individual or
entity named in this message. If you are not the intended recipient, and
have received this message in error, please immediately return this by email
and then delete it.