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

Question

Question

Session timeout occurred

Web Client
Updated April 17, 2018
asked on May 13, 2016

If a user logs into web access, is finished, logs out. Then they log back in they get an error. Session Timeout occurred. Please log in to the Laserfiche repository. They cannot log back in until IIS is reset. Then it happens all over again...

0 0

Answers

APPROVED ANSWER
replied on June 13, 2016 • Show version history

A support case had been opened for this issue and it was pointed out that web gardens aren't supported. Changing the maximum worker processes to 1 resolved the matter.

1 0
SELECTED ANSWER
replied on June 13, 2016

Fixing the WebAccessAppPool Maximum Worker Process in advanced settings from 2 to 1 fixed the issue

AppPoolSettings.png
AppPoolSettings.png (30.18 KB)
Download
0 0

Replies

replied on May 13, 2016

Here is the error that we get when they try to log back in. Again, they are clicking Log Out at the top right of the browser. They are not just closing the browser

you can then click logout, but when you try to log back in it keeps popping this box up

0 0
replied on May 13, 2016

Hi Casey, 

 

Could you open IIS, go to application pools, right click on WebAccessAppPool, click Advanced settings, and check the Request Limit? The value should be '0', which means the app pool can process an unlimited number of requests. 

0 0
View 5 previous replies
replied on June 9, 2016

It is already set at this. Still getting the above errors.....

0 0
SELECTED ANSWER
replied on June 13, 2016

Fixing the WebAccessAppPool Maximum Worker Process in advanced settings from 2 to 1 fixed the issue

AppPoolSettings.png
AppPoolSettings.png (30.18 KB)
Download
0 0
APPROVED ANSWER
replied on June 13, 2016 • Show version history

A support case had been opened for this issue and it was pointed out that web gardens aren't supported. Changing the maximum worker processes to 1 resolved the matter.

1 0
replied on April 16, 2018 • Show version history

Hi Alex, this restriction about worker processes still exists or we can configure it according to our cores (weblink 10)...¿?

0 0
replied on April 16, 2018

We have no plans to support multiple worker processes.  If you need to scale to more resources than a single process can use, you can load balance across machines as long as "session affinity" is enabled.  There is no single-machine/multiple-process equivalent for session affinity, which is approximately why it doesn't work.

0 0
replied on April 16, 2018

Ok, understand, no problem. Thanks for your answer!

0 0
replied on April 16, 2018

Also, to clarify, each process is not confined to a single core.  ASP.Net will create a thread pool to handle requests, and the size of the pool takes into account the number of cores available to the process.

0 0
replied on April 17, 2018

Ok, got it, my question was pointing to the fact that we recently upgraded the version of weblink from 9 to 10 and now we are experimenting very slow performance, the server is not showing stress, so we are making some tests to improve that performance and one of them was changing that variable in IIS. We are goint to keep looking for a possible cause.

 

Thanks for your help.

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

Sign in to reply to this post.

Details
Attachments
Related Posts
Loading ...