Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: pass (nike.apache.org: domain of k.huwig@iku-ag.de designates
 212.88.142.131 as permitted sender)
From: Kurt Huwig <k.huwig@iku-ag.de>
Organization: iKu Systemhaus AG
To: Oystein Grovlen - Sun Norway <Oystein.Grovlen@sun.com>
Subject: Re: Derby and HA-JDBC
Date: Mon, 24 Sep 2007 16:20:31 +0200
User-Agent: KMail/1.9.6
References: <46F7C3E8.5070502@sun.com>
In-Reply-To: <46F7C3E8.5070502@sun.com>
Cc: Derby Discussion <derby-user@db.apache.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200709241620.32356.k.huwig@iku-ag.de>

Am Montag, 24. September 2007 schrieben Sie:
> Hi,
>
> I understand from your postings to the Derby user list that you are
> using HA-JDBC with Derby. We are considering whether HA-JDBC is
> something we can recommend to customers who are asking for HA support
> for Derby. Hence, it would be very interesting to us to hear about
> your experience with HA-JDBC:
>
>   - In what configuration do you use it?  How many Derby back-ends?
> How many clients?

Two JVMs, each contains an embedded Derby and offers network access.=20
Each node is configured with a local embedded Derby and accesses the=20
other node via the network client. Read acces is only local, to take=20
advantage of the embedded database.

>   - Is your main purpose get higher availability, or to be able
>     partition the load across more servers (load-balancing)?

Higher availability.

>   - How easy/difficult is it to get started using HA-JDBC?

Very easy: just replace the JDBC driver and insert old driver/credential=20
into the ha-jdbc.xml

>   - From your experience, what kind of applications is HA-JDBC well
>     suited for?  (e.g. is it best for read-mostly access?) What types
>     of application is not that well suited to use HA-JDBC?

I just used it for this one application and it worked fine. We are=20
having some issues with race conditions across nodes, despite we are=20
using distributed transactions due to a "insert or update"-logic. I=20
patched HA-JDBC to simply ignore duplicate-key-exceptions which works=20
fine.

>   - Have you had particular issues with HA-JDBC/Derby that you have
> had to work around?

I found some bugs, each of them has been fixed within hours. The=20
developer is very friendly and even logged into a system of mine to=20
debug some problems.

> I hope are willing to share some of your experience with us either by
> email directly to me or by posting to derby-user.

Sure. I only used version 1.1 of it. Version 2.0 has been released some=20
time ago.
=2D-=20
Mit freundlichen Gr=FC=DFen

Kurt Huwig (Vorstand)
Telefon 0681/96751-50, Telefax 0681/96751-66
http://www.iku-ag.de/

iKu Systemhaus AG, Am R=F6merkastell 4, 66121 Saarbr=FCcken
Amtsgericht: Saarbr=FCcken, HRB 13240
Vorstand: Kurt Huwig, Andreas Niederl=E4nder
Aufsichtsratsvorsitzender: Jan Bankstahl

GnuPG 1024D/99DD9468 64B1 0C5B 82BC E16E 8940 =A0EB6D 4C32 F908 99DD 9468