Troubleshooting: AS Java Bootstrap Stops with an Exit Code 

Symptom

AS Java stops with an exit code because the AS Java bootstrap module failed to synchronize the system’s files.

Scenario Type: Error analysis

SAP NetWeaver Component: Application Server Java (AS Java)

Analysis

The bootstrap module collects metadata about the instance and the files it has to synchronize and then downloads the required files to the file system. It can fail to synchronize the system's files for the following reasons:

●      The database was not started or is corrupted

●      Incorrect or missing file system permissions

●      Wrong installation type (32 bit binaries on 64 bit machine)

●      Errors in the bootstrap logic

Problem Areas

Depending on the kind of problem that caused the bootstrap to fail, you can have an exit code from one of the following problem areas:

Database connectivity/consistency

This category includes problems with the connection to the database and the database consistency. The exit codes are: 503, 504, 505, 506, 507, 508, 509, 511, 512, 513, 515, 516, 517, 518, 519, 520, 521, 524, 525, 526, 527, 528, 529, 530, 532, 542, 546, 548, 549, 550, 551.

More information: Bootstrap Stops Due to Database Problems

File system

The problems in this area are connected mainly with file system access permissions. The exit codes are: 514, 522, 523, 531, 541, 533, 534, 535, 536, 537, 538, 539, 540, 543, 544, 547, 552.

More information: Bootstrap Stops Due to File System Problems

Configuration properties

The area includes problems with the configuration of the bootstrap module. The exit codes are: 501, 502, 510, 545.

More information: Bootstrap Stops Due to Configuration Problems

 

Further Information

If you are unable to identify the problem or cannot solve the problem following the suggested steps, create a CSS message under the component BC-JAS-COR with short text "Bootstrap exit code XXX", where XXX is the exit code from the bootstrap process. The exit code can be found in dev_bootstrap file. Collect the bootstrap logs and attach them to the created CSS message.

If the offline bootstrap process finished successfully, but the server process fails to start because of a problem related to the bootstrap, collect and attach the server logs too.