TIBCO BusinessWorks™ engine is blocked and eventually runs OutOfMemory when the TIBCO Enterprise Message Service™ server is unavailable.

TIBCO BusinessWorks™ engine is blocked and eventually runs OutOfMemory when the TIBCO Enterprise Message Service™ server is unavailable.

book

Article ID: KB0085440

calendar_today

Updated On:

Products Versions
TIBCO BusinessWorks ProcessMonitor -
Not Applicable -

Description

Description:
When the TIBCO Enterprise Message Service™  (EMS) server is unavailable, the TIBCO BusinessWorks™ ProcessMonitor (BWPM) will buffer log messages into memory. If the memory threshold is reached (maxQueueLength is exceeded), BWPM will block the worker threads of the bwengine. When the EMS server is relaunched, BWPM will reconnect automatically and process the buffered log messages. Nevertheless, it is possible that the bwengine creates new jobs while BWPM is blocking the worker threads. This scenario might cause out of memory exceptions.

Issue/Introduction

TIBCO BusinessWorks™ engine is blocked and eventually runs OutOfMemory when the TIBCO Enterprise Message Service™ server is unavailable.

Resolution

To prevent the out of memory exception, use flow control with regards to the bwengine. There are two options:

1). Use flow control of bwengine.
2). Use the discardPolicy of TIBCO BusinessWorks™ ProcessMonitor (BWPM).

All log messages that have to be discarded due to the unavailability of the messaging layer, are logged into the bwengine’s logfile(s). That means these messages are not really lost. An enhancement request (#1595) has been created for an import tool that allows the user to import these log messages from the bwengine’s logfile(s) into the BWPM Server.