Preventing early faulting of Java and Add-in instances

When you start a SAP Java or a SAP Add-In Application Server Instance, SAP automatically starts processes such as jc and jstart. Depending upon the available resources, starting these processes takes some finite time.

The agent for SAP WebAS allows enough time for SAP to start these processes successfully. The agent checks the status of these processes in definite intervals. While checking the status of these processes, if the processes are missing, the agent pauses for a time period that is equal to one-tenth of the value of the MonitorTimeout attribute before re-checking the status of the processes.

Symantec strongly recommends that the administrator set the MonitorTimeout attribute, such that the agent gives enough time for these processes to restart if a failure occurs.

For example, if an add-in server instance takes 9 seconds to restart a failed jstart process, you must set the value of the MonitorTimeout attribute to at least 90 seconds.