Announcement

Collapse
No announcement yet.

Unable to start Mirth 1.3.1

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

  • Unable to start Mirth 1.3.1

    Dear All,

    Operating System : Windows XP Professional
    JAVA version : 1.5.0_09
    While Starting Mirth I am getting following error.Can anyone suggest how to go about?


    Exception in thread "main" java.lang.ExceptionInInitializerError
    at com.webreach.mirth.server.controllers.SystemLogger .<init>(SystemLogge
    r.java:43)
    at com.webreach.mirth.server.Mirth.<init>(Mirth.java: 63)
    at sun.reflect.NativeConstructorAccessorImpl.newInsta nce0(Native Method)

    at sun.reflect.NativeConstructorAccessorImpl.newInsta nce(Unknown Source)

    at sun.reflect.DelegatingConstructorAccessorImpl.newI nstance(Unknown Sou
    rce)
    at java.lang.reflect.Constructor.newInstance(Unknown Source)
    at java.lang.Class.newInstance0(Unknown Source)
    at java.lang.Class.newInstance(Unknown Source)
    at com.webreach.mirth.server.launcher.Launcher.main(L auncher.java:38)
    Caused by: java.lang.RuntimeException: java.lang.RuntimeException: Error occurre
    d. Cause: com.ibatis.common.xml.NodeletException: Error parsing XML. Cause: ja
    va.net.ConnectException: Connection timed out: connect
    at com.webreach.mirth.server.util.SqlConfig.<clinit>( SqlConfig.java:24)
    ... 9 more
    Caused by: java.lang.RuntimeException: Error occurred. Cause: com.ibatis.common
    .xml.NodeletException: Error parsing XML. Cause: java.net.ConnectException: Con
    nection timed out: connect
    at com.ibatis.sqlmap.engine.builder.xml.SqlMapConfigP arser.parse(SqlMapC
    onfigParser.java:84)
    at com.ibatis.sqlmap.client.SqlMapClientBuilder.build SqlMapClient(SqlMap
    ClientBuilder.java:62)
    at com.webreach.mirth.server.util.SqlConfig.<clinit>( SqlConfig.java:22)
    ... 9 more
    Caused by: com.ibatis.common.xml.NodeletException: Error parsing XML. Cause: ja
    va.net.ConnectException: Connection timed out: connect
    at com.ibatis.common.xml.NodeletParser.parse(NodeletP arser.java:52)
    at com.ibatis.sqlmap.engine.builder.xml.SqlMapConfigP arser.parse(SqlMapC
    onfigParser.java:81)
    ... 11 more
    Caused by: java.net.ConnectException: Connection timed out: connect
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(Unknown Source)
    at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
    at java.net.PlainSocketImpl.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at sun.net.NetworkClient.doConnect(Unknown Source)
    at sun.net.www.http.HttpClient.openServer(Unknown Source)
    at sun.net.www.http.HttpClient.openServer(Unknown Source)
    at sun.net.www.http.HttpClient.<init>(Unknown Source)
    at sun.net.www.http.HttpClient.New(Unknown Source)
    at sun.net.www.http.HttpClient.New(Unknown Source)
    at sun.net.www.protocol.http.HttpURLConnection.getNew HttpClient(Unknown
    Source)
    at sun.net.www.protocol.http.HttpURLConnection.plainC onnect(Unknown Sour
    ce)
    at sun.net.www.protocol.http.HttpURLConnection.connec t(Unknown Source)
    at sun.net.www.protocol.http.HttpURLConnection.getInp utStream(Unknown So
    urce)
    at com.sun.org.apache.xerces.internal.impl.XMLEntityM anager.setupCurrent
    Entity(Unknown Source)
    at com.sun.org.apache.xerces.internal.impl.XMLEntityM anager.startEntity(
    Unknown Source)
    at com.sun.org.apache.xerces.internal.impl.XMLEntityM anager.startDTDEnti
    ty(Unknown Source)
    at com.sun.org.apache.xerces.internal.impl.XMLDTDScan nerImpl.setInputSou
    rce(Unknown Source)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumen tScannerImpl$DTDDis
    patcher.dispatch(Unknown Source)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumen tFragmentScannerImp
    l.scanDocument(Unknown Source)
    at com.sun.org.apache.xerces.internal.parsers.XML11Co nfiguration.parse(U
    nknown Source)
    at com.sun.org.apache.xerces.internal.parsers.XML11Co nfiguration.parse(U
    nknown Source)
    at com.sun.org.apache.xerces.internal.parsers.XMLPars er.parse(Unknown So
    urce)
    at com.sun.org.apache.xerces.internal.parsers.DOMPars er.parse(Unknown So
    urce)
    at com.sun.org.apache.xerces.internal.jaxp.DocumentBu ilderImpl.parse(Unk
    nown Source)
    at com.ibatis.common.xml.NodeletParser.createDocument (NodeletParser.java
    :147)
    at com.ibatis.common.xml.NodeletParser.parse(NodeletP arser.java:49)
    ... 12 more

  • #2
    Re: Unable to start Mirth 1.3.1

    Do you get the same error with 1.3.0? We specifically addressed this issue in .1...
    Chris Lang

    Comment


    • #3
      Re: Unable to start Mirth 1.3.1

      Dear Chirisl

      With Mirth 1.2 there is no issues of installation.
      But Mirth 1.3 and Mirth 1.3.1 i am facing the above error while running the Mirth from command prompt.
      I searched the forum and issuetracker but no solutions. Supposed to be fixed in the Mirth 1.3.1

      Mirth 1.3.1
      Java 1.5.0_09 on Windows XP (5.1, x86)

      Comment


      • #4
        Re: Unable to start Mirth 1.3.1

        I have the same problem. I fear MIRTH-204 should be re-opened

        If I start Mirth in a system with internet connection, Mirth starts fine. But, Without the connection, Mirth can&#039;t start.

        ...Which is a big issue for me, because internet connection is only allowed for trusted users in the hospitas I work for.

        Comment


        • #5
          Re: Unable to start Mirth 1.3.1

          I will look into this ASAP. We know what the issue is and applied the official fix from Apache, however it doesn&#039;t seem to work. I&#039;ll keep you guys posted as we make progress. Here is a quick and dirty workaround in the meantime:

          1.) Look in all of the Postgres or Derby xml files and get the DTD locations.
          2.) Manually download the DTDs from Apache
          3.) Place the DTDs in [Mirth Directory]/web/public/ (if the public directory does not exist, create it)
          4.) Change the Derby/Postgres xml files to point to http://localhost:8080/public/[DTD name]

          Mirth runs an internal webserver that should be able to serve up these DTDs directly. Make sure to check the DTDs to see if they reference any other Apache schemas.

          Sorry about the trouble everyone, but we&#039;re making this our top priority.

          -Chris
          Chris Lang

          Comment


          • #6
            Re: Unable to start Mirth 1.3.1

            Thanks, Chris.

            This solves the issue.

            Comment


            • #7
              Re: Unable to start Mirth 1.3.1

              Another workaround is to set your HTTP proxy in the mirth.bat

              java -Dhttp.proxyHost="1.1.1.1" -Dhttp.proxyPort=11 -jar mirth-launcher.jar launcher.xml

              where 1.1.1.1 is the ip address or hostname of your companys proxy server and 11 is the port

              Comment

              Working...
              X