Tuesday, 23 January 2018

IBM Integration Bus - Integration Toolkit on Red Hat Enterprise Linux

This is another of my various tinkering exercises ….

I'm attempting to get the IBM Integration Bus (IIB) 9 Toolkit working on my Mac, against a VM running Red hat Enterprise Linux 7.4.

I'm actually tunnelling X11 via SSH ( via ssh -y wasadmin@hostname )

When I attempt to start the Toolkit: -

/opt/ibm/IntegrationToolkit90/launcher 

I see this: -

MQSI 9.0.0.2
/opt/ibm/mqsi/9.0.0.2

 progressRectString:  2,489,646,12
 messageRectString: 12,443,444,15
Unhandled exception
Type=Segmentation error vmState=0x00040000
J9Generic_Signal_Number=00000004 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000080
Handler1=F6B5EACA Handler2=F6B0F017 InaccessibleAddress=00000000
EDI=F750FCA4 ESI=F750FB64 EAX=F7510BF0 EBX=ADA45000
ECX=BFD95F61 EDX=F750FA98
EIP=AD958FAE ES=002B DS=002B ESP=F750FA28
EFlags=00010286 CS=0023 SS=002B EBP=F751000C
Module=/lib/libcairo.so.2
Module_base_address=AD905000
Target=2_60_20120809_118929 (Linux 3.10.0-693.11.6.el7.x86_64)
CPU=x86 (1 logical CPUs) (0x1e7da8000 RAM)
----------- Stack Backtrace -----------
(0xF6B005B0 [libj9prt26.so+0xf5b0])
(0xF6B0FFC2 [libj9prt26.so+0x1efc2])
(0xF6B002A1 [libj9prt26.so+0xf2a1])
(0xF6B00395 [libj9prt26.so+0xf395])
(0xF6AFFEA4 [libj9prt26.so+0xeea4])
(0xF6B0FFC2 [libj9prt26.so+0x1efc2])
(0xF6AFFE13 [libj9prt26.so+0xee13])
(0xF6B5DEF5 [libj9vm26.so+0x14ef5])
(0xF6B0FFC2 [libj9prt26.so+0x1efc2])
(0xF6B5E1FE [libj9vm26.so+0x151fe])
(0xF6B5EB18 [libj9vm26.so+0x15b18])
(0xF6B0F1E5 [libj9prt26.so+0x1e1e5])
__kernel_rt_sigreturn+0x0 (0xF7784410)
(0x00023280 [<unknown>+0x0])
---------------------------------------
JVMDUMP039I Processing dump event "gpf", detail "" at 2018/01/23 15:49:57 - please wait.
JVMDUMP032I JVM requested System dump using '/opt/ibm/IntegrationToolkit90/core.20180123.154957.90680.0001.dmp' in response to an event
JVMPORT030W /proc/sys/kernel/core_pattern setting "|/usr/libexec/abrt-hook-ccpp %s %c %p %u %g %t e %P %I %h" specifies that the core dump is to be piped to an external program.  Attempting to rename either core or core.90725.

JVMDUMP010I System dump written to /opt/ibm/IntegrationToolkit90/core.20180123.154957.90680.0001.dmp
JVMDUMP032I JVM requested Java dump using '/opt/ibm/IntegrationToolkit90/javacore.20180123.154957.90680.0002.txt' in response to an event
JVMDUMP010I Java dump written to /opt/ibm/IntegrationToolkit90/javacore.20180123.154957.90680.0002.txt
JVMDUMP032I JVM requested Snap dump using '/opt/ibm/IntegrationToolkit90/Snap.20180123.154957.90680.0003.trc' in response to an event
JVMDUMP010I Snap dump written to /opt/ibm/IntegrationToolkit90/Snap.20180123.154957.90680.0003.trc
JVMDUMP013I Processed dump event "gpf", detail "".

Appreciating that this is almost certainly an unsupported configuration, I was able to solve the problem, using this as inspiration: -


which said, in part: -

Cause

"adwaita-gtk2-theme" (32 and 64 bit) and "adwaita-gtk3-theme" 64 bit libraries were missing.

Resolving the problem

Install the missing libraries "adwaita-gtk2-theme" (32 and 64 bit) and "adwaita-gtk3-theme" 64 bit. Please contact RedHat to obtain the missing libraries.

I installed the missing RPM: -

/usr/bin/yum --noplugins install -y adwaita-gtk2-theme

  adwaita-gtk2-theme.x86_64 0:3.22.2-1.el7                                                                                                                                                               

Complete!

Removed temporary configuration


and now we're good to go.

For the record, I'd previously installed these two RPMs: -

libpng12.so.0
libXtst.so.6


as required by IBM Installation Manager, installing the Toolkit.

No comments:

Note to self - use kubectl to query images in a pod or deployment

In both cases, we use JSON ... For a deployment, we can do this: - kubectl get deployment foobar --namespace snafu --output jsonpath="{...