Configuring application lazy start
By configuring application lazy start, you can release resources that are being consumed by inactive dynamic clusters so that other cluster instances in the cell can use these resources.
Before you begin
- Application lazy start requires that requests are routed through the on demand router. For more information about creating an on demand router, read about creating ODRs.
- Internet Inter-ORB Protocol (IIOP) and Java™ Message Service (JMS) requests cannot be used because they are not routed through the ODR. Do not use application lazy start on dynamic clusters that run Session Initiation Protocol (SIP) applications.
- Create a dynamic cluster. For more information, read about creating dynamic clusters.You can also configure application lazy start when you are creating a dynamic cluster.
About this task
Procedure
- Edit the dynamic cluster properties. In the administrative console, click.
- Select the If other dynamic clusters need resources, stop all instances of this cluster during periods of inactivity option.
- Set the Time to wait before stopping instances in minutes if the application placement controller determines that the resource is required by some other dynamic application cluster.
Results
What to do next
- You can configure the application lazy start without the
proactiveIdleStop
custom property configured, once a application request arrives, the application server instance will start, but lazy start will never stop it in future. - You can configure the application lazy start with the
proactiveIdleStop
custom property configured, the application server instance will stop after a specified time period. - You can configure a custom error page for the ODR that can be used for the 503 error. The error page can include an HTTP meta refresh tag that causes the browser to automatically send the request again after a certain waiting period. For more information about configuring custom error pages, read about configuring ODRs.