lbracchi opened a new issue, #9072: URL: https://github.com/apache/hop/issues/9072
### Apache Hop version? 2.19 ### Java version? jdk-21.0.11+10 ### Operating system Windows ### What happened? ### Description When using the SSH Commands step to execute scripts or commands that take longer than 120 seconds to complete or return output, the step fails with a timeout error. Note that this behavior did not occur in Apache Hop 2.17 using Java jdk-17.0.16+8, making this likely a regression or a newly introduced hardcoded limit in newer versions. It would be very helpful to either remove/increase this limit or, ideally, make the timeout configurable via the step properties so that long-running remote jobs can execute successfully without failing prematurely. ### To Reproduce Steps to reproduce the behavior: - Create a new pipeline in Apache Hop 2.19. - Add an SSH Commands step pointing to a reachable remote server. - Configure a command or script that sleeps or takes longer than 2 minutes to finish (e.g., sleep 150). - Run the pipeline. - Observe the error after exactly 120 seconds. ### Expected Behavior The SSH Commands step should wait for the script to finish executing or respect a user-defined timeout setting, behaving as it did in version 2.17. ### Issue Priority Priority: 0 ### Issue Component Component: Transforms -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
