Workflow with Oracle Connector and Db Table Selector using Custom Query gets Timeout

[b_kochs]

Hello

I created a workflow which uses Oracle Connector and Db Table Selector to execute a custom Query;
a select which runs for at least 3 minutes.
While designing the workflow executing mentioned nodes works fine; there is a execution time of about 3 minutes. The whole workflow runs fine localy.
Which parameter and where is to be set , so that knime server waits until the sql-select has finished?

Thanks in advance
Greetings B.Kochs

[b_kochs]

For further analysis. knime.log ______________________________________________________
2022-05-12 16:08:21,589 : WARN : pool-1-thread-15 : c3ea4b8e-af39-4be9-be4f-8b49f384936a : JsonRpcErrorResolver : : : A json rpc error occurred
com.knime.gateway.api.webportal.service.util.ServiceExceptions$TimeoutException: Workflow didn’t finish before timeout
at com.knime.gateway.impl.webportal.service.DefaultWizardExecutionService.waitUntilDoneAndReturn(DefaultWizardExecutionService.java:397)
at com.knime.gateway.impl.webportal.service.DefaultWizardExecutionService.executeToNextPage(DefaultWizardExecutionService.java:361)
at com.knime.gateway.impl.webportal.jsonrpc.service.JsonRpcWizardExecutionServiceWrapper.executeToNextPage(JsonRpcWizardExecutionServiceWrapper.java:66)
at jdk.internal.reflect.GeneratedMethodAccessor130.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.base/java.lang.reflect.Method.invoke(Unknown Source)
at com.googlecode.jsonrpc4j.JsonRpcBasicServer.invoke(JsonRpcBasicServer.java:478)
at com.googlecode.jsonrpc4j.JsonRpcBasicServer.handleObject(JsonRpcBasicServer.java:349)
at com.googlecode.jsonrpc4j.JsonRpcBasicServer.handleJsonNodeRequest(JsonRpcBasicServer.java:274)
at com.googlecode.jsonrpc4j.JsonRpcBasicServer.handleRequest(JsonRpcBasicServer.java:242)
at org.knime.gateway.impl.jsonrpc.JsonRpcRequestHandler.handle(JsonRpcRequestHandler.java:103)
at com.knime.gateway.executor.jsonrpc.JsonRpcServerRequestHandler.handle(JsonRpcServerRequestHandler.java:77)
at com.knime.enterprise.executor.genericmsg.GenericServerRequestManager.forwardRequest(GenericServerRequestManager.java:82)
at com.knime.enterprise.executor.amqp.actions.GenericServerRequestTask.perform(GenericServerRequestTask.java:66)
at com.knime.enterprise.executor.amqp.RabbitMQMessageConsumer$Consumer.processMessage(RabbitMQMessageConsumer.java:133)
at com.knime.enterprise.executor.amqp.RabbitMQMessageConsumer$Consumer.handleDelivery(RabbitMQMessageConsumer.java:107)
at com.rabbitmq.client.impl.ConsumerDispatcher$5.run(ConsumerDispatcher.java:149)
at com.rabbitmq.client.impl.ConsumerWorkService$WorkPoolRunnable.run(ConsumerWorkService.java:104)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)

---

[b_kochs]

Hi
I changed the setting in preferences.epf , where also the jdbc driver is configured:
/instance/org.knime.workbench.core/database_timeout=600
and restartet both services.
… with no avail: the Workflow is interrupted after ca. 2 minutes.

[JoergWas]

Hello @b_kochs,

can you please try to edit the oracle.jdbc.ReadTimeout parameter in the Oracle Connector in the “JDBC Parameters” tab like this?

It is also strange that the DB Table Selector node takes that long to execute. Can you provide an example of the workflow?

Best regards
Jörg

[JoergWas]

Hi @b_kochs,
additionally, what KNIME server version are you currently using?
Best regards
Jörg

[b_kochs]

Hello JoergWas,

sticking on an timeout-error mentioned in a log file can sometimes be misleading.
You can consider the case solved. Thanks.