ReadyAPI 3.4.0 crashing on BigSur

[NickMitricka]

I recently upgraded my machine to the BigSur beta and I am unable to open ReadyAPI 3.4.0. It crashes consistently with the below.

Process:               JavaApplicationStub [10345]
Path:                  /Applications/ReadyAPI-3.4.0.app/Contents/MacOS/JavaApplicationStub
Identifier:            com.install4j.3080-8797-1984-6034.376
Version:               3.4.0 (3.4.0)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           JavaApplicationStub [10345]
User ID:               1916737258

Date/Time:             2020-10-28 13:04:15.509 -0400
OS Version:            macOS 11.0 (20A5395g)
Report Version:        12
Bridge OS Version:     5.0 (18P50402b)
Anonymous UUID:        CECB179B-B48C-D8B5-0A3D-7A9E1818AA7A


Time Awake Since Boot: 99000 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGABRT)
Exception Codes:       KERN_INVALID_ADDRESS at 0x000000000008f000
Exception Note:        EXC_CORPSE_NOTIFY

VM Regions Near 0x8f000:
--> 
    __TEXT                      100000000-10000c000    [   48K] r-x/rwx SM=COW  /Applications/ReadyAPI-3.4.0.app/Contents/MacOS/JavaApplicationStub

Application Specific Information:
abort() called

Has anyone seen this issue and/or know a solution to get it working?

[rajs2020]

I am new to ReadyAPI. But, here is a suggestion. Try to find out where your ReadyAPI logs are in MacOS and look for clues in ready-api.log and/or ready-api-errors.log files. Post any log errors here as they could help in diagnosing your issue.

Btw, for Windows, logs are stored here:
c:\users\username\.readyapi\logs

Look for a similar location in MacOS.

[NickMitricka]

The logs that get created give no additional details.  This is the ready-api.log file (sanitized for personal information)

2020-10-28 15:00:27,541 INFO  [license] ReadyAPI 3.4.0 (build 6037) started - System properties: {OS=Mac OS X, User name=XXXXX}
2020-10-28 15:00:27,758 INFO  [DefaultSoapUICore] ReadyAPI settings were initialized from [XXXXX/.readyapi/readyapi-settings.xml]
2020-10-28 15:00:27,786 INFO  [SoapUIExtensionClassLoader] "/Applications/ReadyAPI-3.4.0.app/Contents/Resources/app/bin/ext/sqljdbc42.jar" has been added to the classpath.
2020-10-28 15:00:27,786 INFO  [SoapUIExtensionClassLoader] "/Applications/ReadyAPI-3.4.0.app/Contents/Resources/app/bin/ext/postgresql-9.3-1102.jdbc41.jar" has been added to the classpath.
2020-10-28 15:00:27,786 WARN  [SoapUIExtensionClassLoader] The path to the custom library is not specified.
2020-10-28 15:00:27,828 INFO  [DefaultSoapUICore] 2 JDBC drivers have been registered from the directory bin/ext: [com.microsoft.sqlserver.jdbc.SQLServerDriver, org.postgresql.Driver].
2020-10-28 15:00:28,006 INFO  [DefaultSoapUICore] Adding listeners from [/Applications/ReadyAPI-3.4.0.app/Contents/Resources/app/bin/listeners/demo-listeners.xml]
2020-10-28 15:00:28,022 WARN  [SoapUIJasperReportManager] The report directory "XXXXX/report_templates/reports" does not exist. The default report directory will be used.

There is no data written to ready-api-errors.log or global-groovy.log

[sonya_m]

Thank you for willing to help here rajs2020 🙂

@NickMitricka I think Support Team should see this!

[sonya_m]

@NickMitricka I found your support case (00456514), looks like our engineers are waiting for some info from you. Please keep working with them there. The ReadyAPI Community will also appreciate it if you post the final solution here. Thank you!

[NickMitricka · Accepted solution]

UPDATE: Issue appears to be due to a bug in JDK12.

[jasond]

and what is the solution ?

Blocking work in a critical path.

[NickMitricka]

@jasond  - I was told that they were going to be opening a ticket to fix the Java bug. My machine completely crashed and had to have it wiped and re-imaged. I would suggest trying to use a lower version of Java (say 9 or 11 possibly)

[jasond]

Ya Im already on v8.