Hello



I’m not sure this is the correct place to report a bug. Please let me know
the correct way if not.



I have a problem with thread management in the odbc driver v. 05.01.0010
(tested on linux only for now). When we open a connection from one thread
and close it from another thread we get the message:



Error in my_thread_global_end(): 1 threads didn't exit



We don’t know what are the consequences of this situation but I’m afraid
that it produces some kind of instability and/or memory leak.



We use the odbc driver with a framework that creates pool of connections and
several threads can access the odbc connection (one at a time because its
synchronized). Sometimes because of time outs, the connection need to be
closed and reopened by the thread. So this bug is for us a blocking
situation.



Attached is a simple program that reproduces the issue. Just compile it on
linux. The usage is:



testodbc2 -s DataSource -u User [-p Password]



Here is the report on my test machine:



Open db source TEST from thread 1720362784

Source successfully connected

Database name: MySQL

Database version: 5.0.51a-community-nt-log

Driver name: libmyodbc5.so

Driver version: 05.01.0010

Driver ODBC version: 03.52

Close db source from thread 1685018368

Error in my_thread_global_end(): 1 threads didn't exit

Source successfully disconnected



I tried with a 3.51 driver and the result is the same.



Thank you to reply in order for me to know if this bug is well registered.



Kind regards



Pierre MARC
System Architect
Nirva Systems



Tel & mobile: +33 6 71 43 42 86



<http://www.nirva-systems.com> http://www.nirva-systems.com (in English)
<http://www.nirva-systems.com/fr/> http://www.nirva-systems.com/fr/ (en
Français)



Nirva Systems - 51 rue Deleuvre - 69004 Lyon - France



Discover Nirva's new features and functionalities for the fall 2011:
<http://www.nirva-systems.com/en/blog/NewsFall2011/NewsFall2011.html>
http://www.nirva-systems.com/en/blog/NewsFall2011/NewsFall2011.html