(JSTSG)(Kernel)Bootstrap-Exit556 - Java Server Troubleshooting Guide - Confluence

1
19/09/13 (JSTSG)(Kernel)Bootstrap-Exit556 - Java Server Troubleshooting Guide - Confluence wiki.scn.sap.com/wiki/display/JSTSG/(JSTSG)(Kernel)Bootstrap-Exit556 1/1 Added by Maria Jurova, last edited by Maria Jurova on Apr 19, 2009 Java Server Troubleshooting Guide (JSTSG)(Kernel)Bootstrap-Exit556 Problem AS Java stops with exit code 556 Symptom AS Java does not start Logs contain exit code 556 Solution Step 1 If you are using MaxDB, check if the log or data volumes are in a good shape (not full): The log volume should be in "overwriting" mode. If the data volume is full, add a new one. Step 2 Insert the property watchdog.timeout in cluster/bootstrap/bootstrap.properties and increase its value Note: The default value is 90000 ms (1.5 minutes). To increase the value, insert this line: watchdog.timeout=300000 Step 3 Restart the Java instance. Step 4 If the above steps did not help, report the problem and attach all logs from one of the folders: /usr/sap/<SID>/JC<XX>/work for Java Central instance (deprecated) /usr/sap/<SID>/J<XX>/work for Java Central or Dialog instance /usr/sap/<SID>/DVEBMGS<XX>/work - for ABAP/DoubleStack Central instance /usr/sap/<SID>/D<XX>/work - for ABAP/DoubleStack Dialog instance

description

(JSTSG)(Kernel)Bootstrap-Exit556

Transcript of (JSTSG)(Kernel)Bootstrap-Exit556 - Java Server Troubleshooting Guide - Confluence

Page 1: (JSTSG)(Kernel)Bootstrap-Exit556 - Java Server Troubleshooting Guide - Confluence

19/09/13 (JSTSG)(Kernel)Bootstrap-Exit556 - Java Server Troubleshooting Guide - Confluence

wiki.scn.sap.com/wiki/display/JSTSG/(JSTSG)(Kernel)Bootstrap-Exit556 1/1

Added by Maria Jurova, last edited by Maria Jurova on Apr 19, 2009

Java Server Troubleshooting Guide

(JSTSG)(Kernel)Bootstrap-Exit556

Problem

AS Java stops with exit code 556

Symptom

AS Java does not start

Logs contain exit code 556

Solution

Step 1

If you are using MaxDB, check if the log or data volumes are in a good shape (not full):

The log volume should be in "overwriting" mode.

If the data volume is full, add a new one.

Step 2

Insert the property watchdog.timeout in cluster/bootstrap/bootstrap.properties and increase its value

Note: The default value is 90000 ms (1.5 minutes). To increase the value, insert this line: watchdog.timeout=300000

Step 3

Restart the Java instance.

Step 4

If the above steps did not help, report the problem and attach all logs from one of the folders:

/usr/sap/<SID>/JC<XX>/work for Java Central instance (deprecated)

/usr/sap/<SID>/J<XX>/work for Java Central or Dialog instance

/usr/sap/<SID>/DVEBMGS<XX>/work - for ABAP/DoubleStack Central instance

/usr/sap/<SID>/D<XX>/work - for ABAP/DoubleStack Dialog instance