The value set for the following TRA property was ignored: java.property.tangosol.coherence.distributed.backupcount
Article ID: KB0088607
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | - |
| Not Applicable | - |
Description
CR 1-AV0DA5 was fixed in TIBCO BusinessEvents 3.0.2 HF1. The issue was that the value set for the following TRA property was ignored: java.property.tangosol.coherence.distributed.backupcount . However, for a project configured with a JDBC backing store, the fix does not take effect until the latest coherence-cache-config-jdbc.xml is available in the correct directory. The JDBC backing store option was introduced in the TIBCO BusinessEvents 3.0.2 release.
Symptoms:
When a JDBC backing store is in use, the fix for the issue CR 1-AV0DA5, provided in TIBCO BusinessEvents 3.0.2 HF1, does not take effect until a post installation procedure is performed.
Cause:
The Hotfix Installer is not configured to install the bundled version of the coherence-cache-config-jdbc.xml file in the appropriate directory.
Issue/Introduction
Resolution
Extract the coherence-cache-config-jdbc.xml file from the cohererence.jar file located in the <TIBCO_HOME>/BE/3.0/hotfix/lib/ext directory to the <TIBCO_HOME>/BE/3.0/hotfix/lib/ext directory. Confirm that the coherence-cache-config-jdbc.xml file is used in all runtime installations as well as design-time installations. Also be sure that all other properties related to the JDBC backing store are set as needed. For example, the property java.property.tangosol.coherence.distributed.backupcount should be set to the desired value. Refer to the topic "Setting Up a JDBC Backing Store" in TIBCO BusinessEvents 3.0.2 Release Notes for details. The issue will be fixed in an upcoming TIBCO BusinessEvents release. Until the fix is available, use the workaround provided above.
Additional Information
Feedback
