Description:
"Quorum check will be performed" error is thrown when the TIBCO BusinessEvents engine is started.
Symptoms:
Logfile extract shown containing several errors regarding "Quorum Check" and Database errors.

= = = = =
Error [$default.be.mt$.Thread.6] - [runtime.service] [inference-class] Error occurred in [DefaultDistributedCacheBasedStore]. Quorum check will be performed.
java.lang.RuntimeException: com.tibco.as.space.ASException: SYS_ERROR (persister_exception -
Caused by: com.tibco.as.space.ASPersistenceException: java.lang.RuntimeException: java.lang.NullPointerException

Warning [$default.be.mt$.Thread.6] - [runtime.service] [inference-class] Cache:  Exception in get(22922): Retry num: 1 : com.tibco.as.space.ASException: SYS_ERROR (persister_exception -
Caused by: com.tibco.as.space.ASPersistenceException: java.lang.RuntimeException: java.lang.NullPointerException

Database errors:

2014 Aug 29 19:38:13:691 GMT +2 Default Warning [$default.be.mt$.Thread.3] - [jdbcstore] [inference-class] Check failed. Unable to connect to database.
2014 Aug 29 19:38:13:691 GMT +2 Default Warning [$default.be.mt$.Thread.3] - [runtime.service] [inference-class] DBNotAvailableException Exception: DatabaseException : Database Not Available., Exception=ORA-02396: exceeded maximum idle time, please connect again
,Waiting to reconnect.

Cause:
The "Quorum Check" errors could be generated for a number of reasons.

1). It can be related to an Active Spaces heartbeat error. A heartbeat timeout indicates that there was a network break unknown to the OS and AS process. This generally means the network failed without the OS knowing, such as a cable pull or switch down. Check to see if there is any network problem.

2). Contact the System Administrator to validate the network and monitor CPU and memory usage of the machine.

The Database errors are related to a problem with database connections.

1). Idle time is set in a production database. This can be turned off or you can extend the idle time.

Caused by: com.tibco.as.space.ASPersistenceException: com.tibco.cep.runtime.util.DBNotAvailableException: DatabaseException : Database Not Available., Exception=ORA-02396: exceeded maximum idle time, please connect again

2). The JDBC driver version could be different and obtaining connection properties will fail. This is simply used for logging. Changing the JDBC driver will resolve the problem.
This has been commented out in later versions of BusinessEvents.

= = = = = 
2014 Aug 29 12:10:12:384 GMT +2 InventarioCache-InventarioBE_AOTLXPRBPM00005 Warning [Inventario.objectTableCache-bs-readOnly-Inventario--ObjectTableExtIds.persister] - [jdbcstore] Check failed. Unable to connect to database.
2014 Aug 29 12:10:17:390 GMT +2 InventarioCache-InventarioBE_AOTLXPRBPM00005 Warning [Inventario.objectTableCache-bs-readOnly-Inventario--ObjectTableExtIds.persister] - [jdbcstore] DBNotAvailableException in load() of : Inventario Servicios0.8426235, Message: DatabaseException : Database Not Available., Exception=Connection pool status is disconnected
= = = = =

Idle time is normally set in a production database. This can be turned off or you can extend the idle time.

"Quorum check will be performed" error is thrown when the TIBCO BusinessEvents engine is started.