Hi,

Well, it looks like it is garbage collection dependent. With a little test
app I could verify that the db connections *are* closed but only if the
corresponding java object is garbage collected. Since our test server is not
very busy it discards those stale (as in: not used for x minutes)
connections and create new ones. Since no full garbage collection is
triggered they are not physically closed.

Is this a feature or can this be rectified somehow? I would highly
appreciate if they would be closed instantly, i.e. whenever
FBConnection.close() is called.

Kind regards,
Lars

----- Original Message -----
From: "Lars George" <lars@...>
To: <Firebird-Java@yahoogroups.com>
Sent: Wednesday, October 30, 2002 10:05 AM
Subject: [Firebird-Java] Connection does not close properly


> Hi,
>
> We have a connection pool that closes stale connection. It calls
> connection.close() as expected. But the connection does not disappear on
the
> server level, i.e. it leaves the gds_inet_server process connected on the
> database server.
>
> I was under the impression calling FBConnection.close() would free all
> resources and close the connection to the database. What are we doing
wrong?
> Are we doing anything wrong?
>
> Kind regards,
> Lars
>
>
>
> To unsubscribe from this group, send an email to:
> Firebird-Java-unsubscribe@yahoogroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>