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...
Question
Question
Answers
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.
Fixing the WebAccessAppPool Maximum Worker Process in advanced settings from 2 to 1 fixed the issue
Replies
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
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.
It is already set at this. Still getting the above errors.....
Fixing the WebAccessAppPool Maximum Worker Process in advanced settings from 2 to 1 fixed the issue
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.
Hi Alex, this restriction about worker processes still exists or we can configure it according to our cores (weblink 10)...¿?
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.
Ok, understand, no problem. Thanks for your answer!
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.
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.