Qlik Community

Qlik Connectors Discussions

Discussion Board for collaboration regarding Qlik Connectors.

MVP & Luminary
MVP & Luminary

QVX SDK unexpected behavior

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

Labels (4)
4 Replies
Partner
Partner

Re: QVX SDK unexpected behavior

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.

https://support.qlik.com/articles/000059664

Plees ekskuse my Swenglish and or Norweglish spelling misstakes
MVP & Luminary
MVP & Luminary

Re: QVX SDK unexpected behavior

Thanks, good point! Will need to check if it's related.

MVP & Luminary
MVP & Luminary

Re: QVX SDK unexpected behavior

Unfortunately, this has not helped. I think this is related to QRS connections only..

MVP & Luminary
MVP & Luminary

Re: QVX SDK unexpected behavior

Some more info. In the Load Script log we do get this:

2019-09-12 14:58:52 0023 LIB CONNECT TO 'Mock (win8dev_ralf)'
2019-09-12 14:58:54 Connected.
2019-09-12 14:58:54 0025 Test:
2019-09-12 14:58:54 0026 SQL SELECT * FROM information_schema.tables
2019-09-12 14:59:24 Error: Connector is not responding (System error: WAIT_TIMEOUT)
2019-09-12 14:59:24 Execution Failed
2019-09-12 14:59:36 Execution finished.