Symptom
After deployment/undeployment of an SDA of third party or partner (Ariba, Seeburger, Redwood etc) applications, AS Java fails to start and terminates at bootstrap phase. The following log entries can be detected:
- dev_jstart:
[...]
LOG => Process bootstrap stopped (pid 22596).
WARNING => Node bootstrap failed: result 1, exit code 559.
[...]
- dev_bootstrap:
[...]
LOG => SfCJavaVm: exit hook is called. (rc = 559)
********************************************************************************
*** ERROR => Java node 'Instance_bootstrap' terminated with exit code 559.
***
*** Please see section 'Java program exit codes'
*** in SAP Note 1316652 for additional information and trouble shooting advice.
********************************************************************************
LOG => exiting (exitcode 559, retcode 1).
[...]
- jvm_bootstrap:
[...]
[Bootstrap]> Configuration error. More details: Secure Store lib dir /usr/sap/<SID>/SYS/global/security/lib/tools does not exist.
[...]
Non of the KBAs help: 2015573, 2166965, 2573206.
Read more...
Environment
-
SAP NetWeaver Application Server Java all versions
-
Deployment/Undeployment of a third party or partner SDA
Product
Keywords
Seeburger sda, seeburger, redwood, bootstrap fails with exitcode 559, /usr/sap/<SID>/SYS/global/security/lib/tools, /SYS/global/security/lib/tools, /SYS/global, security/lib/tools, /security/lib/tools , KBA , BC-JAS-DPL , Deployment , BC-JAS-COR , Enterprise Runtime, Core J2EE Framework , BC-JAS-SF , Startup Framework , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.