Announcement

Collapse
No announcement yet.

Administrator Launcher 1.1.0 Released!

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    My team also proposed one more suggestion:
    Can we have a grouping feature for the connections..
    So that I can group them into things like - Production , Local, Staging, UAT, Dev , QA etc...

    Comment


    • #17
      Love the client but why does it take so long for it to 'verify' the jar files before loading. Some take up to 5 minutes. Doesn't happen when we used Webstart - perhaps I'm doing something wrong?

      Norm

      Comment


      • #18
        Originally posted by NDressler View Post
        Love the client but why does it take so long for it to 'verify' the jar files before loading. Some take up to 5 minutes. Doesn't happen when we used Webstart - perhaps I'm doing something wrong?

        Norm
        I also see some delay, however not as much as 5 minutes, but definitely more than what it used to take with webstart.jnlp

        Comment


        • #19
          Unable to create cache directory

          Getting this error when trying to connect using this URL
          https://localhost:443/mirth/webstart.jnlp

          Unable to create cache directory for version: 3.5.1
          java.io.IOException: Unable to create cache directory for version: 3.5.1
          at com.mirth.connect.client.launcher.f.a(SourceFile:2 71)
          at com.mirth.connect.client.launcher.MirthClientLaunc her.run(SourceFile:1122)

          Do I need to open up a directory's permissions?

          Using macOS Mojave Version 10.14.2 with the "bundled" Java Home option in the Mirth Connect Administrator Launcher Version 1.0.0
          Last edited by khobbs; 12-12-2018, 04:28 PM.

          Comment


          • #20
            Originally posted by khobbs View Post
            Getting this error when trying to connect using this URL
            https://localhost:443/mirth/webstart.jnlp

            Unable to create cache directory for version: 3.5.1
            java.io.IOException: Unable to create cache directory for version: 3.5.1
            at com.mirth.connect.client.launcher.f.a(SourceFile:2 71)
            at com.mirth.connect.client.launcher.MirthClientLaunc her.run(SourceFile:1122)

            Do I need to open up a directory's permissions?

            Using macOS Mojave Version 10.14.2 with the "bundled" Java Home option in the Mirth Connect Administrator Launcher Version 1.0.0
            Hmm, sounds like a permissions issue on the filesystem. The installer should automatically attempt to set the right permissions, but maybe it wasn't able to. If you open the contents of the .app package you can see the folders within. There should be a "cache" folder there, maybe needs some chmod changes?
            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


            • #21
              Originally posted by khobbs View Post
              Getting this error when trying to connect using this URL
              https://localhost:443/mirth/webstart.jnlp

              Unable to create cache directory for version: 3.5.1
              java.io.IOException: Unable to create cache directory for version: 3.5.1
              at com.mirth.connect.client.launcher.f.a(SourceFile:2 71)
              at com.mirth.connect.client.launcher.MirthClientLaunc her.run(SourceFile:1122)

              Do I need to open up a directory's permissions?

              Using macOS Mojave Version 10.14.2 with the "bundled" Java Home option in the Mirth Connect Administrator Launcher Version 1.0.0
              Hello,

              same happened to me running on a Ubuntu box. Executing this command again with sudo solved the issue.

              Hope this helps,

              RB

              Comment


              • #22
                Unable to retrieve payload

                Thank you for the response, I changed the permissions of the cache directory and got further.

                Now I get this error. I'm sorry if this is annoying, I've just not sure what's wrong.

                Unable to retrieve payload from HTTP request. URI: https://localhost:443/webstart/exten...tfilestep.jnlp
                java.lang.Exception: Unable to retrieve payload from HTTP request. URI: https://localhost:443/webstart/exten...tfilestep.jnlp
                at com.mirth.connect.client.launcher.f.a(SourceFile:7 82)
                at com.mirth.connect.client.launcher.f.a(SourceFile:6 62)
                at com.mirth.connect.client.launcher.f.a(SourceFile:3 07)
                at com.mirth.connect.client.launcher.MirthClientLaunc her.run(SourceFile:1122)
                at java.lang.Thread.run(Thread.java:748)
                Caused by: java.lang.Exception: HTTP request returned invalid response. HTTP status: HTTP/1.1 404 Not Found, URI: https://localhost:443/webstart/exten...tfilestep.jnlp
                at com.mirth.connect.client.launcher.f.a(SourceFile:7 71)
                ... 4 more

                Comment


                • #23
                  also have the same issue

                  Unable to retrieve payload from HTTP request. URI: http://localhost:8080
                  java.lang.Exception: Unable to retrieve payload from HTTP request. URI: http://localhost:8080
                  at com.mirth.connect.client.launcher.f.a(SourceFile:7 82)
                  at com.mirth.connect.client.launcher.f.a(SourceFile:6 62)
                  at com.mirth.connect.client.launcher.f.a(SourceFile:1 67)
                  at com.mirth.connect.client.launcher.MirthClientLaunc her.run(SourceFile:1122)
                  at java.lang.Thread.run(Unknown Source)
                  Caused by: org.apache.http.conn.HttpHostConnectException: Connect to localhost:8080 [localhost/127.0.0.1, localhost/0:0:0:0:0:0:0:1] failed: Connection refused: connect
                  at org.apache.http.impl.conn.DefaultHttpClientConnect ionOperator.connect(DefaultHttpClientConnectionOpe rator.java:159)
                  at org.apache.http.impl.conn.BasicHttpClientConnectio nManager.connect(BasicHttpClientConnectionManager. java:323)
                  at org.apache.http.impl.execchain.MainClientExec.esta blishRoute(MainClientExec.java:381)
                  at org.apache.http.impl.execchain.MainClientExec.exec ute(MainClientExec.java:237)
                  at org.apache.http.impl.execchain.ProtocolExec.execut e(ProtocolExec.java:185)
                  at org.apache.http.impl.execchain.RetryExec.execute(R etryExec.java:89)
                  at org.apache.http.impl.execchain.RedirectExec.execut e(RedirectExec.java:111)
                  at org.apache.http.impl.client.InternalHttpClient.doE xecute(InternalHttpClient.java:185)
                  at org.apache.http.impl.client.CloseableHttpClient.ex ecute(CloseableHttpClient.java:83)
                  at com.mirth.connect.client.launcher.f.a(SourceFile:7 66)
                  ... 4 more
                  Caused by: java.net.ConnectException: Connection refused: connect
                  at java.net.DualStackPlainSocketImpl.waitForConnect(N ative Method)

                  Comment


                  • #24
                    certificate verification

                    Does this use it's own trust store? It doesn't accept the signing certificate on my plug in.

                    Comment


                    • #25
                      Originally posted by ashields View Post
                      Does this use it's own trust store? It doesn't accept the signing certificate on my plug in.
                      It should, as long as the cert is signed by a proper CA and has one of the "code signing" X.509 extensions. Post your public cert here and we can see whether it meets those criteria.
                      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


                      • #26
                        Whoops, sorry. My bad. Looks like somebody changed our dev build environment to use a self signed certificate.
                        Thanks

                        Comment


                        • #27
                          Hello and thanks for your help in advance.

                          I just installed this admin launcher and I'm attempting to launch a client's Mirth Connect and I'm getting an error after I click the Launch button. It says it is Requesting main JNLP... and then it gives this error: "Unable to retrieve payload from HTTP request. URI is the one I entered and was given by the client.

                          I have no idea what the Mirth Connect versions are at the client, they say they are older. I'm connected to their network on a VPN secure connection and then launching from this app. All I know is that the Mirth Connect is installed on a Linux box.

                          Do you have any idea where this error is coming from?
                          Would there be a configuration on this admin launcher that would correct this?

                          Comment


                          • #28
                            I was able to Launch Mirth that resides on a Windows server at the same client.
                            FYI...I disconnected from the VPN and attempted to Launch the Windows based Mirth and I got the exact same error that I got while attempting to launch the Linux based Mirth's,

                            "Unable to retrieve payload from HTTP request. URI:***"

                            Comment


                            • #29
                              Error 2.1.1.5490 instance

                              When trying to connect to a 2.1.1.5490 instance i'm getting the below error. Anything I can try? I wasn't able to get it to work through the regular process from my PC so was hoping this would work.

                              Code:
                              java.lang.NullPointerException
                              java.util.concurrent.ExecutionException: java.lang.NullPointerException
                              	at java.util.concurrent.FutureTask.report(Unknown Source)
                              	at java.util.concurrent.FutureTask.get(Unknown Source)
                              	at com.mirth.connect.client.launcher.f.a(SourceFile:406)
                              	at com.mirth.connect.client.launcher.f.a(SourceFile:365)
                              	at com.mirth.connect.client.launcher.MirthClientLauncher.run(SourceFile:1122)
                              	at java.lang.Thread.run(Unknown Source)
                              Caused by: java.lang.NullPointerException
                              	at com.mirth.connect.client.launcher.f.a(SourceFile:609)
                              	at com.mirth.connect.client.launcher.f.a(SourceFile:536)
                              	at java.util.concurrent.FutureTask.run(Unknown Source)
                              	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
                              	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
                              	... 1 more

                              Comment


                              • #30
                                Administrator launcher doesn't like http.contextpath in the mirth config. We are running Mirth Connect (3.4.2.8129) with http.contextpath set to /mirthconnect. When I access mirth connect directly via https://10.104.0.3:8443/mirthconnect everything works fine, however when trying to use Administrator launcher with url set to https://10.104.0.3:8443/mirthconnect I get an error message saying:

                                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(DOMParser.java:257)
                                at com.sun.org.apache.xerces.internal.jaxp.DocumentBu ilderImpl.parse(DocumentBuilderImpl.java:339)
                                at javax.xml.parsers.DocumentBuilder.parse(DocumentBu ilder.java:121)
                                at com.mirth.connect.client.launcher.f.a(SourceFile:6 64)
                                at com.mirth.connect.client.launcher.f.a(SourceFile:1 67)
                                at com.mirth.connect.client.launcher.MirthClientLaunc her.run(SourceFile:1122)
                                at java.lang.Thread.run(Thread.java:748)

                                When I remove the http.contextpath, restart mirth connect and use https://10.104.0.3:8443/ in stead, Administrator Launcher works fine.

                                Nico

                                Comment

                                Working...
                                X