How to configure TIBCO BusinessEvents engine with DBConcepts feature to reconnect with Database after the connection gets lost?

book

Article ID: KB0088271

calendar_today

Updated On:

Products Versions
TIBCO BusinessEvents Enterprise Edition -
Not Applicable -

Description

Resolution:
Description:
============

When the connection is lost between TIBCO BusinessEvents (BE) engine running with DBConcepts feature and the database, the BE engine does not reconnect automatically by default.


Environment:
============
o TIBCO BusinessEvents  3.0.1 HF3 release onwards

o Microsoft SQL Server 2005/2008, Oracle 10g

o All OS

Symptoms:
=========
When the connection is lost between BE engine and the database it throws a java.sql.SQLException: [Server JDBC Driver] Broken pipe. And the engine never reconnects. You have to restart the BE engine once the database is up and running.

Cause:
======
This is generally due to lack of configuration in your engine TRA files.


Resolution:
===========
Please enable the following properties in your BE Engine TRA files and restart the engines.

be.dbconcepts.connection.retry.count=-1
be.dbconcepts.connection.check.interval=5

The default retry.count is 0, if you set the retry.count to -1, it indicates that the engine should try to reconnect to the database for ever, and if this is set to a positive integer n then it tries to reconnect n times.

The check.interval value is in seconds, and the default retry interval is 60 seconds, you can increase or decrease this value depending on your needs.


Attachments:
============
None.


References:
===========
None.

Issue/Introduction

How to configure TIBCO BusinessEvents engine with DBConcepts feature to reconnect with Database after the connection gets lost?