Re: mysql connection pool

[Micael]

I don't know what is going on in this case but this is normal 
procedure.  When you close the connection, you really are (normally) just 
closing a wrapper to a connection, which, instead of really closing it, 
just sends it back to the pool.  I suspect this is really what is 
happening.  The pools should, I think, have a command like returnToPool() 
rather than close(), but they commonly use close().

At 04:02 PM 7/28/2003 +0200, you wrote:
Hi,
does anyone know why I have to close the connection retrieved from a mysql 
database connection pool ?
Isn't the connection returned to the pool automatically when the object 
goes out of scope?

And why is the datasource.getNumActive() value always 0 even though I have 
multiple connections open ?

greetz
Hans
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


LEGAL NOTICE

This electronic mail  transmission and any accompanying documents contain 
information belonging to the sender which may be confidential and legally 
privileged.  This information is intended only for the use of the 
individual or entity to whom this electronic mail transmission was sent as 
indicated above. If you are not the intended recipient, any disclosure, 
copying, distribution, or action taken in reliance on the contents of the 
information contained in this transmission is strictly prohibited.  If you 
have received this transmission in error, please delete the message.  Thank 
you  



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]