I'm assuming your talking with Derby using the network client JDBC
driver, and that Derby is running as a separate process that accepts
network connections?
If the server goes down, you'll get a disconnect exception and your
connection will be invalid. There's nothing more you need to do. Derby
cleans up (runs recovery) automatically on startup and then you just
reconnect.
Does that answer your question?
David
Amir Michail wrote:
Hi,
I was wondering how a servlet should handle derby server problems. For
example, what should happen if the derby server goes down? How should
the servlet handle this situation as to not confuse the derby server
on startup and cause severe errors (e.g., that might result in an
immediate shutdown of the derby server)?
Amir
