This documentation supports the 9.0 version of Remedy Action Request System.

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

Debugging options for the BMC Remedy Email Engine

The emaildaemon.properties file that is used by the BMC Remedy Email Engine to read the debugging parameters is found in the AREmail directory. For specific issues, see Troubleshooting BMC Remedy Email Engine and its subtopics.

Important

Ensure that you do not edit the emaildaemon.properties file to change the configuration settings for BMC Remedy Email Engine.

To change the configuration settings for BMC Remedy Email Engine use the AR System Configuration Generic UI form. For more information, see  Updating configuration settings by using the AR System Configuration Generic UI form. 

The following options are available: 

Debugging options for the BMC Remedy Email Engine

Setting Definition
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 and BMC Remedy Email Engine logs

com.bmc.arsys.emaildaemon.logfileName

Enables users to specify the log file path.

Note:

Once the user specifies a file path, email engine logs that user defined file only when it connects to AR server. if any error occurred before connecting to  Centralized configuration form then logs will be stored into default log file path.

Default value – $INSTALL_PATH$/AREmail/Logs/email.log

com.bmc.arsys.emaildaemon.logfilesize

Specifies the maximum size of the log file in bytes. If the file size exceeds this limit, a new file is created.

Default value – Unlimited

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 emaildaemon.properties file for a particular module, then the system defaults to the application level (that is, INFO).

 

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.

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

Related topic

