You can tell the pool when it should start recycling existing, inactive application module instances. It's default value is 10. The number of am instances it will create before recycling ams that have an associated state.
A high recycle threshold reduces checkout times, because the pool doesn't have to reactivate an am state as frequently. The cost is more am instances in the pool. Memory vs performance.
When you start the business logic tier's Java VM, include the following directive on the command line:
-Djbo.recyclethreshold=n
A number from 0 to 2,147,483,647.
Alternatively, you can enter a line in the jboserver.properties file, which is stored in \lib\jbomt.zip. During deployment, you need to include the file.
jbo.recyclethreshold=n
In the Workspace view of the Navigator, right-click a business component project and choose Properties.
In the Run/Debug panel, type the parameters in the Java VM Parameters field.
Click OK.
The values are added to the jboserver.properties file, which is stored in \lib\jbomt.zip.
Related topics
Pooling Application Modules
About Application Module Pooling
About Application Module Pooling Classes
About
Configuration Properties for a JSP Project