Re: jdbc-IBM Connection Manager-Servlets and sql handles

> > I do think that it would not be a bad idea for the Connection
> >itself to release those resources when it is closed/destroyed.
>
> Just in case I was not clear, this will happen today.  The only problem
> comes when the connection is pooled and so it does not get really
> closed/destroyed for a very long time.

Richard-

In that case I am suprised Alex had the problem which they had (server
brought to its knees after a few days). That must mean that the Connections
in the pool they were using were being kept alive for longer than a few
days, allowing many statements which are no longer used to remain alive. I
guess this is valid, but a "safe" solution to the problem would be to have
the connection manager close connections and replace them with new ones
after a given set of circumstances (example: they have been used twice, they
are more than 2 hours old, etc..) I don't recall specically, but I think
something like this is configurable within the connection manager?

Luther

+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---