SAP Knowledge Base Article - Preview

1658385 - J2EE System fails with "exitcode = -334"


When you try to start the Java System, it stops, and the following entry can be found in the dev_serverX log:

[Thr 10284] JLaunchCloseProgram: good bye (exitcode = -334)

This issue can also appear if a service is not starting up in the giving time. std_serverX.out shows the following:

Loading [ClusterManager]... FATAL: Critical shutdown with exit code [334] was requested due to [Error getting confirmation reply during attach to cluster.]



SAP Netweaver Application Server Java


SAP NetWeaver 7.1 ; SAP NetWeaver 7.2 ; SAP NetWeaver 7.3 ; SAP NetWeaver 7.4 ; SAP NetWeaver 7.5 ; SAP enhancement package 1 for SAP NetWeaver 7.3


exitcode, -334, message, server, network, instability, JVM, garbage collector, gc, exit, code, NIPING, HaltTimeOut, LoadTimeout, ms.confirmation.timeout, [334] , confirmation  , cluster, Error getting confirmation reply during attach to cluster , KBA , kde , BC-JAS-COR , Enterprise Runtime, Core J2EE Framework , BC-CST-MS , Message Service , 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.