some wierd things I am seeing, someone tell me what I'm missing here:
scenario 1) VB COM objects which open DB connections and run from a standalone VB app with random name. Connection objects are closed and destroyed after each query, with new ones created when needed for the next query. No pooling takes place regardless of settings in ODBC control panel as observed with Network Monitor - TCP connection to DB is closed immediately after each query and reopened before the next one with overhead of a bunch of other commands issued when the connection is opened.
scenario 2) same as above but with an extra connection opened when the application first starts. Nothing is done with this extra connection, it is just left open for application duration - connections are pooled.
scenario 3) same as scenario 1, but application is renamed to either "inetinfo.exe" or "dllhost.exe" - Connections are pooled.
Am I seeing things or is OLEDB really aware of what process it is in to avoid the braindead connection pooling algorithm of dropping the whole pool immediately whenever the number of logical connections drops to 0. I'm using the Oracle driver if this matters.
scenario 1) VB COM objects which open DB connections and run from a standalone VB app with random name. Connection objects are closed and destroyed after each query, with new ones created when needed for the next query. No pooling takes place regardless of settings in ODBC control panel as observed with Network Monitor - TCP connection to DB is closed immediately after each query and reopened before the next one with overhead of a bunch of other commands issued when the connection is opened.
scenario 2) same as above but with an extra connection opened when the application first starts. Nothing is done with this extra connection, it is just left open for application duration - connections are pooled.
scenario 3) same as scenario 1, but application is renamed to either "inetinfo.exe" or "dllhost.exe" - Connections are pooled.
Am I seeing things or is OLEDB really aware of what process it is in to avoid the braindead connection pooling algorithm of dropping the whole pool immediately whenever the number of logical connections drops to 0. I'm using the Oracle driver if this matters.
Facebook
Twitter