Announcement

Collapse
No announcement yet.

Intermittently can't launch Administrator with 'Error Downloading/Verifying Codebase'

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

  • Intermittently can't launch Administrator with 'Error Downloading/Verifying Codebase'

    We've been encountering a frustratingly sneaky problem recently when attempting to connect to our instances of Mirth Connect 3.6.1. Sometimes it works fine, but seemingly at random for extended periods of time, any attempt to connect the launcher (either via the NextGen Connect Administrator Launcher or via the Mirth Connect Administrator web page) fails.

    When attempted via the web page, it just times out; when attempting via the Administrator Launcher (using the built-in JVM), we get the following error:

    Code:
    Error Downloading/Verifying Codebase
    The markup in the document preceding the root element must be well-formed.
    org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 3; The markup in the document preceding the root element must be well-formed.
    	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown Source)
    	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unknown Source)
    	at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
    	at com.mirth.connect.client.launcher.f.a(SourceFile:664)
    	at com.mirth.connect.client.launcher.f.a(SourceFile:167)
    	at com.mirth.connect.client.launcher.MirthClientLauncher.run(SourceFile:1122)
    	at java.lang.Thread.run(Unknown Source)
    During this time, we can still get to the Administrator Launcher web page in a browser (//<host>:<http.port>/), but attempting to actually click the "Launch Mirth Connect Administrator" button just times out.

    There are no errors logged in mirth.log, and we know the port is open because we can still telnet to the host using the port configured as http.port in mirth.properties. Running ps -ef | grep mcservice still shows that mcservice is running. There are other applications running on the same server, and there is ample available RAM and CPU%.

    Even more oddly, the problem seems to self-resolve after an extended period of time. Coming back and attempting again some hours later, it's as if there was never a problem (nothing logged, everything responding as expected).

    We're running:
    CentOS Linux release 7.6.1810 (Core)
    Oracle jdk1.8.0_191-amd64
    Mirth Connect 3.6.1
    NextGen Connect Administrator Launcher using Default Java Home (1.8.0_191-b12)

    Any thoughts or further troubleshooting suggestions? At the moment, if we urgently need to access the Administrator console during one of these recalcitrant periods, our only option is to kill the mcservice process and restart the service again (usually in this phase, running mcservice stop doesn't actually the process, despite feedback saying that the daemon has been stopped).

    Thanks!

  • #2
    Hate to bump the thread, but we're still running into this periodically in our production environment, and it's quite a problem when it does (as we often have to do emergency maintenance to recover from it in a timely fashion).

    Anybody even have any troubleshooting steps we can try, beyond what we've already looked at above? Not sure if this is an issue with Java GC causing the unresponsiveness, or a bug with the Mirth app itself, or if it's something resource-related on the server overall, but something keeps causing the app to go into seclusion and not let us in. Not a comfortable place to be in.

    Thanks.

    Comment


    • #3
      I just upgraded Mirth Connect from 3.5 to 3.7 and I am continuously getting the same error when trying to launch a connection from Administrator Launcher. Before the upgrade it was working just fine.

      Does anyone have a solution for this?

      Error reading Java home directory: ../../jre
      java.lang.Exception: Error reading Java home directory: ../../jre
      at com.mirth.connect.client.launcher.L.a(SourceFile:1 61)
      at com.mirth.connect.client.launcher.MirthClientLaunc her.run(SourceFile:2538)
      at java.lang.Thread.run(Unknown Source)

      Thanks

      Comment


      • #4
        Does anyone have know how to resolve this issue..? Running into the same problem with Mirth 3.6.1. We recently moved to an all docker environment, problems started after migration

        Comment


        • #5
          Same issue Error Downloading/Verifying Codebase

          The markup in the document preceding the root element must be well-formed.
          org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 3; The markup in the document preceding the root element must be well-formed.
          at com.sun.org.apache.xerces.internal.parsers.DOMPars er.parse(Unknown Source)
          at com.sun.org.apache.xerces.internal.jaxp.DocumentBu ilderImpl.parse(Unknown Source)
          at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
          at com.mirth.connect.client.launcher.f.a(SourceFile:6 73)
          at com.mirth.connect.client.launcher.f.a(SourceFile:1 67)
          at com.mirth.connect.client.launcher.MirthClientLaunc her.run(SourceFile:1164)
          at java.lang.Thread.run(Unknown Source)

          Tried a fresh install and a new database, and I have verified that the Mirth tables were created on startup. I can load the http://localhost: 8080 page, and the Mirth Administrator via JNLP will start but I cannot login with error: There was an error connecting to the server at the specified address. Please verify that the server is up and running. I assume it must have connected since it created the tables. I was hoping the launcher would work.

          Running Mirth 3.1.1 (also tried 3.7.1), Java 1.8.0_191, on Windows 10 Pro 64bit, MSSQL Server 2016, using integrated security AD login

          Comment


          • #6
            Does the same happen if you manually download the JNLP file, save it somewhere, and then open that file with the launcher? Also what URL are you currently using in the launcher?
            Last edited by narupley; 06-26-2019, 06:43 AM.
            Step 1: JAVA CACHE...DID YOU CLEAR ...wait, ding dong the witch is dead?

            Nicholas Rupley
            Work: 949-237-6069
            Always include what Mirth Connect version you're working with. Also include (if applicable) the code you're using and full stacktraces for errors (use CODE tags). Posting your entire channel is helpful as well; make sure to scrub any PHI/passwords first.


            - How do I foo?
            - You just bar.

            Comment


            • #7
              Originally posted by narupley View Post
              Does the same happen if you manually download the JNLP file, save it somewhere, and then open that file with the launcher? Also what URL are you currently using in the launcher?
              The URL used in the launcher is
              Code:
              http://<server-ip>:<http.port>
              (where http.port is the http.port configured in mirth.properties, and <server-ip> is the IP address that Connect is installed at)

              We get the same experience if we go to the Mirth Connect Administrator web page and click the "Launch Mirth Connect Administrator" button (it just spins trying to download anything).

              For us, the only way we've been able to clear the issue is fully restarting mcservice on the server, and then we'll usually be okay for a couple of days again. There are never any errors or warnings logged (even with logging turned up to TRACE levels. Ironically, after we cranked up the log4j.appender.fout.MaxFileSize setting to 10M and switched the log levels to TRACE on our test server, we saw the issue happening less-frequently; may be anecdotal, but it was funny.

              Comment


              • #8
                When I manually try to download the JNPL is keep loading.. nothing happens

                Comment


                • #9
                  Please help...I was a happy mirth user until I downloaded the new the Mirth Connect Administrator Launcher...now all I get is this error and cannot access any mirth.
                  Tried reinstall and reboot no luck
                  completely blocked...extremely frustrating

                  Error Downloading / Verifying Codebase
                  Error reading Java home directory: ../../../../Plugins/jre.bundle/Contents/Home/jre
                  java.lang.Exception: Error reading Java home directory: ../../../../Plugins/jre.bundle/Contents/Home/jre
                  at com.mirth.connect.client.launcher.L.a(SourceFile:1 61)
                  at com.mirth.connect.client.launcher.MirthClientLaunc her.run(SourceFile:2573)
                  at java.lang.Thread.run(Thread.java:748)

                  Comment


                  • #10
                    Still experiencing this problem.. did anyone figure it out? Very frustrating

                    Comment


                    • #11
                      Check Heap Size

                      We were getting the same error and it was caused by two different issues. I'm not sure if this helps, but you could give it a shot. We are using Mirth Connect Server 3.8.0 on a Linux server.

                      The first issue was a "stuck" Mirth launcher process. We had to manually kill that process.

                      The second issue was a heap size issue, which we found by looking at the log files in /opt/mirthconnect/logs. One of the logs had a "java.lang.outofmemoryerror: Java heap space" error in it.

                      There are 2 files that tell Java how much RAM it can use, and that number was defaulted to 256m. We changed the number to 1024 and that seemed to fix it. The files are: /opt/mirthconnect/mcservice.vmoptions and mcserver.vmoptions. We changed the second line from Xmx256m to Xmx1024m

                      Not sure it is even the same problem, but that fixed our issues.

                      Comment

                      Working...
                      X