We have implemented a custom connector using QVX API.
When a long running query during QVX_EXECUTE takes more than 30 secs before sending an QVX_OK (because database needs that time to calculate and give back a result set and first record), the connection is cancelled and pipe is closed by Qlik with sending unexpected QVX_DISCONNECT.
Expected behavior would be waiting until QVX_OK is send and data are written to pipe without closing the connection.
We can simulate that a "waiting time" of 29 secs works.
My question: is there a server setting to control this timeout? Can hardly imagine this is hard coded..
Can anyone help here please? Is there any other workaround or fix?
This is with Qlik Sense June 2019, version 13.32.2
Maybe it is related to this support case where the idle_in_transaction_session_timeout terminates any session with an open transaction that has been idle for longer than the specified duration, default 30 seconds.