You are viewing limited content. For full access, please sign in.

Question

Question

503 Service Unavailable When Submitting a Form

asked on February 11, 2016 Show version history

We have had some users report that they receive a "503 - Service Unavailable" error message when they try to submit a form after working on it for approximately an hour.

The user still has internet access, is still logged into Forms, the application pool and the website are still working without issues.

I am guessing it is some kind of a timeout issue, but I wanted to see what others think before I go down that road. I have seen other posts about possible timeout issues, but with different error messages than what we are seeing.

If the guess is a timeout issue, what setting would I change (web.config, Website Configuration, Application Pool configuration, etc.)?

We are using Forms 10.0.0.1154.

1 0

Answer

SELECTED ANSWER
replied on February 12, 2016

When it comes to app pool recycling settings, i like the recommendations in this post. Basically, unless you're really pressed for resources or the server gets very little traffic, timing out the app pool when idle is not worth it.

2 0

Replies

replied on February 11, 2016

Anything in the Application or System event log? Maybe with source "WAS"?

0 0
replied on February 11, 2016

There is an item in the event log (informational) with the source WAS that mentions the application pool that Forms is set to use.

A worker process with process id of '5732' serving application pool 'FormsAppPool2' was shutdown due to inactivity. Application pool timeout configuration was set to 20 minutes. A new worker process will be started when needed.

Do you think the application pool timeout should be extended?

0 0
replied on February 11, 2016

We maintain a session state within the session table so that the timeout should have no effect.  If the session does become stale then I would expect the user to get an error from the forms server and not a 503 error.

0 0
replied on February 11, 2016 Show version history

Would changing the timeout for the application pool to 90 minutes have any negative effects?

I have gone through the links you posted and all of the items about the 503 error do not match the situation we are experiencing. That's why it's so frustrating. I will see about setting up the tracing part.

1 0
SELECTED ANSWER
replied on February 12, 2016

When it comes to app pool recycling settings, i like the recommendations in this post. Basically, unless you're really pressed for resources or the server gets very little traffic, timing out the app pool when idle is not worth it.

2 0
replied on February 12, 2016

I will give that a try Miruna. Thank you for your help and input.

1 0
replied on February 11, 2016

Hi,

I believe this isn't a Forms issue but more an IIS problem.  I looked on the internet and here are a few suggestions.

http://stackoverflow.com/questions/13322937/iis-http-error-503-the-service-is-unavailable

also enable tracing

http://www.iis.net/learn/troubleshoot/using-failed-request-tracing/troubleshooting-failed-requests-using-tracing-in-iis

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.