BusinessConnect engines go to 100 per cent utilization after startup without generating log information

BusinessConnect engines go to 100 per cent utilization after startup without generating log information

book

Article ID: KB0138029

calendar_today

Updated On:

Products Versions
BusinessConnect EDI Protocol 6.11.0
TIBCO BusinessConnect 7.5.0
TIBCO Foresight Instream 9.3.0 and above

Description

Shortly after startup, the BC engine stops generating log entries in the log files, and the CPU utilization goes to 100%

If a thread dump is done, the output looks similar to this:

 

EngineReminderQueue" #17 prio=7 os_prio=0 cpu=31311.39ms elapsed=45.91s tid=0x00007f57140026b0 nid=0xfcac runnable [0x00007f57341d3000]
java.lang.Thread.State: RUNNABLE
at jdk.internal.loader.NativeLibraries.load(java.base@17.0.16/Native Method)
at jdk.internal.loader.NativeLibraries$NativeLibraryImpl.open(java.base@17.0.16/NativeLibraries.java:388)
at jdk.internal.loader.NativeLibraries.loadLibrary(java.base@17.0.16/NativeLibraries.java:232)

  • locked <0x00000000c08dfd10> (a java.util.HashSet)
    at jdk.internal.loader.NativeLibraries.loadLibrary(java.base@17.0.16/NativeLibraries.java:174)
    at jdk.internal.loader.NativeLibraries.findFromPaths(java.base@17.0.16/NativeLibraries.java:315)
    at jdk.internal.loader.NativeLibraries.loadLibrary(java.base@17.0.16/NativeLibraries.java:287)
    at java.lang.ClassLoader.loadLibrary(java.base@17.0.16/ClassLoader.java:2427)
    at java.lang.Runtime.loadLibrary0(java.base@17.0.16/Runtime.java:818)
    at java.lang.System.loadLibrary(java.base@17.0.16/System.java:2006)
    at com.foresight.jinstreamapi.jNHVInStream.<clinit>(jNHVInStream.java:1493)
    at com.tibco.ax.tibedi.runtime.EDIBootStrapExtension.warmUpInstream(EDIBootStrapExtension.java:1823)
  • locked <0x00000000cb054918> (a java.lang.Class for com.tibco.ax.tibedi.runtime.EDIBootStrapExtension)
    at com.tibco.ax.tibedi.runtime.EDIBootStrapExtension.<init>(EDIBootStrapExtension.java:122)
    at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(java.base@17.0.16/Native Method)
    at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(java.base@17.0.16/NativeConstructorAccessorImpl.java:77)
    at jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(java.base@17.0.16/DelegatingConstructorAccessorImpl.java:45)
    at java.lang.reflect.Constructor.newInstanceWithCaller(java.base@17.0.16/Constructor.java:499)
    at java.lang.reflect.ReflectAccess.newInstance(java.base@17.0.16/ReflectAccess.java:128)
    at jdk.internal.reflect.ReflectionFactory.newInstance(java.base@17.0.16/ReflectionFactory.java:347)
    at java.lang.Class.newInstance(java.base@17.0.16/Class.java:645)
    at com.tibco.ax.fw.runtime.impl.RuntimeExtension.sCreateExtension(RuntimeExtension.java:525)
    at com.tibco.ax.fw.runtime.impl.RuntimeBootstrap.sInit(RuntimeBootstrap.java:494)
  • locked <0x00000000c14fcfe0> (a java.lang.Class for com.tibco.ax.fw.runtime.impl.RuntimeBootstrap)
    at com.tibco.ax.fw.runtime.impl.RuntimeBootstrap.sInit(RuntimeBootstrap.java:147)
  • locked <0x00000000c14fcfe0> (a java.lang.Class for com.tibco.ax.fw.runtime.impl.RuntimeBootstrap)
    at com.tibco.plugin.gateway.GatewayBootstrap.init(GatewayBootstrap.java:42)
  • locked <0x00000000c1324e90> (a com.tibco.plugin.gateway.GatewayBootstrap)
    at com.tibco.plugin.gateway.GatewayBootstrap.<init>(GatewayBootstrap.java:36)
    at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(java.base@17.0.16/Native Method)
    at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(java.base@17.0.16/NativeConstructorAccessorImpl.java:77)

This issue has been traced to the default Instream shared libraries (.so files)  in the $INSTREAM directory are not compatible with later Red Hat versions

Environment

Red Hat 8 and above Linux systems only.

Resolution

Instream 9.3 and above introduced separate .so files for RedHat Enterprise in separately labelled bin directories.  The default is labelled bin, and there are two additional libraries, bin_rhel7 and bin_rhel8.  For RedHat 8 and above, copy the .so files from the bin_rhel8 directory to the bin directory, and restart the engine.   The engine should now operate normally.

Issue/Introduction

BusinessConnect engines go to 100 per cent utilization after startup without generating log information.  The engines appear to become non-responsive