Thanks Thomas!
I have been trying different scenarios and memory profilers for over two weeks trying to track down that leak! I didn't want to post until I was sure that I could isolate it to the ODBC connection. Following your suggestion, I added an extra connection that I open but never use and it seems to have done the trick. I've now hit the service with over a half-million transactions under varing load conditions over the past several days and the memory profile appears stable. Terry Gifford Tacoma Power - Gateway Project -----Original Message----- From: Koetter, Thomas Theodor [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 02, 2006 4:39 AM To: Gifford, Terry; maxdb@lists.mysql.com Subject: RE: ODBC leak when pooling connections Hello Terry > -----Original Message----- > From: Gifford, Terry [mailto:[EMAIL PROTECTED] > Sent: Montag, 1. Mai 2006 19:07 > To: maxdb@lists.mysql.com > Subject: ODBC leak when pooling connections > [detailed problem description snipped] Actually there is a problem with connection pooling, when really all connections are released and the pool manager removes all connections. Then the ODBC-driver-dll is unloaded and reloaded when needed again. Unfortunately, by unloading not all resources can be freed. A work around is, not to release all resources. For an application it is sufficient to hold at least one additional ODBC environment. This needs nearly no resources but prevents unloading the dll. HTH & regards Thomas ---------------------------------------------- Dr. Thomas Kötter SAP AG, Berlin NW DT MaxDB MaxDB: all you need! www.mysql.com/products/maxdb www.sapdb.org -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
