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

Gerald,

The 's()' prototype is defined in the JDBCR4 source member... it's not a "C API" (whatever that means) It is a call to the constructor for a Java String object.

I can't see why this routine would ever open a descriptor.

Are you sure it's when this is called? I think it's more likely to be when the JVM is first started up. RPG will automatically start the JVM when the first Java call is made in a program. The string constructor doesn't use any descriptors, but Java certainly does!

It doesn't seem right that it would leave a lot of descriptors open, however. Something isn't right, here...






On 3/16/2016 10:37 AM, Gerald Magnuson wrote:

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...