ADF BC Passivation and Activation

ADF BC Passivation and Activation

In production, when there will be high workload and many concurrent users, ADF will start to passivate Application Module instances.

Along with that if we want to passivate and activate our Transient Variable also then we need to check the Passivate check box in Transient Attribute level.

For More info - http://andrejusb.blogspot.in/2010/01/demystifying-adf-bc-passivation-and.html

Eg: Assume we have "DummyAttr" as Transient variable, and we are assigning value as shown below.

User will open Departments page and will set transient attribute value as shown above.

Will try to open next page - Employees, and will get java.lang.NullPointerException. Why? Let's find an answer in detail log. When there is not enough space in the pool (during next submit in our test case), and Application Module instance is passivated, transient DummyAttr attribute value was not passivated and this means it was simply lost:

So always good practice is to Pssivate our Transient variables and keep running in production with out fail.