This documentation applies to the 8.0 version of Remedy Action Request System, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

Debugging options for the BMC Remedy Email Engine

The logging.properties file that you use for debugging the BMC Remedy Email Engine is usually found in the Java lib directory. For specific issues, see Troubleshooting BMC Remedy Email Engine and its subtopics. The following options are available:

Debugging options for the BMC Remedy Email Engine

Setting Definition
Global Property Handlers
handlers = java.util.logging.ConsoleHandler
Sets the places where logs can go. In this example, it has been set to send logs only to the console.
Global Property Handlers
handlers = java.util.logging.FileHandler, java.util.logging.ConsoleHandler
Enables file logging with console logging. In UNIX, all console output is directed to emailEngineInstallDir/logs/emaild.sh_log, but file logging can also be switched on.
Global Logging Level
java.util.logging.FileHandler.level = FINER

Logging level for the file output. You can set the logging level to Finer in the Java logging.properties file to obtain every log message generated by the system. You can also use the keyword ALL, which means all logs are to be sent to the output.

Note

Use this option with care because the contents of the BMC Remedy AR System Email Error Logs form can become very large.

Handler Specific Properties
java.util.logging.FileHandler.pattern = %h/java%u.log
File to where logs are made. You can reference the Java documentation on this format, as it is specified by Java 1.5.x logging.
Handler Specific Properties
java.util.logging.FileHandler.limit = 50000
Maximum size of the log file in bytes. If the file size exceeds this length, a new file is created.
Handler Specific Properties
java.util.logging.FileHandler.count = 1
Number to start with. This is appended to the end of the file name.
Handler Specific Properties
java.util.logging.FileHandler.formatter = java.util.logging.XMLFormatter
Use an XML formatter to format the output, or you can use java.util.logging.SimpleFormatter with console logging.
Console Handler Specific Properties
java.util.logging.ConsoleHandler.level = INFO
Logging level for the file output.
Console Handler Specific Properties
java.util.logging.ConsoleHandler.formatter = java.util.logging.SimpleFormatter
XML formatter for console logging.
Main Application Level
com.bmc.arsys.emaildaemon.level = INFO

Level for the entire BMC Remedy Email Engine. This setting for the main application level includes the modules unless you specify otherwise. If a level for one of the outputs is lower than this setting, then this level overrides that level for the given output. In this example, because this level is INFO, the level for the file handler will be ignored and also set to INFO. If the main application level is SEVERE, then only module logs with a level of SEVERE are allowed. You can override this behavior by adding one of these module levels, then specifying that level as FINER, FINE, INFO, or WARNING. This level will be used for all logs originating from that particular module and only that module. If you add more than one module level, then logs for more than one module will be allowed, and you can set the levels for the different modules independently.

Default value - SEVERE

For more information, see Setting log files options. For more information about BMC Remedy email engine logs and debugging options, see BMC Remedy Email Engine logs and debugging options

Module Levels
com.bmc.arsys.emaildaemon.moduleName.level

  • ConfigurationModule.level = FINER
  • CreatorModule.level = FINER
  • ExecutionModule.level = FINER
  • ReceiverModule.level = FINER
  • SenderModule.level = FINER
  • MonitorModule.level = FINER

Levels for application modules. You can specify the logging levels for the various modules independently from the entire BMC Remedy Email Engine logging level, for only the modules you are interested in troubleshooting. These application modules allow you to combine main application and module logging. For example, if the main application level is set to INFO and you set the level for the Receiver Module to FINER, then you will see only FINER information in the log for the Receiver module. If there is no entry in the logging.properties file for a particular module, then the system defaults to the application level (that is, INFO).

Note

The level for one of the outputs must be at least FINER, such as the ConsoleHandler, to actually see the log.

Application Levels
com.bmc.arsys.emaildaemon.ARSystemHandler.level = WARNING
Level for the outputs to the BMC Remedy Email Error form. You cannot disable this handler. This level could also be overridden if the application level defined previously is higher.

You can change the logging levels of the email engine debugging options at runtime by using the following command:


java -jar EmailAdminAgent.jar setLog <debuggingOption> <loggingLevel>

Important

Make sure you do not include .level in the debuggingOption when using it in this command.



Also, to change the logging level at run time you must set the following in values in logging.properties for the JRE being used:


com.bmc.arsys.emaildaemon.<debuggingOption>.level = FINEST

java.util.logging.ConsoleHandler.level = INFO
Was this page helpful? Yes No Submitting... Thank you

Comments