Re: Problem in SQLFreeHandle (Statement)

I was able to login with the olddominion login and download the file
(This is normal FTP , this is NOT SFTP)
Using port 21
Which port are you using?

Barry Bell
Senior Developer/Analyst
Logistics
Harte Hanks
1525 NW 3rd ST
Deerfield Beach FL, 33442
954-429-3771 Ext 267 office
954-281-1464 fax
[https://4b2685446389bc779b46-5f66fbb59518cc4fcae8900db28267f5.ssl.cf2.rackcdn.com/email-sig-hh.png]<http://www.hartehanks.com/>
hartehanks.com<http://www.hartehanks.com> / linkedin<http://www.linkedin.com/company/hartehanks> / twitter<http://www.twitter.com/HarteHanks> / facebook<http://www.facebook.com/HarteHanks>

From: pgsql-odbc-owner(at)postgresql(dot)org [mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Jade Koskela
Sent: Tuesday, June 17, 2014 4:06 PM
To: Heikki Linnakangas; pgsql-odbc(at)postgresql(dot)org
Subject: Re: [ODBC] Problem in SQLFreeHandle (Statement)

I couldn't reproduce the behavior using the test program, or a similar one.
I recompiled the driver to enable extra logging.
Here is the grep on ENTER_CONN_CS, the second address is the address of the mutex (pthread recursive).
This was compiled on OSX with Clang, and then also with GCC with the same result. Behavior doesn't reproduce on Windows.

[140735257568016][[SQLFreeHandle]]

[140735257568016]*** ENTER_CONN_CS [140210608634616] ***

[140735257568016]*** ENTER_CONN_CS [140210608634616] ***

[140735257568016]*** LEAVE_CONN_CS [140210608634616] ***

[140735257568016]*** LEAVE_CONN_CS [140210608634616] ***

[140735257568016]*** LEAVE_CONN_CS [140210608634616] ***

[140735257568016][SQLGetConnectAttrW]

[140735257568016]*** ENTER_CONN_CS [140210608634616] ***

[140735257568016]*** LEAVE_CONN_CS [140210608634616] ***

[140735257568016][SQLGetConnectAttrW]

[140735257568016]*** ENTER_CONN_CS [140210608634616] ***

[140735257568016]*** LEAVE_CONN_CS [140210608634616] ***

[140735257568016][SQLGetConnectAttrW]

[140735257568016]*** ENTER_CONN_CS [140210608634616] ***

[140735257568016]*** LEAVE_CONN_CS [140210608634616] ***

[4466282496][[SQLAllocHandle]]

[4466282496]*** ENTER_CONN_CS [140210608634616] *** <- new thread grabbed mutex, count=1

[4466282496]**** PGAPI_AllocStmt: hdbc = 0x7f8553857000, stmt = 0x7f8552d17100

[4466282496]*** LEAVE_CONN_CS [140210608634616] *** <- count=0

[4466282496]**** PGAPI_Prepare: STMT_ALLOCATED, copy

[4466282496]*** ENTER_CONN_CS [140210608634616] *** <- count=1

[4466282496]*** ENTER_CONN_CS [140210608634616] *** <- count=2

[140735257568016]*** LEAVE_CONN_CS [140210608634616] *** <- this thread doesn't own, count=2

[4466282496]*** LEAVE_CONN_CS [140210608634616] *** <- count=1

[4466282496]*** LEAVE_CONN_CS [140210608634616] *** <- count=0

[4466282496]*** LEAVE_CONN_CS [140210608634616] *** <- count=0

[140735257568016][[SQLFreeHandle]]

[140735257568016]*** ENTER_CONN_CS [140210608634616] *** <-thread blocks on mutex here, should be unlocked?

On Thu, Jun 12, 2014 at 6:30 AM, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com<mailto:hlinnakangas(at)vmware(dot)com>> wrote:
On 06/12/2014 05:30 AM, Jade Koskela wrote:
Hello,
I am using psql-odbc 9.3 on OSX.

Which version, exactly? There were some changes to locking in SQLFreeHandle in 09.03.0200. Not sure if those changes might've fixed this, or caused it.

Can easily you test on another platform, or with different version of unixODBC?

I have one thread running a query, and
another thread cancels the query using SQLCancel. The thread running the
query successfully cancels and exits the driver code. When we try to free
the statement handle, it blocks on a mutex doing ENTER_CONN_CS, or
something similar in SQLFreeHandle.

Does anyone have any input on this problem? I don't see who is holding the
mutex, the thread running the query is done.

I tried to reproduce this with the attached little test program. It works fine. Can you post the test program you're using, or modify the attached so that it exhibits the behavior you're seeing, please?

- Heikki