Hi, Well, if I close my application, windows grabs hold of the handles again... If that is what you mean? I use it with an applications generator for telecom mostly so I have no idea how the inner works is done. I could find out for you if you want to, since I'm working at that company :) We want to be able to give MySQL as an option to our partners instead of always suggesting MS SQL server or oracle. The more the merrier :)
What I know is that the DBstuff is started in its own thread and when all DB interaction is done, the thread is killed. The handles are still attached to the platform. When the platform is killed by exiting or force-exit, the handles are returned. Perhaps we can change something in our application? But from what our developers have told me, they are using ODBC 1.0 straight up with no short-cuts.... Let me know if you need anything! / Jens -----Original Message----- From: Venu [mailto:[EMAIL PROTECTED]] Sent: den 19 december 2001 20:01 To: Jens Collin; [EMAIL PROTECTED] Subject: RE: MyODBC leaking handles... Hi, > -----Original Message----- > From: Jens Collin [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, December 19, 2001 3:05 AM > To: '[EMAIL PROTECTED]'; [EMAIL PROTECTED] > Subject: RE: MyODBC leaking handles... > > > Hi again, > > Some more information; > OS: Windows 2000 Professional, SP2a + all patches > mySQL 3.32.46 (windows version) > myODBC 2.50.37 > > I open then database, do a select, close the recordset and finally close the > database. > This results in 2 handles increase. (Notised in windows task manager) > If I loop this test, the handles counter just goes through the roof. over > 800.000 handles over one night! > I have done the exact same test with MS SQL Server 7.0 and 2000, no missing > handles. > This works for oracle's drivers as well. > > I guess that a trace can be useful? However, I should upload it to your FTP > right? (If I read the manual right :)) > I'll be happy to assist you with any data needed, just let me know what to > send. > Thanks for the feedback. I will look into it immediately. When I tested with PURIFY, I couldn't find any leaks. Let me do a cross check again. Another small note, might be useful. There are some open resources allocated for the driver during the initialization, and will be freed only upon termination or unloading of driver from memory. So, does this happen even after terminating the application in the proper sequence of calls ? No need of any trace right now, if needed I will ask you. Regards, Venu -- For technical support contracts, go to https://order.mysql.com __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Mr. Venu <[EMAIL PROTECTED]> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Developer /_/ /_/\_, /___/\___\_\___/ California, USA <___/ www.mysql.com > > > > -----Original Message----- > From: Venu [mailto:[EMAIL PROTECTED]] > Sent: den 18 december 2001 19:38 > To: Jens Collin; [EMAIL PROTECTED] > Subject: RE: MyODBC leaking handles... > > > Hi, > > > -----Original Message----- > > From: Jens Collin [mailto:[EMAIL PROTECTED]] > > Sent: Tuesday, December 18, 2001 4:22 AM > > To: '[EMAIL PROTECTED]' > > Subject: MyODBC leaking handles... > > > > > > Hi all, > > > > This is my first post in this forum. I've tried to find something in the > > documentation but failed. > > I cannot find out why the ODBC driver is leaking 1 handle for each request > > that I do! > > It doesn't matter if I close it or whatever I do. > > Anyone that knows what to do? > > Any hints or tips? > > Recently we found the leaks in the initialization > towards UNIX, and fixed them from driver and server, > but we didn't find any thing from Windows (The Unix > fixes will be there for 2.50.40 and 3.51.01) > > > > > Windows 2000 Professional > > MySQL 3.23 > > MyODBC 2.50.39 > > Can you be more specific on this, please ? If you can send the > leaks statistics, it will be a great help. > > Regards, Venu > -- > For technical support contracts, go to https://order.mysql.com > __ ___ ___ ____ __ > / |/ /_ __/ __/ __ \/ / Mr. Venu <[EMAIL PROTECTED]> > / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Developer > /_/ /_/\_, /___/\___\_\___/ California, USA > <___/ www.mysql.com > > > > > > Regards, > > ___________________________________ > > > > Jens A. Collin > > Envox Technical System Developer > > > > Envox Group > > Söder Mälarstrand 43 > > 118 25 Stockholm > > Sweden > > > > Office: +46 (0)8 56 256 000 > > Fax : +46 (0)8 56 256 050 > > > > [EMAIL PROTECTED] > > http://www.envox.com > > ___________________________________ > > > > > > --------------------------------------------------------------------- > > Before posting, please check: > > http://www.mysql.com/manual.php (the manual) > > http://lists.mysql.com/ (the list archive) > > > > To request this thread, e-mail <[EMAIL PROTECTED]> > > To unsubscribe, e-mail > > <[EMAIL PROTECTED]> > > Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php > > > --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
