November 17, 2003 at 8:33 am
hi there,
Does anybody have more information regarding the memory
leak the MDAC 2.7 SP1 Refresh fixes? The MS site is very
vague about this.
http://support.microsoft.com/?kbid=814410
I have a situation where ODBC opens connections to a SQL
server on another machine, but these connections are never
used, nor closed. Result is that the client machine runs
out of TCP/IP connections, and then ODBC time-out errors
start ocurring. The weird thing is that the ODBC
Connection Pooling PerfMon counter displays 20 Active / 0
Inactive connections in the pool, but at the same time the
server shows typically 800+ open connections! These
connections are established, since there is a corresponding
TCP/IP connection for each showing up in netstat.
I don't know if this scenario fits in with MS'es definition
of a memory leak, but I need more definate proof that
upgrading to MDAC 2.7SP1 Refresh will fix the problem. The
problem only occurs in production, and we cannot simulate
it in other (less powerful) environments. We are currently
running MDAC2.7SP1.
Thank you in advance for any help!
Ruan
November 20, 2003 at 8:00 am
This was removed by the editor as SPAM
November 20, 2003 at 8:33 am
Nothing I've seen. We've yet to deploy it.
Andy
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply