Re: JDBCR4 - leaving lots of file descriptors open.. -- MIDRANGE-L

Subject: Re: JDBCR4 - leaving lots of file descriptors open..
From: Gerald Magnuson <gmagqcy.midrange@xxxxxxxxx>
Date: Wed, 16 Mar 2016 10:37:08 -0500
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

I am attempting to debug through the JDBC program...

what C api is "s()"???
I first thought it was return the length of string, but the first time it
is called, I get 64 open descriptors...

On Wed, Mar 16, 2016 at 9:25 AM, Gerald Magnuson <gmagqcy.midrange@xxxxxxxxx

wrote:

I am having intermittent problems with jobs having too many open file
descriptors.
I have found that when I first connect to a remote database I consume 124
open file descriptors.
and after I perform a close on the connection, it doesn't close those 124.

I am sure that this popped up when either I updated my java, or some other
update...

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: JDBCR4 - leaving lots of file descriptors open.. , Scott Klement

This mailing list archive is Copyright 1997-2024 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.