[SOLVED] Application restarting with "Maximum Worker Processes" Greater then one

Answered
0
0

whenever the “Maximum Worker Processes”  of the application pool is increase from 1, the application keeps restarting. Setting it back to 1, the application works as expected. Are there other settings i need to set alongside the “Maximum Worker Processes” to make it work?

section of defaut.json

“sessionTimeout”: 0,
“autoReload”: true,
“responseTimeout”: 5000,
“secure”: true,
“enableWebSocket”:true,
“pollingInterval”:1000,
“dropDuplicateClicks”:true,
“debug”:false,
“showLoader”:false,
“loaderTimeout”:0,
“keepAliveInterval”:300,
“validateClient”:true

 

  • You must to post comments
Best Answer
0
0

The application doesn’t restart. What you see is the session being created when the request hits a different process.

it’s the same as load balancing without session affinity.

Keep the default value of 1. Increasing that number doesn’t provide any benefit in this case. It’s mostly for asp.net apps with session stored on file or db that have to run long requests since aspnet cannot handle background threads easily.

if you need to start a long process with Wisej use Application.StartTask.

  • You must to post comments
Showing 1 result
Your Answer

Please first to submit.