Creating reports and dashboards | Stimulsoft community forum

Hello

We are carrying out some tests and notices that the query timeout field is not being respected, setting a value and even so the system does not respect the passed value.

Print and video follow.

expected action
https://www.stimulsoft.com/en/documenta ... ueries.htm
7 - The Query Timeout parameter is used to specify the execution time of a query, which means time during which the request will be executed. If the request timed out and the request failed, the user will see a message about this. The parameter value is indicated in seconds.

Hello,

We need some additional time to investigate the issue, we will let you know about the result.

Thank you.

Awaiting.

Hello.

We pass this value (or if defined StiOptions.Dictionary.getQueryTimeout()) to java.sql.Statement & it processed with corresponding DB driver. We can't influence it

Vadim.
I didn't understand.

The "StiOptions.Dictionary.getQueryTimeout" setting should not influence the query timeout in the report execution process in Stimulsoft.
Does this configuration not allow you to set a maximum value for the time a query can take to complete?

Hello.

By defaults StiOptions.Dictionary.getQueryTimeout is 0, so QueryTimeout for every java.sql.Statement takes from SqlSource, default value is 3000 sec = 5 min,
if StiOptions.Dictionary.getQueryTimeout not equals 0 -> QueryTimeout for every java.sql.Statement takes from StiOptions.Dictionary.getQueryTimeout

Vadim.
So if you set StiOptions.Dictionary.getQueryTimeout to 5 min for example, all java.sql.Statement statements will have a time limit of 5 min to complete execution. If a statement exceeds this limit, it should be stopped.
However this is not happening.

Hello.

TecnologiaMV wrote: ↑Thu Jul 06, 2023 11:45 am So if you set StiOptions.Dictionary.getQueryTimeout to 5 min for example, all java.sql.Statement statements will have a time limit of 5 min to complete execution.

Right

TecnologiaMV wrote: ↑Thu Jul 06, 2023 11:45 am If a statement exceeds this limit, it should be stopped.
However this is not happening.

We pass timeout value to java.sql.Statement (requests to DB) & it processed with corresponding DB driver. We can't influence it