Mirth Connect 4.3.0 Released!

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

This is a major release containing new features like adding new functionality to the Mirth Connect Setup Wizard, adding the ability for resource and channel-specific classloaders to load child-first or parent-first, and added a default implementation of the getObjectsForSwaggerExamples() method in the ServicePlugin class. This release also contains enhancements for the Mirth Connect Administrator Launcher, the Mirth Connect Docker images, and several bug fixes and security improvements.

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

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

Failure to see log files in Mirth Administrator

  • Filter
  • Time
  • Show
Clear All
new posts

  • Failure to see log files in Mirth Administrator

    I am currently unable to see any system events inside of the Mirth Administrator. I originally thought this corresponded to an error in logging, however events are being logged in ./logs/mirth.log and ./logs/wrapper.log. Where in my configuration could this error be occuring? I am currently running Mirth using a Linux init script under CentOS 4.

  • #2
    Re: Failure to see log files in Mirth Administrator

    I'll double check later today, but the logs inside Mirth are only for high-level logging, telling an admin what happened to a message or the general status of a message. The mirth.log and wrapper.log and for lower level errors, such as exceptions and faults thrown by the application. So you only see system events in those logs and only high-level events inside Mirth.

    I could be wrong though, I'll check my installation later today and see what it does.