Profile Parameters for the AS Java

rdisp/j2ee_error

Number of incorrect attempts to start an AS Java before the restart is deactivated.

By dynamically switching using parameter rdisp/j2ee_start, you can reactivate the restart.

Integer (number of attempts)

10

rdisp/j2ee_start

You can use this parameter to activate or deactivate starting the AS Java.

The start of the AS Java is automatically deactivated if a specific number of attempts ( rdisp/j2ee_error ) to start the server failed.

You can reactivate the start by dynamically changing this parameter to the value of 1.

Logical value

0

rdisp/j2ee_start_lazy

If this parameter is set to 1, the following applies:

If an AS Java is to be started (parameter rdisp/j2ee_start ), it is not started until the ABAP runtime environment has been fully initialized. This avoids problems that are caused by a long initialization phase.

If the parameter has the value 0 (default), then the AS Java can be started without waiting for the ABAP initialization.

Logical value

0

rdisp/j2ee_timeout

Within this time span, the AS Java must log on to the dispatcher. If not, it is assumed that the AS Java had problems starting and it is started again. You can determine the number of incorrect start attempts using parameter rdisp/j2ee_error . If this number of start attempts failed, this deactivates the AS Java from starting.

By dynamically switching using parameter rdisp/j2ee_start , you can reactivate the restart.

Seconds

60