C++ client is not propagating a connection failed error when a drillbit goes down

When a drillbit goes down, there are two conditions under which the client is not propagating the error back to the application -
1) The application is in a submitQuery call: the ODBC driver is expecting that the error be reported thru the query results listener which hasn't been registered at the point the error is encountered.
2) A submitQuery call succeeded but never reached the drillbit because it was shutdown. In this case the application has a handle to a query and is listening for results which will never arrive. The heartbeat mechanism detects the failure, but is not propagating the error to the query results listener.