Settings in the EmailDaemon.properties file

 

Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Andreas Mitterdorfer

     

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

    is not working as documented, see below. When setting ConfigurationModule as debuggingOption, the output is the same.

    [remedy@vie-vm-102 AREmail]$ ./emaild.sh status
    checking BMC Remedy Email Engine ...
    BMC Remedy Email Engine is running on port 1100
    [remedy@vie-vm-102 AREmail]$ pwd
    /opt/bmc/ARSystem/AREmail
    [remedy@vie-vm-102 AREmail]$ echo $LD_LIBRARY_PATH
    .::.:.:/opt/bmc/ARSystem/bin:/opt/bmc/AtriumCore/cmdb/server/bin:
    [remedy@vie-vm-102 AREmail]$ /opt/bmc/jdk/bin/java -jar EmailAdminAgent.jar setLog com.bmc.arsys.emaildaemon.ConfigurationModule INFO
    Exception in thread "main" java.lang.NoClassDefFoundError: com/bmc/arsys/emaildaemon/EmailUtil
            at com.bmc.arsys.emaildaemon.AdminAgent.main(AdminAgent.java:112)
    Caused by: java.lang.ClassNotFoundException: com.bmc.arsys.emaildaemon.EmailUtil
            at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
            at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
            at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
            at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
            ... 1 more
    [remedy@vie-vm-102 AREmail]$ cat EmailDaemon.properties
    #Email Daemon
    #Tue Apr 05 10:00:31 CEST 2016
    com.bmc.arsys.emaildaemon.Monitor=30
    com.bmc.arsys.emaildaemon.SortMessages=false
    com.bmc.arsys.emaildaemon.ARDATEONLY=
    com.bmc.arsys.emaildaemon.vie-vm-102.notbmc.com.Password=D3pkjpsl6FCUyizn67RBNRlbao6gwioEtYKjP7Oy5x1cDons5R0bs9F4IDAcuO97ylhfLmlxyLenfYNAaYVuS9uHjFZwvM5WhPdyaiyiBKJBbAEVKNzBUw\=\=
    com.bmc.arsys.emaildaemon.CreatorModule.level=FINER
    com.bmc.arsys.emaildaemon.Exchange-Wait-Time=1
    com.bmc.arsys.emaildaemon.SenderModule.level=FINER
    com.bmc.arsys.emaildaemon.ReceiverModule.level=FINER
    com.bmc.arsys.emaildaemon.CommaValidAddressSeparator=true
    com.bmc.arsys.emaildaemon.templateCacheSize=20
    com.bmc.arsys.emaildaemon.IncomingConnectionRecycleSize=100
    com.bmc.arsys.emaildaemon.UseNameIfNoEmailAddress=true
    com.bmc.arsys.emaildaemon.MonitorModule.level=FINER
    com.bmc.arsys.emaildaemon.ExecutionModule.level=FINER
    com.bmc.arsys.emaildaemon.companionservername=vie-vm-102.notbmc.com
    com.bmc.arsys.emaildaemon.SendEmailSetSize=100
    com.bmc.arsys.emaildaemon.Mailboxes=
    com.bmc.arsys.emaildaemon.FetchUserGroupInfoOnDemand=false
    com.bmc.arsys.emaildaemon.MBOXFromLineWith-At-The-Rate-Sign=false
    com.bmc.arsys.emaildaemon.ARSystemHandler.level=OFF
    com.bmc.arsys.emaildaemon.StoreInstructions=false
    com.bmc.arsys.emaildaemon.vie-vm-102.notbmc.com.Interval=30
    com.bmc.arsys.emaildaemon.AdditionalMailHeaders=X-Loop-Detect
    com.bmc.arsys.emaildaemon.vie-vm-102.notbmc.com.TCP=2000
    com.bmc.arsys.emaildaemon.level=FINER
    com.bmc.arsys.emaildaemon.securityCacheSize=20
    com.bmc.arsys.emaildaemon.SaveSentItem=True
    com.bmc.arsys.emaildaemon.IncomingMessagesQueueSize=100
    com.bmc.arsys.emaildaemon.ConfigurationModule.level=FINER
    com.bmc.arsys.emaildaemon.vie-vm-102.notbmc.com.RPC=0
    com.bmc.arsys.emaildaemon.URLWithHrefTag=true
    com.bmc.arsys.emaildaemon.ARTIMEONLY=
    com.bmc.arsys.emaildaemon.ContentTypeWithCharset=True
    com.bmc.arsys.emaildaemon.ChunkSize=100
    com.bmc.arsys.emaildaemon.UserChunkSize=5000
    com.bmc.arsys.emaildaemon.instructionCacheSize=20
    com.bmc.arsys.emaildaemon.ARDATE=
    com.bmc.arsys.emaildaemon.vie-vm-102.notbmc.com.Language=en_US
    com.bmc.arsys.emaildaemon.RMIPort=1100
    com.bmc.arsys.emaildaemon.servers=vie-vm-102.notbmc.com
    com.bmc.arsys.emaildaemon.MailboxPollingUnitIsMinutes=true
    com.bmc.arsys.emaildaemon.vie-vm-102.notbmc.com.Authentication=
    java.util.logging.ConsoleHandler.level=INFO
    [remedy@vie-vm-102 AREmail]$

     

    Apr 05, 2016 05:09
    1. Prachi Kalyani

      Hello Andreas,

      Thank you for the detailed information. I will verify this and get back to you.

      Thanks,

      Prachi

      Apr 05, 2016 05:19
    1. Prachi Kalyani

      Hello Andreas,

      The technical team would need some more inputs to resolve this issue. Please contact BMC Customer Support to log a formal ticket on this issue. To contact customer support click here.

      In the meanwhile you can use the following workaround to address this issue:

      - From the AR install Directory location, run the following command and update only the build and release version:

      java  -cp emaildaemon.jar;EmailAdminAgent.jar;arapi90_build002.jar com.bmc.arsys.emaildaemon.AdminAgent setLog com.bmc.arsys.emaildaemon.ConfigurationModule 
      INFO
      java  -cp emaildaemon.jar;EmailAdminAgent.jar;arapi90_build002.jar com.bmc.arsys.emaildaemon.AdminAgent setLog com.bmc.arsys.emaildaemon OFF

      Thanks,

      Prachi

      Apr 18, 2016 01:38
  2. Andreas Mitterdorfer

    Thanks Prachi!

    [remedy@vie-vm-102 AREmail]$ /opt/bmc/jdk/bin/java -cp ./emaildaemon.jar:./EmailAdminAgent.jar:./arapi90_build002.jar com.bmc.arsys.emaildaemon.AdminAgent setLog com.bmc.arsys.emaildaemon.ConfigurationModule WARN

    <EML> /* Mon Apr 18 2016 13:49:39.856 */ Success

     

    [remedy@vie-vm-102 AREmail]$ /opt/bmc/jdk/bin/java -cp ./EmailAdminAgent.jar:./emaildaemon.jar com.bmc.arsys.emaildaemon.AdminAgent setLog com.bmc.arsys.emaildaemon.ConfigurationModule INFO

    <EML> /* Mon Apr 18 2016 13:58:44.937 */ Success

     

    IMHO the emaildaemon.jar  is missing in documentation.

     

     

     

     

    Apr 18, 2016 06:55