Kbase 20004: How to enable / increase debug messages within the AdminServer?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
7/14/2009 |
|
Status: Verified
GOAL:
How to enable / increase debug messages within the AdminServer?
GOAL:
How to get additional Debugging Messages for the AdminServer?
GOAL:
How to increase Adminserver logging level ?
FACT(s) (Environment):
Progress 9.1C
Progress 9.1D
Progress 9.1E
OpenEdge 10.x
Windows NT 32 Intel/Windows 2000
UNIX
FIX:
Here are some parameters that can help debug AdminServer issues.
A) -DLogLevel
B) -Djvmstart.debug
C) -Djava.rmi.server.logCalls
A) -DLogLevel
-DLogLevel=<value> will increase the logging level to the AdminServer. This value has a range between <1-5>. The default value is 3. Setting the value to 4 or 5 would give you increased logging.
To implement this parameter:
On WINDOWS, you can add this parameter via two methods;
Method 1: Through the Registry
Method 2: Through the 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. Go to %DLC%\bin
2. Edit proadsv.bat file
3. Go to the bottom of the file where it states:
:START
type "%DLC%\version"
"%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%
4. Add -DLogLevel=value anywhere before parameter -Djava.jvmargs="%ARGS%"
Example
"%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, you can add this parameter through the proadsv script (just as proadsv.bat file).
1. Go to $DLC/bin
2. Edit proadsv script
3. Go to the bottom of the file where it states
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 $@
5. Add -DLogLevel=value anywhere before parameter -Djava.jvmargs="$JVMARGS"
Example
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 $@
The difference between each logging level for -DLogLevel is as follows:
0: Severe Error
1: Error
2: Warning
3: Information
Levels 4 and 5 generally are reserved for printing debugging information that will probably only be meaningful to Progress Development.
For example logging level 3 will contain all messages from 0 to 3.
B) -Djvmstart.debug.
-Djvmstart.debug=<value> gives you a debug log file jvmStart.log for all the processes the AdminServer starts using the jvmStart executable. Please note that this parameter does not give additional information about the AdminServer. This parameter only accepts values; 0 or 1, thus the parameter can either be turned off or on.
Example,
-Djvmstart.debug=1
-Djvmstart.debug=0
Follow the same instructions above when implementing this parameter on Unix and/or Windows.
C) -Djava.rmi.server.logCalls
-Djava.rmi.server.logCalls-<value> allow you to increase 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 off or on.
Example,
-Djava.rmi.server.logCalls=true
-Djava.rmi.server.logCalls=false
Follow the same instructions above when implementing this parameter on Unix and/or Windows.