One Automation Webservice Timeout

[R Godfrey]

I have multiple  SOAP based webservices that are taking over 60 minutes to run.  After 60 minutes, Automic will show the job as blocked, however I can watch the job complete in it's main application.  Somewhere there is a timeout at 60 minutes.  The job has both &conn_timeout# and 
&read_timeout#  set to 7200 (2 hours).  Has anyone experienced this timeout?  Where else should I be looking?  Thank you!

[kay_koll_automic]

It is not recommend to work with long time out at web service calls.  The protocol the web service is using is not designed to wait for a long time until call is finished.  It is not reliable either, independent from Automic.

Would  it be possible to redesign the web service and split it a caller operation (which returns with runid/tracking code immediately) and an operation which checks whether the called service has finished or not. The second operation get executed periodically until the operation has returned that the service call has been finished.

[Winston_Hinton_9494]

Regardless, is there a way to set the client timeout on the Automic server? Unfortunately, I cannot work around a long running webservice call.

[Legacy User]

I've tested long running WS calls that were out for 2 hours or more and they never disconnected. Maybe you have some firewall rule in place that identifies the long running connection as idle and disconnects it? 

[R Godfrey]

Did you have to reconfigure your API timeout for two hours?  Out of curiosity which web service are you using?  We are using SOAP.

[Legacy User]

I'm just utilizing our internal web service using SOAP. I start a WS job that calls an Automic job that runs for > 2 hours. The return value is the Run#. The WS job stays active as long as the Automic job is active and as soon as it ends it returns the Run#. This is achieved by setting the connection timeout value inside the WS job to a value > 7200.

[Winston_Hinton_9494]

The default WCF timeout value is 600 seconds. I need to understand how this can be adjusted from the client side on the Tomcat server.

[Legacy User]

This would be in the server.xml --> Connector section

  <Connector port="8080" protocol="HTTP/1.1"

               connectionTimeout="20000"

               redirectPort="8443" />

The value is in milliseconds.

[Winston_Hinton_9494]

Thanks, Alexander!

[Winston_Hinton_9494]

Well, I was hopeful that would work, but it doesn't appear to be meshing with the WCF client side timeout conditions. The Automic SOAP calls are still timing out at 600 seconds. Any other thoughts?

[Legacy User]

Can you try the scenario described above using our internal web service to see if this job also times out after 600 seconds. This could help us narrow down if it's one of our components or just the different web services.

[R Godfrey]

We are using SOAP to connect to Costpoint and when called by Automic, I receive "The remote server returned an error: (503) Server Unavailable" after 60 minutes.  Oddly enough,  when I review the job in Costpoint, the job will continue to run to completion.  I feel like I'm missing something very obvious......