Announcement

Collapse

Mirth Connect 3.12.0 Released!

Mirth Connect 3.12.0 is now available as an appliance update and on our GitHub page. This release includes database performance improvements, improves visual HL7 representation, message pruning, keystore handling, PDF generation, community contributions, and fixes several security vulnerabilities. This release also contains many improvements to 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

Channel not deploying properly

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    Channel not deploying properly

    Hi,

    I made some changes to some of my scripts in a channel and copied a custom library into the lib folder and from then on my channel seems to not deploy properly. There is no error message from the admin client but the following is the error stack trace from the wrapper.log.

    INFO | jvm 1 | 2008/01/17 15:57:19 | ERROR 2008-01-17 15:57:19,843 [SslListener0-0] com.webreach.mirth.model.converters.ER7Reader: Unable to parse, message is null or too short:
    INFO | jvm 1 | 2008/01/17 15:57:19 | org.xml.sax.SAXException: Unable to parse, message is null or too short:
    INFO | jvm 1 | 2008/01/17 15:57:19 | at com.webreach.mirth.model.converters.ER7Reader.pars e(ER7Reader.java:68)
    INFO | jvm 1 | 2008/01/17 15:57:19 | at com.webreach.mirth.model.converters.ER7Serializer. toXML(ER7Serializer.java:117)
    INFO | jvm 1 | 2008/01/17 15:57:19 | at com.webreach.mirth.model.converters.ER7Serializer. toXML(ER7Serializer.java:50)
    INFO | jvm 1 | 2008/01/17 15:57:19 | at com.webreach.mirth.server.builders.MuleConfigurati onBuilder.addTransformer(MuleConfigurationBuilder. java:404)
    INFO | jvm 1 | 2008/01/17 15:57:19 | at com.webreach.mirth.server.builders.MuleConfigurati onBuilder.getInboundRouter(MuleConfigurationBuilde r.java:247)
    INFO | jvm 1 | 2008/01/17 15:57:19 | at com.webreach.mirth.server.builders.MuleConfigurati onBuilder.getDescriptor(MuleConfigurationBuilder.j ava:166)
    INFO | jvm 1 | 2008/01/17 15:57:19 | at com.webreach.mirth.server.builders.MuleConfigurati onBuilder.getConfigurationDocument(MuleConfigurati onBuilder.java:133)
    INFO | jvm 1 | 2008/01/17 15:57:19 | at com.webreach.mirth.server.builders.MuleConfigurati onBuilder.getConfiguration(MuleConfigurationBuilde r.java:82)
    INFO | jvm 1 | 2008/01/17 15:57:19 | at com.webreach.mirth.server.controllers.Configuratio nController.deployChannels(ConfigurationController .java:279)
    INFO | jvm 1 | 2008/01/17 15:57:19 | at com.webreach.mirth.server.servlets.ConfigurationSe rvlet.doPost(ConfigurationServlet.java:70)
    INFO | jvm 1 | 2008/01/17 15:57:19 | at javax.servlet.http.HttpServlet.service(HttpServlet .java:616)
    INFO | jvm 1 | 2008/01/17 15:57:19 | at javax.servlet.http.HttpServlet.service(HttpServlet .java:689)
    INFO | jvm 1 | 2008/01/17 15:57:19 | at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:428)
    INFO | jvm 1 | 2008/01/17 15:57:19 | at org.mortbay.jetty.servlet.ServletHandler.dispatch( ServletHandler.java:666)
    INFO | jvm 1 | 2008/01/17 15:57:19 | at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:568)
    INFO | jvm 1 | 2008/01/17 15:57:19 | at org.mortbay.http.HttpContext.handle(HttpContext.ja va:1530)
    INFO | jvm 1 | 2008/01/17 15:57:19 | at org.mortbay.http.HttpContext.handle(HttpContext.ja va:1482)
    INFO | jvm 1 | 2008/01/17 15:57:19 | at org.mortbay.http.HttpServer.service(HttpServer.jav a:909)
    INFO | jvm 1 | 2008/01/17 15:57:19 | at org.mortbay.http.HttpConnection.service(HttpConnec tion.java:816)
    INFO | jvm 1 | 2008/01/17 15:57:20 | at org.mortbay.http.HttpConnection.handleNext(HttpCon nection.java:982)
    INFO | jvm 1 | 2008/01/17 15:57:20 | at org.mortbay.http.HttpConnection.handle(HttpConnect ion.java:833)
    INFO | jvm 1 | 2008/01/17 15:57:20 | at org.mortbay.http.SocketListener.handleConnection(S ocketListener.java:244)
    INFO | jvm 1 | 2008/01/17 15:57:20 | at org.mortbay.util.ThreadedServer.handle(ThreadedSer ver.java:357)
    INFO | jvm 1 | 2008/01/17 15:57:20 | at org.mortbay.util.ThreadPool$PoolThread.run(ThreadP ool.java:534)

    Any idea what is going on? I'm pretty sure all my scripts are valid, I've checked numerous times.

    Any help will be appreciated.

    Thanks.
    Tags: None
  • #2
    Re:Channel not deploying properly

    I reinstalled Mirth and that solved my problem...

    Comment

    • #3
      Hi,
      I am facing the same problem..
      I am not able to deploy channel properly.
      I am getting the following error.
      "ERROR (com.webreach.mirth.model.converters.ER7Reader:75) : Unable to parse, message is null or too short:".
      Not sure how to proceed.
      Any help appreciated.
      Thanks in advance.

      Comment

      • #4
        what type of reader are you using? that message usually pops up when sending Mirth a blank message.

        Comment

        Previous template Next
        Working...
        X

        We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.

        By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.

        I Agree