ReadyAPI - 3.3.0 quit unexpectedly

[afatma]

MKC02XR410JG5J:~ $ /Applications/ReadyAPI-3.3.0.app/Contents/MacOS/JavaApplicationStub ; exit;

Listening for transport dt_socket at address: 53677

WARNING: An illegal reflective access operation has occurred

WARNING: Illegal reflective access by com.google.inject.internal.cglib.core.$ReflectUtils$1 (file:/Applications/ReadyAPI-3.3.0.app/Contents/java/app/lib/guice-4.2.2.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)

WARNING: Please consider reporting this to the maintainers of com.google.inject.internal.cglib.core.$ReflectUtils$1

WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations

WARNING: All illegal access operations will be denied in a future release

Configuring log4j from [/Applications/ReadyAPI-3.3.0.app/Contents/java/app/bin/soapui-log4j.xml]

10:32:05,219 INFO  [license] ReadyAPI 3.3.0 (build 5642) started - System properties: {OS=Mac OS X, User name=afatma}

10:32:05,448 INFO  [DefaultSoapUICore] SoapUI settings were initialized from [/Users/afatma/soapui-settings.xml]

10:32:05,551 INFO  [SoapUIExtensionClassLoader] "/Applications/ReadyAPI-3.3.0.app/Contents/Resources/app/bin/ext/sqljdbc42.jar" has been added to the classpath.

10:32:05,552 INFO  [SoapUIExtensionClassLoader] "/Applications/ReadyAPI-3.3.0.app/Contents/Resources/app/bin/ext/postgresql-9.3-1102.jdbc41.jar" has been added to the classpath.

10:32:05,595 INFO  [DefaultSoapUICore] 2 JDBC drivers have been registered from the directory bin/ext: [com.microsoft.sqlserver.jdbc.SQLServerDriver, org.postgresql.Driver].

10:32:05,748 INFO  [DefaultSoapUICore] Adding listeners from [/Applications/ReadyAPI-3.3.0.app/Contents/Resources/app/bin/listeners/demo-listeners.xml]

10:32:06,886 INFO  [DefaultSoapUICore] Adding actions from [/Applications/ReadyAPI-3.3.0.app/Contents/Resources/app/bin/actions/demo-actions.xml]

10:32:06,924 INFO  [DefaultSoapUICore] Defaulting to native L&F for Mac OS X

10:32:06,926 INFO  [PluginManager] 0 plugins loaded in 0 ms

10:32:06,927 INFO  [DefaultSoapUICore] All plugins loaded

#

# A fatal error has been detected by the Java Runtime Environment:

#

#  SIGSEGV (0xb) at pc=0x00007fff208ec029, pid=5448, tid=259

#

# JRE version: OpenJDK Runtime Environment (12.0.1+12) (build 12.0.1+12)

# Java VM: OpenJDK 64-Bit Server VM (12.0.1+12, mixed mode, tiered, compressed oops, g1 gc, bsd-amd64)

# Problematic frame:

# C  [libsystem_platform.dylib+0x1029]  _platform_memmove$VARIANT$Haswell+0x29

#

# No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again

#

# An error report file with more information is saved as:

# /var/folders/55/hl2lskjs7yx78sfllwmhzr540000gq/T//hs_err_pid5448.log

[thread 20995 also had an error]

#

# If you would like to submit a bug report, please visit:

#   http://bugreport.java.com/bugreport/crash.jsp

# The crash happened outside the Java Virtual Machine in native code.

# See problematic frame for where to report the bug.

#

Abort trap: 6

logout

Saving session...

...copying shared history...

...saving history...truncating history files...

...completed.

Deleting expired sessions...none found.

[Process completed]

[GrantElliot]

I thought it was just me who faced this problem, please let me know if you've find anything in this regard. PaybyPlatema

[RickyPonting]

Please elaborate your problem in detail, maybe I can help you in this regard. Thanks My JDF Account

[luluglobal]

"ReadyAPI - 3.3.0 quit unexpectedly" is an error that can occur when using the ReadyAPI software. This error indicates that the application has unexpectedly closed or crashed.

There are several possible causes for this error, including:

1. Outdated software: If you are using an outdated version of ReadyAPI, it may not be compatible with your operating system or other software on your computer.
2. Corrupted files: If any of the files associated with ReadyAPI are corrupted or damaged, it can cause the application to crash.
3. Insufficient system resources: If your computer does not have enough memory or processing power to run ReadyAPI, it may crash or close unexpectedly.

To resolve this error, you can try the following troubleshooting steps:

1. Update ReadyAPI: Make sure that you are using the latest version of ReadyAPI. Check the SmartBear website for any available updates and install them if necessary.

2. Repair or reinstall ReadyAPI: If the issue persists, try repairing or reinstalling ReadyAPI. This can help to fix any corrupted files or configuration issues that may be causing the error.

3. Check system resources: Make sure that your computer has enough memory and processing power to run ReadyAPI. Close any unnecessary programs or processes that may be using up system resources.

4. Contact technical support: If the issue persists after trying these troubleshooting steps, contact SmartBear technical support for further assistance. They may be able to help you identify and resolve the underlying issue causing the error. GMGlobalConnect

[jeonlae]

Thanks for sharing these helpful suggestions. our sainsburysmis webmailmysainsburysess compass app

[marnusdavid]

It seems like you're experiencing an issue with ReadyAPI version 3.3.0. "Quit unexpectedly" typically means that the program encountered an error and had to close abruptly.

Here are some steps you can take to try to resolve this issue:

1. **Restart your Computer:** Sometimes, a simple restart can fix temporary glitches.

2. **Check for Updates:** Ensure that you're using the latest version of ReadyAPI. If not, consider updating to the latest version.

3. **Check System Requirements:** Make sure your computer meets the system requirements for ReadyAPI 3.3.0.

4. **Check for Compatibility Issues:** Ensure that ReadyAPI is compatible with any other software or plugins you might be using.

5. **Corrupted User Data:** Sometimes, user-specific data can get corrupted. Try running ReadyAPI with a fresh user profile or reset the settings.

6. **Check Logs:** Look for any error logs or crash reports that might provide more information about why ReadyAPI crashed.

7. **Contact Support:** If none of the above steps work, consider reaching out to SmartBear's support team. They may have specific troubleshooting steps or be aware of a known issue.

Remember to back up any important projects or data before attempting any major changes or updates.

If you're still having trouble after trying these steps, please provide more specific details about the issue you're facing, and I'll do my best to assist you further.disneyhublogin.vip