Announcement

Collapse
No announcement yet.

Mirth Connect Administrator Crashes after MacOs upgrade to Monterey Version 12.0.1

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

  • Mirth Connect Administrator Crashes after MacOs upgrade to Monterey Version 12.0.1

    Hi Community,

    Could someone help resolving this error? After upgrading to Mac OS Monterey, Mirth Connect Administrator launching as well Administrator crashes sporadically making it unusable?

    Based on the crash (information below), it clearly seems like Java issue. I have changed the JAVA Home environment variable, updated java, tried to use custom/default java location instead of the bundled version and still I am unable to resolve this issue. All other apps (needing java) seem to work without issues.

    Thanks in advance.

    -------------------------------------
    Translated Report (Full Report Below)
    -------------------------------------

    Process: java [97044]
    Path: /Applications/Mirth Connect Administrator Launcher.app/Contents/java/app/mcadministrator/macos/../../../../Plugins/jre.bundle/Contents/Home/jre/bin/java
    Identifier: java
    Version: ???
    Code Type: X86-64 (Native)
    Parent Process: launchd [1]
    User ID: 503

    Date/Time: 2021-11-23 17:53:28.3843 -0500
    OS Version: macOS 12.0.1 (21A559)
    Report Version: 12
    Anonymous UUID: BD2DD766-A73C-4436-F60A-49F90286DB2F

    Sleep/Wake UUID: 09497398-86B9-47DE-9837-A0A36D749ED6

    Time Awake Since Boot: 970000 seconds
    Time Since Wake: 61230 seconds

    System Integrity Protection: enabled

    Notes:
    thread_get_state(PAGEIN) returned 0x10000003: (ipc/send) invalid destination port
    thread_get_state(EXCEPTION) returned 0x10000003: (ipc/send) invalid destination port
    thread_get_state(FLAVOR) returned 0x10000003: (ipc/send) invalid destination port

    Crashed Thread: 33 Java: Thread-7

    Exception Type: EXC_CRASH (SIGABRT)
    Exception Codes: 0x0000000000000000, 0x0000000000000000
    Exception Note: EXC_CORPSE_NOTIFY

    Application Specific Information:
    abort() called

    Error Formulating Crash Report:
    thread_get_state(PAGEIN) returned 0x10000003: (ipc/send) invalid destination port
    thread_get_state(EXCEPTION) returned 0x10000003: (ipc/send) invalid destination port
    thread_get_state(FLAVOR) returned 0x10000003: (ipc/send) invalid destination port


    Thread 33 Crashed:: Java: Thread-7
    0 libsystem_kernel.dylib 0x7ff819a99112 __pthread_kill + 10
    1 libsystem_pthread.dylib 0x7ff819acf233 pthread_kill + 263
    2 libsystem_c.dylib 0x7ff819a1bd10 abort + 123
    3 libjvm.dylib 0x10fc0bad9 os::abort(bool) + 25
    4 libjvm.dylib 0x10fd33d22 VMError::report_and_die() + 2304
    5 libjvm.dylib 0x10f967185 report_vm_error(char const*, int, char const*, char const*) + 84
    6 libjvm.dylib 0x10fc6369c SafepointSynchronize::block(JavaThread*) + 440
    7 libjvm.dylib 0x10fcec95e JavaThread::check_safepoint_and_suspend_for_native _trans(JavaThread*) + 232
    8 libjvm.dylib 0x10f8e8a0e ThreadStateTransition::trans_from_native(JavaThrea dState) + 150
    9 libjvm.dylib 0x10fa94535 jni_DeleteGlobalRef + 53
    10 libglass.dylib 0x15ce569d1 -[GlassRunnable dealloc] + 49
    11 libobjc.A.dylib 0x7ff8199830fe objc_object::sidetable_release(bool, bool) + 232
    12 Foundation 0x7ff81aa1e10b -[_NSThreadPerformInfo dealloc] + 42
    13 libobjc.A.dylib 0x7ff8199830fe objc_object::sidetable_release(bool, bool) + 232
    14 Foundation 0x7ff81a9eadc7 -[NSObject(NSThreadPerformAdditions) performSelectorOnMainThread:withObject:waitUntilDo ne:] + 124
    15 ??? 0x117f9f3fc ???
    16 ??? 0x117ec723c ???
    17 ??? 0x1169467a7 ???
    18 libjvm.dylib 0x10fa6dcba JavaCalls::call_helper(JavaValue*, methodHandle*, JavaCallArguments*, Thread*) + 1710
    19 libjvm.dylib 0x10fa6e45e JavaCalls::call_virtual(JavaValue*, KlassHandle, Symbol*, Symbol*, JavaCallArguments*, Thread*) + 356
    20 libjvm.dylib 0x10fa6e60a JavaCalls::call_virtual(JavaValue*, Handle, KlassHandle, Symbol*, Symbol*, Thread*) + 74
    21 libjvm.dylib 0x10fac8ef9 thread_entry(JavaThread*, Thread*) + 124
    22 libjvm.dylib 0x10fceda7f JavaThread::thread_main_inner() + 155
    23 libjvm.dylib 0x10fcef17a JavaThread::run() + 450
    24 libjvm.dylib 0x10fc0c342 java_start(Thread*) + 246
    25 libsystem_pthread.dylib 0x7ff819acf514 _pthread_start + 125
    26 libsystem_pthread.dylib 0x7ff819acb02f thread_start + 15


    -----------
    Full Report
    -----------

    {"app_name":"java","timestamp":"2021-11-23 17:53:28.00 -0500","app_version":"","slice_uuid":"31a33169-9cd9-3f99-93a0-1d4715ed56a7","build_version":"","platform":1,"sha re_with_app_devs":0,"is_first_party":1,"bug_type": "309","os_version":"macOS 12.0.1 (21A559)","incident_id":"81A2DFE7-B2B2-498D-96EE-F8017B739398","name":"java"}
    {
    "uptime" : 970000,
    "procLaunch" : "2021-11-23 17:52:56.9729 -0500",
    "procRole" : "Background",
    "version" : 2,
    "userID" : 503,
    "deployVersion" : 210,
    "modelCode" : "MacBookPro14,1",
    "procStartAbsTime" : 971318302392581,
    "coalitionID" : 71968,
    "osVersion" : {
    "train" : "macOS 12.0.1",
    "build" : "21A559",
    "releaseType" : "User"
    },
    "reportNotes" : [
    "thread_get_state(PAGEIN) returned 0x10000003: (ipc\/send) invalid destination port",
    "thread_get_state(EXCEPTION) returned 0x10000003: (ipc\/send) invalid destination port",
    "thread_get_state(FLAVOR) returned 0x10000003: (ipc\/send) invalid destination port"
    ]
    }

    ​​

  • #2
    Is that an m1 mac?
    Diridium Technologies, Inc.
    https://diridium.com

    Comment


    • #3
      It is not a m1 mac.

      Comment


      • #4
        I got same problem.
        Waiting how to fix this.
        Thank you.

        Comment


        • #5
          That seems to be a macos Monterrey thing irrespective of Mirth.

          The launcher does embed java 8 however that can be overridden. I would suggest that the folks with this problem try assorted flavors of Java until they find a solution. I have a 2014 MacBook Pro and can’t upgrade to Monterey to help you all out.
          Diridium Technologies, Inc.
          https://diridium.com

          Comment


          • #6
            Tried several versions of Java and still no resolution.

            Comment


            • #7
              Why don't you document here the exact versions you tried so others don't repeat your effort?
              Diridium Technologies, Inc.
              https://diridium.com

              Comment


              • #8
                I forgot my Mac mini is newer. I am using Amazon Corretto and don't seem to have an issue. But even with the built in JRE sessions are stable.

                java -version
                openjdk version "11.0.7" 2020-04-14 LTS
                OpenJDK Runtime Environment Corretto-11.0.7.10.1 (build 11.0.7+10-LTS)
                OpenJDK 64-Bit Server VM Corretto-11.0.7.10.1 (build 11.0.7+10-LTS, mixed mode)
                Last edited by pacmano; 11-27-2021, 02:24 PM.
                Diridium Technologies, Inc.
                https://diridium.com

                Comment


                • #9
                  pacmano - Thanks for helping but I am still facing the crashes even after installing Amazon Corretto openjdk version 11.0.7 (also tried with the latest version 11.0.13).

                  The java versions I have tried so far: jdk8u311, jdk8u192, jdk8u162, jdk8u152

                  Comment


                  • #10
                    I can’t get it to not work correctly. Even with java 17.
                    Diridium Technologies, Inc.
                    https://diridium.com

                    Comment


                    • #11
                      I have the same issue. Always worked fine until I installed Monterey update. I'm not savvy enough to play around with different version of Java. Would be very interested in concrete tips I could try to fix this issue. I'm using NextGen connect a lot, so this is very annoying.

                      Comment


                      • #12
                        Originally posted by bdewulf View Post
                        I'm not savvy enough to play around with different version of Java. Would be very interested in concrete tips I could try to fix this issue. I'm using NextGen connect a lot, so this is very annoying.
                        Sounds like a great time to become savvy. And contribute back to the community rather than complaining and not helping. When I first contributed to this forum, I knew very little about Mirth/Java. Answering others' questions about Mirth or the underlying OS or Java problems was very beneficial to learning.
                        Last edited by pacmano; 11-30-2021, 09:10 AM.
                        Diridium Technologies, Inc.
                        https://diridium.com

                        Comment


                        • #13
                          I got it to work indirectly (quick fix to enable my work) by installing VMware Fusion (free version) then Windows 10 (Home free version) and installing Mirth Connect Administrator on it. There is an issue where Mirth client appears very small in VMware but I could use magnifier tool in windows to access the channels and interface.

                          Comment


                          • #14
                            I have the same issue on my Macbook M1. Several options I have tried.

                            Mirth Connect Administrator - Apple M1 Pro - Mirth Community (mirthproject.io)

                            The issue you have with it being small is due to Retina, disable it in the Fusion VM or there are configurations you can do to the executable that will fix it.

                            Comment


                            • #15
                              Same issue here, right after upgrading to Monterey on an iMac (non M1 chip). I also tried a full uninstall and brand new install of java (java version "1.8.0_311") and no dice. This is quite problematic since my main machine is this iMac. I always told myself to wait a looooong time until upgrading to a new Mac OS, and again I couldn't wait, and again I get some program that stops working. Arghh.... I can try anything else that anybody might think of. Right now, to get around using a remote desktop to a Windows machine (argh!) but at least I get access.

                              I need to resolve this though. I have another Mac with Monterey which has an M1 chip. I'll try that and report back.

                              Comment

                              Working...
                              X