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.
Thanks
--
Xavier VIGOUROUX - sun microsystems
