SAP Knowledge Base Article - Preview

3443172 - ServerX node get restart when do failover of SCS instance in AS Java system

Symptom

AS Java is installed as High Availability (HA).
When do failover of SCS instance from one node to another node, notice serverX node get restarted. 
Want to know if this is expected behavior or not.

When check serverX log can see following log:

usr/sap/<SID>/<xx>/work/dev_serverX:
-------------------
F  [Thr 7780] *** LOG => SfCJavaVm: exit hook is called. (rc = 11114)
-------------------

usr/sap/<SID>/<xx>/work/std_serverX.out:
-------------------
FATAL: Critical shutdown with exit code [11114] was requested due to [Enque Server was restarted without restarting the J2EE engine. This could lead to data inconsistencies and requires a restart of the entire system.]
-------------------

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."


Read more...

Environment

  • SAP NetWeaver Java system

Product

SAP NetWeaver Application Server for Java all versions

Keywords

fail-over, fail over, java engine, single java stack, pure java, locking manager,  , KBA , BC-JAS-COR , Enterprise Runtime, Core J2EE 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.