SAP Basis/Netweaver Tutorials, Monitoring, Administration(Certification) and FAQs Headline Animator

SAP Basis/Netweaver Tutorials, Monitoring, Administration(Certification) and FAQs


Thursday, 23 June 2016

How to resolve, if J2EE system is failing to start throwing “exit code 503” error?


This article answers following queries:

·         What is the reason for J2EE system failing with “exitcode 503”?
·         How to resolve, if J2EE system is failing to start throwing “exit code 503” error?
·         How to fix com.sap.engine.bootstrap.SynchronizationException: Database connection initialization error?
·         What is the location of log_bootstrap file?
·         How to prevent J2ee system start up failure with exit code 503?

-----------------------------------------------------------------------------
Sometimes, while bringing up sap netweaver java system, it fails to start. Upon investigation, we may notice following errors in dev_serverX file (i.e. dev_server0 or dev_server1)

*******************************************************

F [Thr 3408] *** LOG => SfCJavaVm: exit hook is called. (rc = 503)

F [Thr 3408] *** LOG => exiting (exitcode 503, retcode 1).

M [Thr 3408] CCMS: CCMS Monitoring Cleanup finished successfully.

********************************************************

 Analysis & Solution:

Exit code 503 means that the system couldn’t connect to the database. If we check log_bootstrap file located under /usr/sap/<SID>/<inst name>/work directory, following errors can be noticed

Message: [Exception occurred:]

com.sap.engine.bootstrap.SynchronizationException: Database connection initialization failed. Check if the database is running and the database properties.

 Reasons for this issue could be due to
i)             Unavailability of database: In this scenario, we need to check the database and make sure it is up. If required, we may have to restart it
ii)            Parameters maintained to connect to the database are wrong: In this scenario, we need to cross check parameters used to connect to the database for any typos or wrong locations or paths mentioned.

Wednesday, 22 June 2016

How to fix “Address already in use: JVM_Bind” error?


This article answers following queries:

·         How to resolve if dispatcher or server node of the J2ee application server fails to start?

·         How to fix “Address already in use: JVM_Bind” error?

·         How to address “Address already in use: JVM_Bind” error in std_dispatcher.out or std_server0.out log?

·         What is the location of std_server0.out file?

·         What is the location of std_dispatcher.out file?
---------------------------------------------------------------------------


In SAP Netweaver 7.0 environment, sometimes, dispatcher or server0 node of the J2EE application server fails to start. Please check various logs under work directory.

std_server0 and std_dispatcher.out files will be under /usr/sap/<SID>/inst_name/work directory.

Mainly, If we notice “Address already in use: JVM_Bind” errors in these files, then the issue is with port number. That particular port is being used by another process thus preventing java node to start.

To resolve this issue, we need to

i)             Go through above mentioned logs and identify the port that is being blocked

ii)            Identify the process that is using the port and kill that process. Various network tools like netstat can be used to identify the problematic process

iii)           Kill the problematic process or restart the HOST to release that port

iv)           Once that problematic port is released, restart the J2EE system