Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik GA: Multivariate Time Series in Qlik Predict: Get Details

Scheduled task executions fail with 'Connection parameters were not received in time' error

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
TalendSolutionExpert
Contributor II
Contributor II

Scheduled task executions fail with 'Connection parameters were not received in time' error

Last Update:

Jan 22, 2024 9:35:30 PM

Updated By:

Jamie_Gregory

Created date:

Oct 10, 2023 6:44:09 AM

Problem

Scheduled task executions fail with the following error message:

Connection parameters were not received in time.

 

Root cause

A possible cause for this error is that communication is disrupted, and the transferring of artifacts and parameters is retried but not completed in time.

 

Solution

If the delay is minor, you can increase the timeout so that the engine will wait longer at times of latency and not cause failures.

 

You can set the connection.parameters.timeout setting in <Remote Engine Install>/etc/org.talend.ipaas.rt.deployment.agent.cfg.

 

For example:

wait.for.connection.parameters.timeout = 600
flow.deployment.timeout = 600
Labels (1)
Comments
ITCC
Contributor
Contributor

dear support, these settings were already in place, and it was working till tuesday with such, and no more since wednesday; no change reported this week, except yesterday the on-premise server hostng the talend remote engine that was rebooted abruptly

# In seconds
wait.for.connection.parameters.timeout=600
flow.deployment.timeout=600

Sonja_Bauernfeind
Digital Support
Digital Support

Hello @ITCC 

It looks to me as if you were attempting to post this comment in your ongoing case with Support. I will forward this information to them.

All the best,
Sonja

ITCC
Contributor
Contributor

Thanks a lot

Version history
Last update:
‎2024-01-22 09:35 PM
Updated by: