Announcement

Collapse

Mirth Connect 4.2.0 Released!

Mirth Connect 4.2.0 is now available as an appliance update and on our GitHub page.

This is a major release containing new features like streamlining the process of selecting a listener port, adding the usernames to the overwriting channel changes warning message, adding additional, sortable columns to the Events screen, and being able to select multiple messages when sending messages through a channel. We also added new message integrity features like adding new JavaScript utility methods for hashing channel messages and automatically hashing outgoing messages. This release also contains enhancements for the Mirth Connect Administrator Launcher and several bug fixes, security improvements, and updates to the commercial extensions. See the release notes for the list of fixes and updates.

Download | See What's New | Upgrade Guide | Release Notes

For discussion on this release, see this thread.
See more
See less

Log4j.properties to Log4j.xml

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Log4j.properties to Log4j.xml

    Is there a way to use the XML version of Log4j configuration file instead of the key/value .properties version?

    I believe that a using the -D switch to set the 'log4j.configuration' system property on the java command line can override the default file it looks for. Can't quite figure out how I could do this in Mirth because of the exe's used to start it.

    Removing the .properties file causes Server Manager to show a message box that it cant find the file.

    Searched the forums and could not find anyone else trying this.

    TIA,
    Ross

  • #2
    Re:Log4j.properties to Log4j.xml

    http://wrapper.tanukisoftware.org/do...roduction.html
    Chris Lang

    Comment


    • #3
      Re:Log4j.properties to Log4j.xml

      Thanks for the help.

      Here is some additional info. If there is a log4j.xml file in the conf directory Mirth will attempt to use it, however the Log4j system throws parsing errors unless the following line is defined in
      Code:
      wrapper.conf
      Code:
      wrapper.java.additional.1=-Dlog4j.configuration=./conf/log4j.xml
      Cheers,
      Ross

      Comment

      Working...
      X