When increased AdminServer logging is needed:
Extended logging is enabled by adding the required logging -Dargs to the 'jvmargs=' line under the AdminServer section of the DLC/properties/AdminServerPlugins.properties file
- As long as the AdminServer has not been started up in interactive mode (-interactive true), STDOUT and STDERR are written to the admserv.log.
- This logging level accepts values from 1 to 5, being 3 the default.
- Each logging level will contain entries from the previous logging levels. Logging level 5 will contain all messages from 0 to 5.
Where:
0: Severe Error
1: Error
2: Warning
3: Information
4: Security
5: Verbose
For OpenEdge 10.1B to 11.6:
- Under the section: [PluginPolicy.Progress.AdminServer]
- jvmargs=-Xmx512m -DLogLevel=5 (... remainder of existing parameters)
For OpenEdge 11.7:
- Under the sections : [PluginPolicy.Progress.AdminServer] & [PluginPolicy.Progress.ProAdsv]
- When the AdminServer is started as a Service, jvmstart makes use of the "PluginPolicy.Progress.AdminServer" section, otherwise PROADSV uses the "PluginPolicy.Progress.ProAdsv" section. It is advisable to update both sections.
There is a defect that prevents jvmargs=-DLogLevel specifically from working on in later 11.7 versions. Cannot increase adminserver logging level from AdminServerPlugins.properties file
This does not affect -Djava.rmi.server.logCalls or -Djvmstart.debug outlined below, which are added to jvmargs.
Either start the AdminServer with the logging level required:
a. proadsv -start -loglevel 5
{AND OR} Use the online method instead:
b. http://localhost:9090/diagnostics/logconsole.jsp
Where for example: Logging Subsystem levels
(enable ) AdminServer & Security == Verbose
(enable ) OpenEdge == Extended
OE 12.x:
The parameter is now lowercase -Dloglevel
When diagnosing issues with AdminServer startup:
Debugging information for all processes the AdminServer starts using the jvmStart executable will be created in a jvmStart.log file.
Where debugging information is enabled by adding "-Djvmstart.debug=1" to the 'jvmargs=' line as above. This parameter only accepts values: 0 or 1, jvmStart debugging can either be turned on or off.
Example:
jvmargs=-Xmx512m -DLogLevel=5 -Djvmstart.debug=1 (... remainder of existing parameters)
When diagnosing issues with a client having issues communicating with the AdminServer:
Increased RMI communications tracing information can be turned on by adding "-Djava.rmi.server.logCalls=true" to the 'jvmargs=' line as above. This parameter only accepts values; true or false, RMI tracing can either be turned on or off.
Example:
jvmargs=-Xmx512m -DLogLevel=5 -Djava.rmi.server.logCalls=true (... remainder of existing parameters)
The AdminServer will need to be restarted after saving the above changes to the AdminServerPlugins.properties file.
To disable extended logging, the AdminServer will have to be stopped and restarted after reverting the above changes.
Since OpenEdge 11.5 verbose logging for specific areas can be enabled and disabled online without having to restart the AdminServer. For further information refer to Article:
In Progress 9 logging levels can be increased by modifying the proadsv.bat or Windows Registry as outlined in Article:
Enabling interactive mode for troubleshooting:
Some issues prevent the AdminServer from generating a log, the interactive parameter allows the redirection of STDOUT and STDERR to the console.
Prior to 12.x
proadsv -start -interactive true -loglevel 5
12.x+
proadsv -start -interactive true -loglevel 5 -consolelog true
