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

Discussion

Discussion

Forms public form timeout

Forms
Updated September 6, 2018
posted on September 6, 2018

Hello.

I see that the forms login timeout is set here

      <forms loginUrl="~/Account/LogOn" timeout="20160" name=".LFFORMSAUTH" slidingExpiration="false" />

 

Where is the public form timeout. We had a user get the Invalid form data error with a public form and I thought there was no timeout.

 

0 0
replied on September 6, 2018

The default timeout for anonymous users is 4 days. The idea is to prevent the database from growing too large when there are many concurrent anonymous sessions. You'll want to change the value of  AnonymousSessionTimeout in the cf_options table of the Forms database. More details in this white paper.

0 0
replied on September 6, 2018

The Error Below is code for "Timeout" right? This was what I found in previous answers discussions.  The reason I ask is because this happened to 2 users, yesterday afternoon, within a 10 minute timeframe. I can't imagine 2 people leaving the form open for 4 days.

-

Invalid form data was sent to the server. This can occur if the form is out of date. Please refresh this form and try again. [LFF2106-InvalidDataSent]

0 0
replied on September 6, 2018

Oh I found another post that might explain. It is the automatic recycle setting in the FormsAppPool.

https://answers.laserfiche.com/questions/110954/Invalid-Form-Data-was-sent-t-the-server#115615

0 0
replied on September 6, 2018 • Show version history

Wait a minute, why is this even configured? I don't even want to do the proposed recommendation to set a specific time, say Midnight. Since that means, if someone opens a form at 11:30, and submits it at 12:10, they will get the same error. What is the purpose of this configuration? How do I set the timeout to be 4 days from the individual user login, or even 4 hours would be fine.

 

Just verified I have overlapped recycle enabled, this was the default on forms installation.

 

"In an overlapped recycling scenario, the process targeted for a recycle continues to process all remaining requests while a replacement worker process is created simultaneously. The new process is started before the old worker process stops, and requests are then directed to the new process. This design prevents delays in service, since the old process continues to accept requests until the new process has initialized successfully, and is instructed to shut down only after the new process is ready to handle requests."

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

Sign in to reply to this post.

Details
Related Posts
Loading ...