Mirth Connect 4.1.1 Released!

Mirth Connect 4.1.1 is now available as an appliance update and on our GitHub page. This release contains modifications to the Welcome to Mirth Connect screen and two fixed defects. 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

Error in mule-config.xml

  • Filter
  • Time
  • Show
Clear All
new posts

  • Error in mule-config.xml

    It looks like there is an invalid character in a file written and read by Mirth. This probably occurred on deploying all channels or on saving a channel. Would it be possible to check for invalid character prior to writing mule-config.xml?

    org.mule.config.ConfigurationException: Failed to parse configuration resource "/usr/local/mirth/conf/mule-config.xml" (org.mule.config.ConfigurationException)
    at er.configure(
    at com.webreach.mirth.server.Mirth.startMule(Mirth.ja va:178)
    at com.webreach.mirth.server.Mirth.restartMule(Mirth. java:160)
    at )
    Caused by: org.mule.config.ConfigurationException: Failed to parse configuration resource "/usr/local/mirth/conf/mule-config.xml"
    at tion.process( 1)
    at er.configure(
    at er.configure(
    ... 3 more
    Caused by: org.mule.umo.lifecycle.InitialisationException: Initialisation Failure: illegal character (08348f2c-eae5-4602-886c-0bc32da9f3b3#41)
    at org.apache.commons.digester.Digester.createSAXExce ption(
    at org.apache.commons.digester.Digester.createSAXExce ption(
    at org.apache.commons.digester.Digester.endElement(Di
    at org.apache.xerces.parsers.AbstractSAXParser.endEle ment(Unknown Source)

  • #2
    Re:Error in mule-config.xml

    Try disabling each channel unitl your deploy succeeds. Once you isolate the offending channel, post it here (if you can).
    Chris Lang


    • #3
      Re:Error in mule-config.xml

      I found and fixed my channel, that was easy because I knew what changes I had made. That is not why I posted this thread, and maybe it should be posted under development.

      The problem is Mirth did not give any indication that there was a problem after pushing the deploy button other then not list any of my channels on the dashboard. I had to view the events first to realize there was a deployment problem. I feel Mirth should have given a warning either during the deployment or during the channel save or possibly when switching from the filter page to the main channel page.