Walter Harris
Top achievements
Rank 1
Rank 1
Walter Harris
asked on 09 Nov 2009, 03:29 PM
We have an app that uses the TabStrip and RadMultiView (version 2009.1.527.35) to present several pages of information to the user that they can change. We are using a set of servers via NLB, and are using InProc Session State to keep track of the user's profile and settings. IP Affinity is turned on so that the user is not redirected to a different server (we even brought the other servers down to test this).
If the user goes to any tab, changes a set of controls on a single page, when they submit the changes/form, the process works fine. The script updates the backend Oracle database correctly, and returns the user to the proper page.
If however, the user makes changes on two or more tabs and hits submit, the session state is lost and forces the user to log back in. If this occurs, they lose the effort that they have gone through. If they again change more than one tabs' worth of components, this process will repeat. If they resort to changing one tab at a time, it works fine.
We are not sure if it is causing an App Pool recycle or if the object just "vanishes". At this point we are hoping that this may be something someone else has experienced and has a fix other than using cookies or a database to store data.
If the user goes to any tab, changes a set of controls on a single page, when they submit the changes/form, the process works fine. The script updates the backend Oracle database correctly, and returns the user to the proper page.
If however, the user makes changes on two or more tabs and hits submit, the session state is lost and forces the user to log back in. If this occurs, they lose the effort that they have gone through. If they again change more than one tabs' worth of components, this process will repeat. If they resort to changing one tab at a time, it works fine.
We are not sure if it is causing an App Pool recycle or if the object just "vanishes". At this point we are hoping that this may be something someone else has experienced and has a fix other than using cookies or a database to store data.
1 Answer, 1 is accepted
0
Walter Harris
Top achievements
Rank 1
Rank 1
answered on 12 Nov 2009, 07:39 PM
We've managed to determine what the issue was and have now fixed it...
IIS however was recycling the app pool due to a memory size limitation in our configuration. The control itself is now working fine if we do not have this configuration set.
IIS however was recycling the app pool due to a memory size limitation in our configuration. The control itself is now working fine if we do not have this configuration set.