Connection Pool gone berzerk.

Anyone suddenly having problems with connections not being reused after
applying the latest updates from MS? Specifically...
Successful Wednesday, July 14, 2004 Security Update for Windows 2000
(KB839645) Automatic update
Successful Wednesday, July 14, 2004 Security Update for Windows 2000
(KB841872) Automatic update
Successful Wednesday, July 14, 2004 Security Update for Windows 2000
(KB841873) Automatic update
Successful Wednesday, July 14, 2004 Security Update for Windows 2000
(KB840315) Automatic update
Successful Wednesday, July 14, 2004 Security Update for Windows 2000
(KB842526) Automatic update
Successful Wednesday, July 14, 2004 Cumulative Security Update for
Outlook Express 6 SP1 (KB823353) Automatic update
I'm using the Data Application Block and passing the SAME connection string
with only one exception: I manually connect and pass the connection object
rather than the connection string in a couple of routines...and, yes, the
connections are closed before exiting.
The strange thing is...all this worked great until the security updates
above were applied. No other changes.
Now, I run about 5-6 queries and, boom, I'm over the Max Limit default of
100.
Anyone else run into this?
Dave
btw, it's "berserk" not "berzerk".
"Dave Diehl" <d.diehl@.worldnet.att.net> wrote in message
news:uQoEzMcaEHA.2488@.tk2msftngp13.phx.gbl...
> Anyone suddenly having problems with connections not being reused after
> applying the latest updates from MS? Specifically...
> Successful Wednesday, July 14, 2004 Security Update for Windows 2000
> (KB839645) Automatic update
> Successful Wednesday, July 14, 2004 Security Update for Windows 2000
> (KB841872) Automatic update
> Successful Wednesday, July 14, 2004 Security Update for Windows 2000
> (KB841873) Automatic update
> Successful Wednesday, July 14, 2004 Security Update for Windows 2000
> (KB840315) Automatic update
> Successful Wednesday, July 14, 2004 Security Update for Windows 2000
> (KB842526) Automatic update
> Successful Wednesday, July 14, 2004 Cumulative Security Update for
> Outlook Express 6 SP1 (KB823353) Automatic update
>
> I'm using the Data Application Block and passing the SAME connection
string
> with only one exception: I manually connect and pass the connection object
> rather than the connection string in a couple of routines...and, yes, the
> connections are closed before exiting.
> The strange thing is...all this worked great until the security updates
> above were applied. No other changes.
> Now, I run about 5-6 queries and, boom, I'm over the Max Limit default of
> 100.
> Anyone else run into this?
> Dave
>

Connection Pool gone berzerk.

Anyone suddenly having problems with connections not being reused after
applying the latest updates from MS? Specifically...
Successful Wednesday, July 14, 2004 Security Update for Windows 2000
(KB839645) Automatic update
Successful Wednesday, July 14, 2004 Security Update for Windows 2000
(KB841872) Automatic update
Successful Wednesday, July 14, 2004 Security Update for Windows 2000
(KB841873) Automatic update
Successful Wednesday, July 14, 2004 Security Update for Windows 2000
(KB840315) Automatic update
Successful Wednesday, July 14, 2004 Security Update for Windows 2000
(KB842526) Automatic update
Successful Wednesday, July 14, 2004 Cumulative Security Update for
Outlook Express 6 SP1 (KB823353) Automatic update
I'm using the Data Application Block and passing the SAME connection string
with only one exception: I manually connect and pass the connection object
rather than the connection string in a couple of routines...and, yes, the
connections are closed before exiting.
The strange thing is...all this worked great until the security updates
above were applied. No other changes.
Now, I run about 5-6 queries and, boom, I'm over the Max Limit default of
100.
Anyone else run into this?
Davebtw, it's "berserk" not "berzerk".
"Dave Diehl" <d.diehl@.worldnet.att.net> wrote in message
news:uQoEzMcaEHA.2488@.tk2msftngp13.phx.gbl...
> Anyone suddenly having problems with connections not being reused after
> applying the latest updates from MS? Specifically...
> Successful Wednesday, July 14, 2004 Security Update for Windows 2000
> (KB839645) Automatic update
> Successful Wednesday, July 14, 2004 Security Update for Windows 2000
> (KB841872) Automatic update
> Successful Wednesday, July 14, 2004 Security Update for Windows 2000
> (KB841873) Automatic update
> Successful Wednesday, July 14, 2004 Security Update for Windows 2000
> (KB840315) Automatic update
> Successful Wednesday, July 14, 2004 Security Update for Windows 2000
> (KB842526) Automatic update
> Successful Wednesday, July 14, 2004 Cumulative Security Update for
> Outlook Express 6 SP1 (KB823353) Automatic update
>
> I'm using the Data Application Block and passing the SAME connection
string
> with only one exception: I manually connect and pass the connection object
> rather than the connection string in a couple of routines...and, yes, the
> connections are closed before exiting.
> The strange thing is...all this worked great until the security updates
> above were applied. No other changes.
> Now, I run about 5-6 queries and, boom, I'm over the Max Limit default of
> 100.
> Anyone else run into this?
> Dave
>

Connection closes abruptly

My application consists of two modules, one in VB6, which performs Inserts and Updates on an SQL Express Server, and the other in VB.NET which performs Select operations on the same server.

From last two days the .NET module (which performs heavy select queries), randomly gives an error : "Connection closed for this operation", and rarely gives an error : "SqlException: A severe error occurred on the current command".

I don't know whether these two errors are linked to each other. But the former error is a very high priority for me, as it is application wide.

This problem is occuring only in the .NET module. The VB6 module which uses the same server is working fine.

Please help.

Girish

Hi Girish,

It sounds like you're trying to open a connection once and then just leave it open all the while the application is running. You probably shouldn't do this, rather, you should only open the connection when you are activly querying against it. You can certainly run a number of queries in a row against the same connection, but once your immediate need for the connection is past, you should close it.

Connection pooling in .NET and SQL 2005 will automatically manage having connections available to you when you need to re-open them for the next batch of queries. My guess is that if you maintain your connection for shorter times, you'll problem with the connection closing will go away.

You might also consider asking this question on the .NET Data Access forum to see if that group has additional ideas.

Regards,

Mike Wachal
SQL Express team

-
Mark the best posts as Answers!

|||

Hi Girish,

Any luck with this issue?

Mike