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: neutral (asf.osuosl.org: local policy)
Message-ID: <430B4417.1090109@debrunners.com>
Date: Tue, 23 Aug 2005 08:43:19 -0700
From: Daniel John Debrunner <djd@debrunners.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.7.3) Gecko/20040910
MIME-Version: 1.0
To: Derby Discussion <derby-user@db.apache.org>
Subject: Re: Derby server health probing
References: <5dc22fbdcfaba8804d8e9600d77b121b@sun.com>
In-Reply-To: <5dc22fbdcfaba8804d8e9600d77b121b@sun.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Xavier Vigouroux wrote:

> Hi,
> 
> We use a derby server in an High Availability context. Thus, we need to
> test if derby server is in a good shape or not. The result of this
> repetitive question will imply a fail-over or not.
> 
> we thought about two solutions:
> 
> 1/ create an agent to insert/select/delete an entry in a table
> 2/ create a stored procedure doing a finer job.
> 
> these solutions do not satisfy us as:
> 
> o a JVM needs to be created for a very short duration and repetitively
> o it's CPU consuming.
> 
> So, do you think of another solution that would prove the derby server
> is in a good shape, without consuming too much resources.

There's no requirement for a client of the network server to be written
in Java. It should be possible to write a lightweight C program that
sends and receives a ping tcp/ip message to the network server.

Dan.