Returning Connections to Pool

Question

Does anyone know how long iAS 6.5 SP1 (on W2K) takes to return connections to the pool after close() is called? Does the app server wait until the end of a transaction to return connections to the pool, even if close() was called earlier?

Answer 1

Hello,
I understand that a good code must release resources
exactly.
But the problem is that I have 50 coders that write
thousand of JSPs and not all of them write a good
code. You need to hold code reviews. You can't try to band-aid the situation, you have to have standards, conventions, etc.
And it is impossible to check & debug every JSP
for resource-leaking (a question of time-money). This is a design problem. If you are putting code inside of JSP's (which I believe is a bad thing), then you will pay the price. If you use JSP's for presentation only, then you don't need to worry about this, much.
It is very important for a stable system that allocated
resources must be released in every case early of
late. The good idea is to use GC to control
finalization & releasing of resources. In this way
for example it makes every application server to
return allocated db connection to pool. It works
perfectly with local VM.No, no, no. Don't use GC to control ANYTHING. Release the resources back to the server when you're done with them, not when the object is getting collected.
Remote GC uses object expiration time (TTL) that
equals 15 minutes. If rmi have not received "ping"
for that objects from remote system during this time,
they are finalized locally. The time of 15 minutes is
reasonable for some objects type, but some resources
(like db connections from pool) required to be
finalized more rapidly. Is there any method to set
manually the TTL for rmi object?Again, don't do this. You're shooting yourself in the foot. Create all the timers you want, but don't rely on the GC.