Some customers mention that after a certain period of inactivity, the Application Module pool is completely empty.
This happens even though jbo.ampool.minavailablesize (Minimum Available
Size) is greater than 0.
The reason is that after x milliseconds, we consider an AM instance in the pool as a candidate for removal during
the next resource cleanup regardless of whether it would bring the
number of instances in the pool below jbo.ampool.minavailablesize.
This is specified by parameter jbo.ampool.timetolive (Maximum Instance Time to Live) with has a default of one hour (3600000 milliseconds).
For more details, see Understanding Application Module Pooling Concepts and Configuration Parameters and Topic 29.6.2 Pool Sizing Parameters in the ADF Developer's Guide
« JDeveloper 10.1.2.2 Maintenance Release | Main | Set jbo.ampool.doampooling=false to Reproduce Problems Related to AM Passivation / Activation »
Application Module Pool Empty After a Certain Period of Inactivity
Search All Blogs
Google Search
About This Entry
This page contains a single entry from the blog posted on November 12, 2006 7:44 AM.
The previous post in this blog was JDeveloper 10.1.2.2 Maintenance Release.
The next post in this blog is Set jbo.ampool.doampooling=false to Reproduce Problems Related to AM Passivation / Activation.
Many more can be found on the main index page or by looking through the archives.
