![]() ![]() ![]() All event logs are empty of any errors involving the state service.It is almost as if something in the state service is faulting, and causing the application to fall back to using InProc.ĭoes anyone have any ideas as to what might be causing this? Here's some of the troubleshooting steps we've done: This is completely divorced from the main application and exhibits the exact same behavior, so I'm fairly confident this is environmental. I also deployed a small test application that does nothing except store and retrieve data from session state. At the application level, all configuration settings appear to be identical. I've searched high and low for a solution but have come up empty. On the test machine, using the exact same code and config files, recycling an app pool while using either InProc or the State Service causes session state to be lost. Configuring the application to use the ASP.NET State Service maintains the session Setting to InProc works as expected: session state is maintained until the application pool is recycled, at which time it is lost. This is, of course, not the case locally. We're having an issue in some production environments where, despite having our application configured to use the state service properly, recycling the app pool hosting the application causes all state to be lost. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |