Users running IBM MQ Explorer version 8 on Red Hat Enterprise Linux (RHEL) 6 may observe that Explorer crashes during use.
Users running IBM MQ Explorer version 8 on Red Hat Enterprise Linux (RHEL) 6 may observe that Explorer crashes during use. The full failure message reported is similar to the following example:
|java: cairo-misc.c:380: _cairo_operator_bounded_by_source: Assertion `NOT_REACHED' failed.|
JVMDUMP039I Processing dump event "abort", detail "" at 2014/11/12 10:02:27 - please wait.
JVMDUMP032I JVM requested System dump using '/tmp/mquser/core.20141112.100227.13953.0001.dmp' in response to an event
JVMDUMP010I System dump written to /tmp/mquser/core.20141112.100227.13953.0001.dmp
JVMDUMP032I JVM requested Java dump using '/tmp/mquser/javacore.20141112.100227.13953.0002.txt' in response to an event
JVMDUMP010I Java dump written to /tmp/mquser/javacore.20141112.100227.13953.0002.txt
JVMDUMP032I JVM requested Snap dump using '/tmp/mquser/Snap.20141112.100227.13953.0003.trc' in response to an event
JVMDUMP010I Snap dump written to /tmp/mquser/Snap.20141112.100227.13953.0003.trc
JVMDUMP007I JVM Requesting JIT dump using '/tmp/mquser/jitdump.20141112.100227.13953.0004.dmp'
#JITDUMP: vmThread=0000000001801D00 Recursive crash occurred. Aborting JIT dump.
#JITDUMP: vmThread=0000000001801D00 Recursive crash occurred. Aborting JIT dump.JVMDUMP010I JIT dump written to /tmp/mquser/jitdump.20141112.100227.13953.0004.dmp
JVMDUMP013I Processed dump event "abort", detail "".
Resolving The Problem
This is a platform specific issue present within the underlying Eclipse platform, and is visible in the Eclipse project bugtracker: https://bugs.eclipse.org/bugs/show_bug.cgi?id=441705
The issue can be mitigated by adding the following line to the MQExplorer.ini file, which can be found in the same directory as the MQExplorer executable, which is typically $MQ_INSTALLATION_PATH\bin:
Each parameter in the MQExplorer.ini file must be on a separate line and so this parameter should be added to the MQExplorer.ini file as a new line, after the following line:
15 June 2018