This Article is specific to earlier
Progress 9 versions, for OpenEdge 10 and later these parameters are implemented differently as described in Article:
The following java parameters are used to debug AdminServer issues.
A) -DLogLevel, to increase the AdminServer logging
B) -Djvmstart.debug, to log any jvmstart calls going through this AdminServer.
C) -Djava.rmi.server.logCalls, log all the client communication to the AdminServer
A) -DLogLevel-DLogLevel will increase the logging level to the AdminServer.
This value has a range between {1..5},
The default value is 3, which will contain all messages from 0 to 3.
The difference between each logging level for -DLogLevel is as follows:
0: Severe Error
1: Error
2: Warning
3: Information
4: Security
5: Verbose
Levels 4 and 5 generally are reserved for printing debugging information that Progress Technical Support will need to further analyse in collaboration with Progress Development. They will also lead to much larger AdminServer log files and are typically only used when the problem under investigation can be reproduced or troubleshooting is outside production environments.
To change AdminServer logging:On WINDOWS, add the
-DLogLevel parameter via either of the following methods;
Method 1: Through the Windows Registry
Method 2: Through the %DLC%\bin\proadsv.bat file
Method 1: Through the Registry
1. Run Regedit
2. Edit the Registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\PSC\AdminService\<version>\StartupCmd\Chimera
3. Add -DLogLevel=<value> anywhere before -Djvmstart.debug=0.
Method 2: Through the proadsv.bat file
1. Edit the %DLC%\bin\proadsv.bat file
2. Navigate to the bottom of the file and optionally comment and copy the following line for ease of reversion:
:START
type "%DLC%\version"
REM "%JVMSTRT%" -o stderr -s -m silent -c %JCP% "%JVM%"
-Djava.security.policy="%POLICY%" -Dadmsrv.jvm="%JVM%"
-DInstall.Dir="%DLC%" -DWork.Dir="%WRK%"
-Djava.jvmargs="%ARGS%" %ADMSRVRCLASS% %PARMS%
3. Add -DLogLevel=<value> anywhere before parameter -Djava.jvmargs="%ARGS%"
"%JVMSTRT%" -o stderr -s -m silent -c %JCP% "%JVM%"
-Djava.security.policy="%POLICY%" -Dadmsrv.jvm="%JVM%"
-DInstall.Dir="%DLC%" -DWork.Dir="%WRK%"
-Djvmstart.debug=1 -DLogLevel=5 -Djava.jvmargs="%ARGS%" %ADMSRVRCLASS% %PARMS%
On UNIX, add the
-DLogLevel parameter through the proadsv script
1. Edit the $DLC/bin/proadsv script
2. Navigate to the bottom of the file and optionally comment and copy the following line for ease of reversion:
# exec $JVMSTRT -w $WRKDIR -o stderr -m silent $JREHOME/bin/$JVMEXE -classpath $CLASSPATH $JVMARGS
-Djava.security.policy=$JAVAPOLICY
-DInstall.Dir=$DLC -DWork.Dir=$WRKDIR
-Djvmstart.debug=$JVMSTRT_DBGOPT -Djava.command=$JVMEXE -Dadmsrv.jvm=$JREHOME/bin/$JVMEXE
-Djava.jvmargs="$JVMARGS" $ADMSRVRCLASS $@
3. Add -DLogLevel=<value> anywhere before parameter -Djava.jvmargs="$JVMARGS"
exec $JVMSTRT -w $WRKDIR -o stderr -m silent $JREHOME/bin/$JVMEXE -classpath $CLASSPATH $JVMARGS
-Djava.security.policy=$JAVAPOLICY
-DInstall.Dir=$DLC -DWork.Dir=$WRKDIR
-Djvmstart.debug=$JVMSTRT_DBGOPT -Djava.command=$JVMEXE -Dadmsrv.jvm=$JREHOME/bin/$JVMEXE
-DLogLevel=5 -Djava.jvmargs="$JVMARGS" $ADMSRVRCLASS $@
B) -Djvmstart.debug
-Djvmstart.debug provides a debug log file
jvmStart.log for all processes the AdminServer starts using the
jvmStart executable and only accepts values; 0 or 1, thus can either be turned on or off.
-Djvmstart.debug=1
-Djvmstart.debug=0
Follow the same instructions above when implementing this parameter on Unix and/or Windows.
When jvmStart debugging is enabled:
- jvmStart.log file is written to the current working directory. This may not be the OpenEdge working directory. It is the working directory for the jvmStart tool.
- The output a log file contains for example all the current environment variables, what jvmStart is currently processing and the command line that jvmStart generated and is executing.
- This debug file is appended to each time jvmStart runs and it is not reinitialized.
- It does not provide additional information about the AdminServer, that is obtained by setting -DLogLevel outlined above..
Alternatively use the
JVMSTRT_DBGOPT variable, which is not set by default. When JVMSTRT_DBGOPT = 1, everytime the AdminServer uses jvmStart it will write debug information to the output log file.
C) -Djava.rmi.server.logCalls-Djava.rmi.server.logCalls increases RMI tracing information. This helps when a client is having issues connecting to the AdminServer. This parameter only accepts values; true or false, thus the parameter can either be turned on or off.
-Djava.rmi.server.logCalls=true
-Djava.rmi.server.logCalls=false
Follow the same instructions above when implementing this parameter on Unix and/or Windows.
