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.