When I create a multithreaded process in PB and create a NEW connection in that NVO I can see that connection and it continues to process (select 1... ) at the same time as my long running connection in my window. The window is frozen but the multithreaded NVO keeps processing.
BUT in a CMD window I do: netstat -an and I can see there are two active connections going to the database. I only want ONE connection.
We have a separate application that is looking at long running connections between machines (ie: the connections that you can see with netstat -an) and terminates them. So even if the database has a long timeout if the connection going to the database is not doing anything (for example running a long stored procedure) than the will get terminated.
I want to use one transaction object and start a long running stored procedure --- then in a multithreaded NVO use that same transaction object and ever so often send a select 1... to wake up that connection.
You mentioned ASE 16 has a new CI Timeout feature, I am not sure how that will help with another app terminating the connect (not ASE). Is there any white paper ... or something I can see that explains how ASE 16 allows multithreading on their single connections? thank you!!