If you have a new question you’d like our support staff to post a response to, please visit our customer community, GoAnywhere Insiders, to pose the question in our Discussion Boards. We have a thread “Ask Our Tech Experts” that our support team monitors on a regular basis, or you can start a new discussion where other GoAnywhere users and support staff can weigh in. Log in or create your new account at https://insiders.goanywhere.com
If you need an immediate response, please create a support ticket or contact our support team by email at [email protected]
- Posts: 10
- Joined: Tue Mar 27, 2012 7:59 pm
We are using the Execute SSH Command task in a central Project (cmdRunner) to run commands on a remote Linux server. This cmdRunner Project is called from various other Projects usually 2 to 6 times within a given Job run. This works great except that when we get more then 20 jobs running at the same time we end up overloading the authentication service on the remote Linux server. To reduce the load on the authentication service we would like to maintain the same session over the entire run of the Job as it goes in and out of various Projects but it seems like as soon as you exit a Project it drops the session. Is there a way to maintain a session between Projects in the same Job?
- Posts: 592
- Joined: Tue Jul 17, 2012 2:12 pm
- Location: Phoenix, AZ
Currently, we do not allow persistent connections on executeSSH tasks.
You could always submit an Enhancement Request to try and get this added to a future release!
Lead Solutions Consultant
Return to “Community Forum”