500 read timeout error

Hi,
I have a TeamSite workflow. Workflow has an external task.
The external calls a perl script that resides in
home>/httpd/iw-bin/gl (script name Request.cgi).
This script makes http call to another application
to create submission. However the appication
take long time to send response back to the cgi. This
results in 500 read timeout error.
Now my question is, is there any way we can increase this
timeout to hours so that the cgi waits for the request to
complete (which may take an hour or more)?
Please let me know.

I have attached the cgi and Error.log here. You can
check how the cgi makes call and how the error is printed in
the log. Please let me know if more information is needed.

Thanks
-Gautam

Find more posts tagged with

Comments

vaibhav2288

Hi,
I have a TeamSite workflow. Workflow has an external task.
The external calls a perl script that resides in
home>/httpd/iw-bin/gl (script name sendRequestToGL.cgi).
This script makes http call to Globallink content director
to create submission. However GlobalLink content director
take long time to send response back to the cgi. This
results in 500 read timeout error.
Now my question is, is there any way we can increase this
timeout to hours so that the cgi waits for the request to
complete (which may take an hour or more)?
Please let me know.

I have attached the cgi and teamsiteError.log here. You can
check how the cgi makes call and how the error is printed in
the log. Please let me know if more information is needed.

Thanks
-Gautam

I think you should use the timeout link and add the timeout to hour or any number of minutes, untill that time task will remain on the external and as the times completes it will go to next task.

Also you have not added cgi and error log. What version of teamsite ? Whether WFM or WFT you are using ?

padmanabh

Hi Vaibhav,
Thanks for your reply. I am using wft. It's not an issue with task. Task remains waiting till I do a callback. So I can decide when to callback. However the request times out. It does not wait for the response from the application and proceeds with timeout error. So even though the application successfully processes request in say 60 minutes, I get the timeout in 5 minutes and so the workflow always thinks that the task failed. So I would like to know a way for the request to hold for response till the actual response comes back. So what is the way to increase this timeout?
I have attached the files for your reference. the worklow has an external task that calls the request.cgi. also find the log.

Thanks
-Gautam

Rick Poulin

The external calls a perl script that resides in
home>/httpd/iw-bin/gl (script name Request.cgi).

#1, this is a bad place for your script. It's where CGI tasks must reside, and other screens which are called by your users on the UI. Internal-use perl scripts like external tasks should ideally be in /local/bin. Just pointing this out as a best practice, as I don't think it has anything to do with your problem. I certainly hope you did mean external task and not CGI task, as I don't know of any user that will sit there for an hour, waiting for something to happen.

This script makes http call to another application
to create submission. However the appication
take long time to send response back to the cgi. This
results in 500 read timeout error. Now my question is, is there any way we can increase this timeout to hours so that the cgi waits for the request to
complete (which may take an hour or more)?

I would expect that the timeout actually occurs on the other end (where your called service is hosted) -- this would be typical for 5xx errors (they're returned by HTTP servers, not HTTP clients). There are some things you could look at doing on your service to keep the socket alive all this time, but that is contrary to how the web works. You should consider either using a different transport (perhaps an actual TCP socket) or rewrite your app to send the original request and have the service immediately return a request ID. Then, your script can ping the service every X minutes to ask "is request ID 1234 done yet?".

padmanabh

Thank you very much rpoulin and Vaibhav for your suggestions and solutions!
I actually got around it just by increasing the timeout of the user agent.
$ua->timeout( $config->{timeout} );
This was set to 5 minutes. I increased it to an hour and my issue was resolved. I can increase the timeout value as needed.

Thanks again for your help!
-Gautam