TIBCO BusinessEvents engine crashes when started without network connection.
Article ID: KB0081971
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | 5.2.2, 5.3.0, 5.4.x, 5.5.0 |
Description
Unable to start TIBCO BusinessEvents instance when the computer is not connected to network. The engine crashes with below error.
+++++++++++++++
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000024affa08, pid=9176, tid=0x000000000000350c
#
# JRE version: Java(TM) SE Runtime Environment (8.0_162-b12) (build 1.8.0_162-b12)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.162-b12 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C [as-core.dll+0x10fa08]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\tmp\be-working-dir\hs_err_pid9176.log
+++++++++++++++
+++++++++++++++
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000024affa08, pid=9176, tid=0x000000000000350c
#
# JRE version: Java(TM) SE Runtime Environment (8.0_162-b12) (build 1.8.0_162-b12)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.162-b12 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C [as-core.dll+0x10fa08]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\tmp\be-working-dir\hs_err_pid9176.log
+++++++++++++++
Issue/Introduction
TIBCO BusinessEvents engine crashes when you start it on starting engine without network connection.
Environment
All Supported Environments
Resolution
TIBCO BusinessEvents supports both unicast(tcp) and multicast(tibpgm - default) for cluster discovery.
The current behaviour is observed with the default tibpgm multicast protocol (when starting BE engines without network conenction) . You can switch to unicast setting for discovery URL to resolve the issue. In general we recommend tcp Unicast (Well-Known Address) cluster member discovery as multicast(tibpgm) will be deprecated in future releases.
The current behaviour is observed with the default tibpgm multicast protocol (when starting BE engines without network conenction) . You can switch to unicast setting for discovery URL to resolve the issue. In general we recommend tcp Unicast (Well-Known Address) cluster member discovery as multicast(tibpgm) will be deprecated in future releases.
Feedback
Yes
No
Powered by
