1. For performance reasons, ADF keeps a pool of application modules in memory. It tries to give each session the same application module as the session used during the last request; however, this might not be possible during peak load of your application.
2. In this case, ADF saves the application modules state in a database table so the application module can be used by another session. This is called passivation.
3. When the first session needs the application module again, its state is retrieved from
the database process known as activation.
4. If you have made an error in your code and depend on some variable that is not persisted correctly when your application module state is stored, you will experience mysterious errors under high load.
Enable/Disable Application Module Pooling:
Right-click on your application module, choose Configurations.By default, each application module has two configurations. Ensure that the one ending in …Local is selected and then click Edit.
Then choose the Pooling and Scalability tab and deselect/select the checkbox to Enable/Disable Application Module Pooling.
Useful stuff
ReplyDelete