db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepa Remesh" <drem...@gmail.com>
Subject Re: [jira] Commented: (DERBY-210) Network Server will leak prepared statements if not explicitly closed by the user until the connection is closed
Date Tue, 21 Feb 2006 00:17:36 GMT
On 2/20/06, Daniel John Debrunner <djd@apache.org> wrote:
> Deepa Remesh wrote:
> >
> > Bryan, thanks for bringing this up. Please see if the following is okay:
> >
> > If we add back CLSQRY to the finalize call, we need to have
> > synchronization around the code where we send CLSQRY to network server
> > and read server's reply. This synchronization is to ensure we wait for
> > the correct reply. It does not change the state of any objects, So I
> > think it is okay for it to be there in the finalizer. If anyone has
> > other opinions, please share your thoughts.
> Waiting in the finalizer for a server response doesn't seem like a great
> idea to me. The worst case is the server is down or slow and we block
> there for a significant portion of time. Even in the best case of a fast
> response the finalizer is still blocking the finalizer thread,
> potentially stalling the JVM.

Thanks Dan.

This is what I gathered so far from the reviews of patch4:
1. We need to send CLSQRY for all result sets of a statement when the
statement is finalized.
2. Network messages (for which we need to wait for a reply) should not
be sent from the finalizer. This will block the finalizer thread and
potentially the JVM. In general, avoid any synchronized operation from

To be able to do 1 and 2, we require a mechanism similar to what is
done by embedded driver for finalization. I have to work out some more
details for this. Once done, I'll post it to the jira issue for
review. In the meantime, if anyone has any other comments/suggestions,
please let me know.


View raw message