J2EE Engine Startup Errors codes and their Description

1. Positive exit codes which usually cause restart of server/dispatcher:

0      normal exit/shutdown
1      Forced shutdown was executed by the engine server side because of a non  
       recoverable error.
11     xml parser cannot be initialized by the engine server side.
64     Error while reading the properties for bootstrap process.
65     Error when bootstrap process tries to connect/work with the data
       base.
66     Common error code for issues in bootstrap process. Check note 997510.
666    Could be caused by memory misconfiguration or memory leak of applications 
       involved. During startup misconfiguration is more reasonable. Under special
       circumstances a hotspot error is generated instead of an
       OutOfMemoryError (Note 597187).
888    When the shutdown of the server/dispatcher process cannot finish for the  
       preconfigured timeout, the VM is halt with this exit code. This happens if 
       there are many applications deployed on the system and some of them take 
       significant time to finalize the usage of common resources. Usually this is 
       not an issue as long as the consecutive engine start is flawless.
999    When an error occurs during engine shutdown the server/dispatcher process 
       will exit with code 999. 

2. Negative exit codes which usually will not cause restart of server/dispatcher:

-1     JSTARTUP_INTERNAL_ERROR
       This code is also used when experiencing issues with Wily Introscope. The 
       dev_server log file in the work directory contains the following message:
       [Thr 7920] *** ERROR => can't find native registration class
       [com.sap.bc.proj.jstartup.JStartupNatives] [jhvmxx.c     551]
       Exception in thread "main" [Thr 7920] JLaunchCloseProgram: good
       bye (exitcode = -1).

-2     JSTARTUP_VM_ABORTED

-3     JSTARTUP_INVALID_ARGUMENTS

-4     JSTARTUP_INVALID_SHUTDOWN

-6     comes from within the VM itself, in dev_jcontrol:
       ERROR => JHVM_LoadJavaVM: Cannot create Java VM (rc=-6)
       please check std_server.out, might be wrong parameter

-10    JSTARTUP_NO_MORE_MEMORY

-11    JSTARTUP_PARENT_ATTACH_ERROR

-12    JSTARTUP_TIMEOUT

-13    JSTARTUP_SYNC_SEMAPHORE_ERROR

-14    JSTARTUP_INVALID_PROPERTY_FILE

-15    JSTARTUP_INVALID_VMTYPE

-16    JSTARTUP_NO_PERMISSION

-17    JSTARTUP_INVALID_JDK

-18    JSTARTUP_NODE_NOT_FOUND

-100   JSTARTUP_NO_SYSTEMNAME

-101   JSTARTUP_PARAM_NOT_EXISTS

-102   JSTARTUP_INVALID_LOCAL_PROFILE

-103   JSTARTUP_CREATE_LOCAL_PROFILE

-104   JSTARTUP_NO_MORE_PROCESSES

-105   JSTARTUP_INVALID_PROCESS

-106   JSTARTUP_PROGRAM_ALREADY_RUNS

-107   JSTARTUP_SHM_NOT_INITIALIZED

-108   JSTARTUP_DEBUG_SESSION_ALREADY_ACTIVATED

-109   JSTARTUP_DEBUG_SESSION_NOT_ACTIVATED

-333   server/dispatcher process is restarted because it has missed a cluster 
       broadcast message due to network problems.

-334   server/dispatcher process is restarted because of error getting confirmation 
       during reattach to the message server.

-335   server/dispatcher process is restarted because of timeout for reconnecting to 
       message server has reached.

-336   server/dispatcher process is restarted because no notification is received 
       from message server.

-337   server/dispatcher process is restarted because exits listener loop.

-338   server/dispatcher process is restarted because of invalid message.

-339   client is not authorized to access the message server.

-1000  JSTARTUP_PROCESS_IS_STOPPED.

-1001  JSTARTUP_PROCESS_WAITERROR

-1501  server/dispatcher process is not able to start because the initialization of 
       some manager ends up with error.

-11111 server/dispatcher process is stopped due to license expiration.

-11112 server/dispatcher explicit shutdown is invoked from shell command or Visual 
       Administration tool. No restart will be performed. Not a problem.

-11113 Essential service fails to start so the server/dispatcher process should exit.

-11114 Services load timeout has been reached. In case the value of
       "haltOnServiceTimeout" property of ServiceManager is true server/dispatcher 
       process would exit.