TIBCO BusinessEvents engine crashes when using tibpgm multicast discovery mechanism on MacOS
book
Article ID: KB0075334
calendar_today
Updated On:
Products
Versions
TIBCO BusinessEvents Enterprise Edition
5.x
Description
TIBCO BusinessEvents engine crashes when using default multicast tibpgm discovery mechanism on MacOS.
Here are the crash logs:
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x000000012d74ec1b, pid=11602, tid=5891
#
# JRE version: Java(TM) SE Runtime Environment (11.0.4+10) (build 11.0.4+10-LTS)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (11.0.4+10-LTS, mixed mode, sharing, tiered, compressed oops, g1 gc, bsd-amd64)
# Problematic frame:
# C [libas-tibpgm.dylib+0x2ac1b] WRMF::num_mcast_ifaces()+0x2b
#
Environment
Platform: Mac OS X
TIBCO BusinessEvents Versions 5.x
Resolution
The crash happened in ActiveSpaces native code libas-tibpgm.dylib
###### # Problematic frame: # C [libas-tibpgm.dylib+0x2ac1b] WRMF::num_mcast_ifaces()+0x2b ######
This happens when using the default multicast cluster member discovery process to form the ActiveSpaces cluster.
Note: Multicast discovery (tibpgm) mechanism got deprecated and this feature will be removed in future releases.
To resolve this issue ,switch multicast to unicast cluster member discovery process. Unicast discovery uses the TCP protocol. Set the discovery and listen property "be.engine.cluster.as.discover.url" , be.engine.as.listen.url as tcp://ip:port[;ip:port]*/
For eg: be.engine.as.discover.url= tcp://IPAddress:5555 be.engine.as.listen.url= tcp://IPAddress:5555-*/
Issue/Introduction
TIBCO BusinessEvents engine crashes when using tibpgm discovery mechanism on Mac OS