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. Support component for this case is
BC-JAS-COR.
11
xml parser cannot be initialized by the engine server side. Support
component for this case is BC-JAS-COR.
64
Error while reading the properties for bootstrap process. Support
component for this case is BC-JAS-COR.
65
Error when bootstrap process
tries to connect/work with the database. Support component for this case is
BC-JAS-COR.
66
Common error code for issues in bootstrap process. Check note 997510 if
this does not provide a solution send it to
666
Out of memory case. 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. Support
component - BC-JAS-COR.
999
When an error occurs during engine shutdown the server/dispatcher
process will exit with code 999. Support component for this case
is BC-JAS-COR.
2.
Negative exit codes which usually will not cause restart of server/dispatcher:
-1 JSTARTUP_INTERNAL_ERROR. Support component
for this case is BC-JAS-SF.
This code is also used when
experiencing issues with Wily Introscope. The dev_server<No> 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. Support component for this case is BC-JAS-SF.
-3
JSTARTUP_INVALID_ARGUMENTS. Support component for this case is
BC-JAS-SF.
-4
JSTARTUP_INVALID_SHUTDOWN. Support component for this case is BC-JAS-SF.
-6... comes from within the VM itself, in
dev_jcontrol:
ERROR => JHVM_LoadJavaVM:
Cannot create Java VM (rc=-6)
please check
std_server<no>.out, might be wrong parameter
-10
JSTARTUP_NO_MORE_MEMORY. Support component for this case is BC-JAS-SF.
-11
JSTARTUP_PARENT_ATTACH_ERROR. Support component for this case is
BC-JAS-SF.
-12
JSTARTUP_TIMEOUT. Support component for this case is BC-JAS-SF.
-13
JSTARTUP_SYNC_SEMAPHORE_ERROR. Support component for this case is
BC-JAS-SF.
-14
JSTARTUP_INVALID_PROPERTY_FILE. Support component for this case is
BC-JAS-SF.
-15
JSTARTUP_INVALID_VMTYPE. Support component for this case is BC-JAS-SF.
-16
JSTARTUP_NO_PERMISSION. Support component for this case is BC-JAS-SF.
-17
JSTARTUP_INVALID_JDK. Support component for this case is BC-JAS-ADM.
-18
JSTARTUP_NODE_NOT_FOUND. Support component for this case is BC-JAS-SF.
-100
JSTARTUP_NO_SYSTEMNAME. Support component for this case is BC-INS.
-101
JSTARTUP_PARAM_NOT_EXISTS. Support component for this case is BC-JAS-SF.
-102
JSTARTUP_INVALID_LOCAL_PROFILE. Support component for this case is
BC-INS.
-103
JSTARTUP_CREATE_LOCAL_PROFILE. Support component for this case is
BC-JAS-SF.
-104
JSTARTUP_NO_MORE_PROCESSES. Support component for this case is
BC-JAS-SF.
-105
JSTARTUP_INVALID_PROCESS. Support component for this case is BC-JAS-SF.
-106
JSTARTUP_PROGRAM_ALREADY_RUNS. Support component for this case is
BC-JAS-SF.
-107
JSTARTUP_SHM_NOT_INITIALIZED. Support component for this case is
BC-JAS-SF.
-108
JSTARTUP_DEBUG_SESSION_ALREADY_ACTIVATED. Support component for this
case is BC-JAS-SF.
-109
JSTARTUP_DEBUG_SESSION_NOT_ACTIVATED. Support component for this case is
BC-JAS-SF.
-333
server/dispatcher process is restarted because it has missed a cluster
broadcast message due to network problems. Support
component for this case is BC-CST-MS.
-334
server/dispatcher process is restarted because of error
getting confirmation during
reattach to the message server.
Support component for this case is
BC-CST-MS.
-335
server/dispatcher process is restarted because of timeout
for reconnecting to message server
has reached. Support
component for this case is
BC-CST-MS.
-336
server/dispatcher process is restarted because no notification
is received from message server.
Support component for this
case is BC-CST-MS.
-337
server/dispatcher process is restarted because exits
listener loop. Support component
for this case is BC-CST-MS.
-338
server/dispatcher process is restarted because of invalid
message. Support component for
this case is BC-CST-MS.
-339
client is not authorized to access the message server. Support
component for this case is
BC-CST-MS.
-1000 JSTARTUP_PROCESS_IS_STOPPED. Support
component for this case is
BC-JAS-SF.
-1001 JSTARTUP_PROCESS_WAITERROR. Support
component for this case is
BC-JAS-SF.
-1501 server/dispatcher process is not
able to start because the
initialization of some manager
ends up with error. Support
component for this case is
BC-JAS-COR.
-11111server/dispatcher process is stopped
due to license expiration.
Support component for this case is
XX-SER-LIKEY.
-11112server/dispatcher explicit shutdown
is invoked from shell
command or Visual Administration
tool. No restart will be
performed. Not a problem. Support
component regarding this
behavior - BC-JAS-COR.
-11113Essential service fails to start so
the server/dispatcher
process should exit. Support
component for this case is
BC-JAS-COR.
-11114Services load timeout has been
reached. In case the value of
"haltOnServiceTimeout"
property of ServiceManager is
true server/dispatcher process
would exit. Support component for this case is BC-JAS-COR.
No comments:
Post a Comment