SAP Knowledge Base Article - Preview

2265959 - AS Java restarted/Crashed because Missed broadcast by network problems


The system is automatically restarting, you can see the following error contained in the std_serverX.out and/or the default trace files:

java.lang.Exception: Missed broadcast due to network problems. Restart is required (advanced Reconnect)


ERROR => Java node 'server0' terminated with exit code 335


FATAL: Critical shutdown with exit code [336] was requested due to [No notification from message server in 180000 ms. Triggering reboot of node.]

This error can be followed by exit code 333,334,335 or 336.



  • Release Independent
  • SAP NetWeaver


SAP Composition Environment all versions ; SAP NetWeaver all versions


missed broadcast, network problems, 333,  334,  335, 336,  FATAL Emergency shutdown terminated SfCJavaVm, FATAL: Critical shutdown. exit code [334] , exit code [335], exit code [336], rc=333, exiting (exitcode 333, retcode 1)., Kernel 745, Starting Framework, ms.reconnect.timeout, ms.confirmation.timeout, ms.notification.timeout , 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 ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.