Resolution:

Issue:

====

When the Microsoft SQL Server Backing Store Database goes offline and then comes back online, TIBCO BusinessEvents does not reconnect. The following warning messages are thrown.

Error Messages:

==========

2015 Mar 26 09:31:15:773 GMT -4 Risk-1 Warning[FraudDetectionCache.0.$smtimeouts.DBPoller] - [runtime.service] DBPoller:  SQL Connection Unavailable, Skipping
2015 Mar 26 09:31:25:773 GMT -4 Risk-1 Warning[FraudDetectionCache.0.$smtimeouts.DBPoller] - [runtime.service] DBPoller:  SQL Connection Unavailable, Skipping
2015 Mar 26 09:31:35:774 GMT -4 Risk-1 Warning[FraudDetectionCache.0.$smtimeouts.DBPoller] - [runtime.service] DBPoller:  SQL Connection Unavailable, Skipping

Resolution:

=======

This is a known issue in BusinessEvents 5.1.2 and this has been fixed in version 5.1.4. Both Cache and Inference agents recreate connections after the backing store has been restored when tested in BE 5.1.4 . 

Note:

====

By default, the Backing Store database connection should be reconnected when the database is available. The following are a few Backing Store properties for tuning.

be.backingstore.recreateOnRecovery=true
be.backingstore.test.connections.interval=30
be.backingstore.connection.retry.count=-1
be.backingstore.test.connections.checkall=true

TIBCO BusinessEvents not restoring a connection to Microsoft SQL Server.