Hello dudes. When I run BonitaBPMCommunity-7.1.5 in CentOS 6.7 (64 bit) it does not work and the log file is as follow:

Sean_McP · 29 January 2016 13:19

What Antoine means is install Eclipse for Linux and run that as a separate tool.

If that fails then it’s definitely not Bonitasoft but the CentOS installation that’s the problem

try


yum install eclipse-platform

if that doesn’t work you need to download it and install it, here is a link for Eclipse for 64 bit linux

http://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/mars/1/eclipse-java-mars-1-linux-gtk-x86_64.tar.gz

regards

bakhshayesh · 29 January 2016 15:49

Thank you Sean McP I installed eclipse ( yum install eclipse-platrom ) successfully but when I tried to run eclipse ( # ./eclipse ) I received the following message and running eclipse failed:
Meanwhile how can I copy and paste the ingredients of log file to a word file ?

*CompilerOracle: exclude org/eclipse/core/internal/dtree/DataTreeNode.forwardDeltaWith
CompilerOracle: exclude org/eclipse/jdt/internal/compiler/lookup/ParameterizedMethodBinding.
CompilerOracle: exclude org/eclipse/cdt/internal/core/dom/parser/cpp/semantics/CPPTemplates.instantiateTemplate
CompilerOracle: exclude org/eclipse/cdt/internal/core/pdom/dom/cpp/PDOMCPPLinkage.addBinding
CompilerOracle: exclude org/python/pydev/editor/codecompletion/revisited/PythonPathHelper.isValidSourceFile
CompilerOracle: exclude org/python/pydev/ui/filetypes/FileTypesPreferencesPage.getDottedValidSourceFiles

(Eclipse:8680): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(Eclipse:8680): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)’ failed

(Eclipse:8680): Gtk-CRITICAL **: IA__gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)’ failed

(Eclipse:8680): Gtk-WARNING **: Screen for GtkWindow not set; you must always set
a screen for a GtkWindow before using the window

(Eclipse:8680): Gdk-CRITICAL **: IA__gdk_screen_get_display: assertion `GDK_IS_SCREEN (screen)’ failed

(Eclipse:8680): Gdk-CRITICAL **: IA__gdk_display_get_pointer: assertion `GDK_IS_DISPLAY (display)’ failed

(Eclipse:8680): Gtk-WARNING **: Screen for GtkWindow not set; you must always set
a screen for a GtkWindow before using the window

(Eclipse:8680): Gdk-CRITICAL **: IA__gdk_screen_get_n_monitors: assertion `GDK_IS_SCREEN (screen)’ failed

(Eclipse:8680): Gtk-WARNING **: Screen for GtkWindow not set; you must always set
a screen for a GtkWindow before using the window

(Eclipse:8680): Gdk-CRITICAL **: IA__gdk_screen_get_monitor_geometry: assertion `GDK_IS_SCREEN (screen)’ failed

(Eclipse:8680): Gdk-CRITICAL **: IA__gdk_screen_get_default_colormap: assertion `GDK_IS_SCREEN (screen)’ failed

(Eclipse:8680): Gdk-CRITICAL **: IA__gdk_colormap_get_visual: assertion `GDK_IS_COLORMAP (colormap)’ failed

(Eclipse:8680): Gdk-CRITICAL **: IA__gdk_screen_get_default_colormap: assertion `GDK_IS_SCREEN (screen)’ failed

(Eclipse:8680): Gdk-CRITICAL **: IA__gdk_screen_get_root_window: assertion `GDK_IS_SCREEN (screen)’ failed

