JVM crashed while launching the soatest 2022.1 from linux virtual server.
JVM crashed while launching the soatest 2022.1 from linux virtual server.
And
Navigate from parasoft >>preferences ... jvm crashed
open jdk 1.8 and 11 .. either way it is not working...
Comments
-
Which Linux flavor and version are you using?
0 -
Can you look for any hs_err_pid*.log file(s) in the tool installation directory? Can you share it?
open jdk 1.8 and 11 .. either way it is not working...
SOAtest 2022.1 requires Java 11 and will not launch with Java 8.
0 -
Java and Linux Redhat7 version:
java -version
openjdk version "11.0.15" 2022-04-19 LTS
OpenJDK Runtime Environment 18.9 (build 11.0.15+9-LTS)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.15+9-LTS, mixed mode, sharing)redhat-release
Red Hat Enterprise Linux Server release 7.9 (Maipo)0 -
could not find the error log, but below is the info from nohup.out file:
==================================================
(SOAtest:22562): dconf-WARNING **: 15:56:33.211: failed to commit changes to dconf: Failed to execute child process “dbus-launch†(No such file or directory)
(SOAtest:22562): dconf-WARNING **: 15:56:33.250: failed to commit changes to dconf: Failed to execute child process “dbus-launch†(No such file or directory)
(SOAtest:22562): dconf-WARNING **: 15:56:33.280: failed to commit changes to dconf: Failed to execute child process “dbus-launch†(No such file or directory)
(SOAtest:22562): dconf-WARNING **: 15:56:33.312: failed to commit changes to dconf: Failed to execute child process “dbus-launch†(No such file or directory)
(SOAtest:22562): dconf-WARNING **: 15:56:33.342: failed to commit changes to dconf: Failed to execute child process “dbus-launch†(No such file or directory)
(SOAtest:22562): dconf-WARNING **: 15:56:33.400: failed to commit changes to dconf: Failed to execute child process “dbus-launch†(No such file or directory)
(SOAtest:22562): dconf-WARNING **: 15:56:35.065: failed to commit changes to dconf: Failed to execute child process “dbus-launch†(No such file or directory)
(SOAtest:22562): dconf-WARNING **: 15:56:35.121: failed to commit changes to dconf: Failed to execute child process “dbus-launch†(No such file or directory)
(SOAtest:22562): dconf-WARNING **: 15:56:35.153: failed to commit changes to dconf: Failed to execute child process “dbus-launch†(No such file or directory)
(SOAtest:22562): dconf-WARNING **: 15:56:35.209: failed to commit changes to dconf: Failed to execute child process “dbus-launch†(No such file or directory)
(SOAtest:22562): dconf-WARNING **: 15:56:35.209: failed to commit changes to dconf: Failed to execute child process “dbus-launch†(No such file or directory)
(SOAtest:22562): Gtk-WARNING **: 15:57:14.633: Could not load a pixbuf from /org/gtk/libgtk/theme/Adwaita/assets/check-symbolic.svg.
This may indicate that pixbuf loaders or the mime database could not be found.
Gdk-Message: 15:57:15.510: SOAtest: Fatal IO error 11 (Resource temporarily unavailable) on X server 10.204.73.57:0.0.Gtk-Message: 15:57:15.861: GtkDialog mapped without a transient parent. This is discouraged.
Parasoft SOAtest: Version 2022.1.0 (10.6.0.202205082000) -- Copyright (C) 2022 Parasoft Corporation
OpenJDK 64-Bit Server VM warning: Ignoring option MaxPermSize; support was removed in 8.0
SWT SessionManagerDBus: Failed to connect to org.gnome.SessionManager: Failed to execute child process “dbus-launch†(No such file or directory)
SWT SessionManagerDBus: Failed to connect to org.xfce.SessionManager: Failed to execute child process “dbus-launch†(No such file or directory)(SOAtest:27103): Gtk-WARNING **: 16:14:28.016: Could not load a pixbuf from /org/gtk/libgtk/theme/Adwaita/assets/check-symbolic.svg.
This may indicate that pixbuf loaders or the mime database could not be found.
Gdk-Message: 16:14:28.933: SOAtest: Fatal IO error 11 (Resource temporarily unavailable) on X server 10.204.73.57:0.0.Gtk-Message: 16:14:29.371: GtkDialog mapped without a transient parent. This is discouraged.
Parasoft SOAtest: Version 2022.1.0 (10.6.0.202205082000) -- Copyright (C) 2022 Parasoft Corporation
OpenJDK 64-Bit Server VM warning: Ignoring option MaxPermSize; support was removed in 8.0
SWT SessionManagerDBus: Failed to connect to org.gnome.SessionManager: Failed to execute child process “dbus-launch†(No such file or directory)
SWT SessionManagerDBus: Failed to connect to org.xfce.SessionManager: Failed to execute child process “dbus-launch†(No such file or directory)
Parasoft SOAtest: Version 2022.1.0 (10.6.0.202205082000) -- Copyright (C) 2022 Parasoft Corporation
OpenJDK 64-Bit Server VM warning: Ignoring option MaxPermSize; support was removed in 8.0
SWT SessionManagerDBus: Failed to connect to org.gnome.SessionManager: Failed to execute child process “dbus-launch†(No such file or directory)
SWT SessionManagerDBus: Failed to connect to org.xfce.SessionManager: Failed to execute child process “dbus-launch†(No such file or directory)
Gdk-Message: 18:31:08.480: SOAtest: Fatal IO error 110 (Connection timed out) on X server 10.204.73.57:0.0.Gdk-Message: 18:31:08.759: eclipse: Fatal IO error 2 (No such file or directory) on X server 10.204.73.57:0.0.
Parasoft SOAtest: Version 2022.1.0 (10.6.0.202205082000) -- Copyright (C) 2022 Parasoft Corporation
SWT SessionManagerDBus: Failed to connect to org.gnome.SessionManager: Failed to execute child process “dbus-launch†(No such file or directory)
SWT SessionManagerDBus: Failed to connect to org.xfce.SessionManager: Failed to execute child process “dbus-launch†(No such file or directory)0 -
Gdk-Message: 18:31:08.480: SOAtest: Fatal IO error 110 (Connection timed out) on X server 10.204.73.57:0.0.
The process could die if it loses connection with your X server as what this error suggests.
0 -
-
thank you for your suggestions. We are using secureCRT with Reflexion X .
0