Darren
Connection pooling is on by default with the connector. What this means is
that when you close a connection in your code, the actual link to the server
is not closed but rather returned to the pool. This allows for much faster
opens later. To disable pooling, add pooling=false to your connection
string. Regardless of your pooling setting, the connections should
terminate when your application exits. If they are not, please report this
as a bug. If, however, you are still seeing the connections while your
application is running, it is likely because of pooling.
-reggie
-----Original Message-----
From: Darren Hill [mailto:darren@stripped]
Sent: Wednesday, November 10, 2004 2:13 PM
To: dotnet@stripped
Subject: Connection Life?!?!?
Hello all,
I'm finding some connections are never dieing.
Here's my connection string
<add key="conn" value="Persist Security
Info=False;database=hrmanager;server=xxxxxxxx;Connect Timeout=30;user
id=xxxx; pwd=xxxx;" />
And I'll go ahead and do some testing and then run SHOW PROCESSLIST.
I'll find that all my connections are NOT timing out. They stay in a
SLEEP command indefinatley.
Is this a bug I should report, or am I missing something in the
connector string?
Darren Hill
darren@stripped
Tel: 416-410-1154 ext. 2
Toll Free: 866-410-1154 ext. 2
Fax: 905-873-6685
--
MySQL on .NET Mailing List
For list archives: http://lists.mysql.com/dotnet
To unsubscribe: http://lists.mysql.com/dotnet?unsub=1