(Eclipse:8680): Gdk-CRITICAL **: IA__gdk_window_new: assertion `GDK_IS_WINDOW (parent)’ failed

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

SIGSEGV (0xb) at pc=0x00007f318c442486, pid=8680, tid=139850969274112

JRE version: Java™ SE Runtime Environment (7.0_80-b15) (build 1.7.0_80-b15)

Java VM: Java HotSpot™ 64-Bit Server VM (24.80-b11 mixed mode linux-amd64 compressed oops)

Problematic frame:

C [libgdk-x11-2.0.so.0+0x7a486] gdk_window_enable_synchronized_configure+0x16

Failed to write core dump. 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:

/usr/bin/hs_err_pid8680.log

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.

#*

system · 29 January 2016 15:59

I think you are trying to run Eclipse (and probably also Bonita BPM Studio) as root user.

Usually you logged in in your graphical environment (e.g. Gnome) using a normal user (e.g. bakhshayesh).
And root does not have access to the display.

So I would recommend to try to run Eclipse (and Bonita BPM Studio) using a normal user account (you should not have the # sign in the console when you execute commands as a normal user).

bakhshayesh · 29 January 2016 16:17

I ran the eclipse using a normal user (hadiov) and got the following error messages:

[hadiov@Hadi bin]$ ./eclipse
CompilerOracle: exclude org/eclipse/core/internal/dtree/DataTreeNode.forwardDeltaWith
CompilerOracle: exclude org/eclipse/jdt/internal/compiler/lookup/ParameterizedMethodBinding.
CompilerOracle: exclude org/eclipse/cdt/internal/core/dom/parser/cpp/semantics/CPPTemplates.instantiateTemplate
CompilerOracle: exclude org/eclipse/cdt/internal/core/pdom/dom/cpp/PDOMCPPLinkage.addBinding
CompilerOracle: exclude org/python/pydev/editor/codecompletion/revisited/PythonPathHelper.isValidSourceFile
CompilerOracle: exclude org/python/pydev/ui/filetypes/FileTypesPreferencesPage.getDottedValidSourceFiles

(Eclipse:8782): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(Eclipse:8782): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)’ failed

(Eclipse:8782): Gtk-CRITICAL **: IA__gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)’ failed

(Eclipse:8782): Gtk-WARNING **: Screen for GtkWindow not set; you must always set
a screen for a GtkWindow before using the window

(Eclipse:8782): Gdk-CRITICAL **: IA__gdk_screen_get_display: assertion `GDK_IS_SCREEN (screen)’ failed

(Eclipse:8782): Gdk-CRITICAL **: IA__gdk_display_get_pointer: assertion `GDK_IS_DISPLAY (display)’ failed

(Eclipse:8782): Gtk-WARNING **: Screen for GtkWindow not set; you must always set
a screen for a GtkWindow before using the window

(Eclipse:8782): Gdk-CRITICAL **: IA__gdk_screen_get_n_monitors: assertion `GDK_IS_SCREEN (screen)’ failed

(Eclipse:8782): Gtk-WARNING **: Screen for GtkWindow not set; you must always set
a screen for a GtkWindow before using the window

(Eclipse:8782): Gdk-CRITICAL **: IA__gdk_screen_get_monitor_geometry: assertion `GDK_IS_SCREEN (screen)’ failed

(Eclipse:8782): Gdk-CRITICAL **: IA__gdk_screen_get_default_colormap: assertion `GDK_IS_SCREEN (screen)’ failed

(Eclipse:8782): Gdk-CRITICAL **: IA__gdk_colormap_get_visual: assertion `GDK_IS_COLORMAP (colormap)’ failed

(Eclipse:8782): Gdk-CRITICAL **: IA__gdk_screen_get_default_colormap: assertion `GDK_IS_SCREEN (screen)’ failed

(Eclipse:8782): Gdk-CRITICAL **: IA__gdk_screen_get_root_window: assertion `GDK_IS_SCREEN (screen)’ failed

(Eclipse:8782): Gdk-CRITICAL **: IA__gdk_window_new: assertion `GDK_IS_WINDOW (parent)’ failed

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

SIGSEGV (0xb) at pc=0x00007efc4df29486, pid=8782, tid=139622591727360

JRE version: Java™ SE Runtime Environment (7.0_80-b15) (build 1.7.0_80-b15)

Java VM: Java HotSpot™ 64-Bit Server VM (24.80-b11 mixed mode linux-amd64 compressed oops)

Problematic frame:

