Kbase P108877: How to configure the AdminServer to allow child processes to generate core files?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
19/10/2009 |
|
Status: Verified
GOAL:
How to configure the AdminServer to allow child processes to generate core files?
GOAL:
How to configure the AdminServer to allow database servers to generate core files when errors occur?
GOAL:
How to configure the AdminServer to allow AppServers to generate core files when errors occur?
FACT(s) (Environment):
Progress 9.x
OpenEdge 10.x
All Supported Operating Systems
FIX:
The JVM process is configured to trap SIGQUIT signals by default.
This prevents the normal core generation of database server processes started with the AdminServer.
In Version 9.x the -Xrs parameter may be added to the jvmargs within the environment or the value within the jvmargs in the file java_env.
In version 10.X within the $DLC/properties/AdminServerPlugins.properties the jvmargs value can be set within the AdminServer group.
Example:
[PluginPolicy.Progress.AdminServer]
jvmargs=-Xrs
One exception exists on Solaris, where not only must the -Xrs be added to the AdminServerPlugins.properties but it must also be added to the proadsv script.
Example:
exec $JVMSTRT -w $WRKDIR -o stderr -m silent -a $ADMSRVRPROP::$ADMSRVRGRP
$JREHOME/bin/$JVMEXE -Xrs -DInstall.Dir=$DLC
-DWork.Dir=$WRKDIR-Djvmstart.debug=$JVMSTRT_DBGOPT -Djava.command=$JVMEXE
-Dadmsrv.jvm=$JREHOME/bin/$JVMEXE $ADMSRVRCLASS $@
To pick up this new setting the AdminServer will need to be restarted.