Re: JDBC host server job locks object after 2nd query -- MIDRANGE-L

Subject: Re: JDBC host server job locks object after 2nd query
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Fri, 16 Apr 2021 12:34:14 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

On 4/16/21 12:28 PM, Richard Schoen wrote:

This may be a Captain Obvious type of question, but are you closing your statements and connections after the query is done ?

No, this the connection is not being closed, but the statement is.

The lock defintely goes away when the connection is closed (because the
host server job goes away).

Also what type of Java app ? Web App, Web Service, Console or other background type of app ? Run once or always running ?

Not really a factor.

Or maybe it's just V7R2....

No, I saw it on multiple releases.

John Eberhard suggested it was a pseudo closed cursor
(https://archive.midrange.com/java400-l/202104/msg00005.html) which
makes a lot of sense.

david

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.