C [libgdk-x11-2.0.so.0+0x7a486] gdk_window_enable_synchronized_configure+0x16

Failed to write core dump. 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:

/tmp/hs_err_pid8782.log

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.

Sean_McP · 29 January 2016 18:54

I’ll be honest, after seeing that eclipse won’t even work I think your base CentOS is corrupt.

If Bonitasoft have managed to get it working without any to-do. I’m stuck on a download otherwise I would try.

The log basically seems to say gtk is corrupt/not installed…

Definitely something wrong with the OS

regards
Seán

Sean_McP · 30 January 2016 09:59

This is how I did my install from minimal:

Boot from ISO
Welcome screen → Install
Welcome screen → Next
Select language → Next
Select Keyboard → Next
Basic Storage → Next
Yes Discard any Data
Hostname = centos67-01.localdomain → Next
Select timezone → Next
Give root password → Next
Use all space → Next
→ Next to create space
Install boot loader - no changes → Next
Installing x of 205 packages
Congratulations root → Reboot

Login in

couldn’t get my internet up so did
ifconfig eth0 up dhclient eth0 yum install NetworkManager
everything working

Install eclipse using


yum install eclipse-platform

I then executed eclipse and I get the same as you - errors…

Then I added desktop components


yum groupinstall "Desktop" "Desktop Platform" "X Window System" "Fonts"

from: http://blog.nowherelan.com/2013/12/24/install-a-desktop-environment-on-centos-minimal-install/

and tried eclipse again…still failed

added a new user with SUDO


adduser username
gpasswd -a username wheel
passwd username

Logged out of root and as new user

Started the GUI
startx

opened a terminal window and tried eclipse again…

YES ECLIPSE WORKS!!!

Boy - Windows is much easier…

So this confirms it to my understanding - minimum install of CentOS is NOT suitable for running Bonitasoft.

You should install a more capable level of CentOS that has a graphical interface, for example gnome or something else.

Well that’s my finding anyway…

regards
Seán

bakhshayesh · 31 January 2016 10:03

Thank you very much dear Sean
I entered the command " startx " as a non root user and the graphical environment windows opened.
I executed eclipse and it worked properly.
But when I ran the Bonita 1.7.5 I received this error message : "An error has occurred. See the log file /.eclipse/… " and the log file is here.
<

I also receive a message that Tomcat 7 failed to start.

Topic		Replies	Views
Error when launching Bonita On server Q&A	1	5	25 July 2014
BonitaStudioCommunity failed to start Q&A	4	7	28 September 2022
Unable to process "BonitaStudioWorkbenchAdvisor.repositoryAccessor": error Q&A	2	1	18 January 2020
[Solved] Bonita doesn't start Q&A	5	3	30 May 2014
SWTBot: My New friend Blog	0	52	2 February 2010

Hello dudes. When I run BonitaBPMCommunity-7.1.5 in CentOS 6.7 (64 bit) it does not work and the log file is as follow:

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

SIGSEGV (0xb) at pc=0x00007f318c442486, pid=8680, tid=139850969274112

JRE version: Java™ SE Runtime Environment (7.0_80-b15) (build 1.7.0_80-b15)

Java VM: Java HotSpot™ 64-Bit Server VM (24.80-b11 mixed mode linux-amd64 compressed oops)

Problematic frame:

C [libgdk-x11-2.0.so.0+0x7a486] gdk_window_enable_synchronized_configure+0x16

Failed to write core dump. 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:

/usr/bin/hs_err_pid8680.log

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.

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

SIGSEGV (0xb) at pc=0x00007efc4df29486, pid=8782, tid=139622591727360

JRE version: Java™ SE Runtime Environment (7.0_80-b15) (build 1.7.0_80-b15)

Java VM: Java HotSpot™ 64-Bit Server VM (24.80-b11 mixed mode linux-amd64 compressed oops)

Problematic frame:

C [libgdk-x11-2.0.so.0+0x7a486] gdk_window_enable_synchronized_configure+0x16

Failed to write core dump. 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:

/tmp/hs_err_pid8782.log

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.

Related topics