TIBCO BusinessEvents Enterprise Edition 6.2.2 Hotfix-01 is available
book
Article ID: KB0100785
calendar_today
Updated On:
Products
Versions
TIBCO BusinessEvents Enterprise Edition
6.2.2 hotfix-01
Description
Please follow instructions below to download the hotfix:
Login to TIBCO Support Portal using your TIBCO Support Portal credentials.
After logging in select menu option “Downloads” -> “Hotfixes” , then navigate to /AvailableDownloads/BusinessEvents/EnterpriseEdition/6.2.2/hotfix-01 to download the Hotfix.
Alternatively, you can use the direct portal link to download 6.2.2 Hotfix-01. https://support.tibco.com/s/hotfixes?id=a014z00000yk1jvAAA
================================================================================
Closed Issues in 6.2.2_HF-001 (This Release)
BE-31022
The retry mechanism for cluster locks fails to handle lock calls when timeout
is set to -1 (forever) and thus blocking the inference agent.
BE-31018
Instance assertion for duplicate check in the working memory is running
slow for a large data set when be.engine.id.useLegacy is set to false.
BE-31017
While creating concepts from event payload, extId in the child element
is not used and incorrect extIds are set for parent and child elements.
BE-31008
When a project is running for a long time with a continuous query
containing aggregate functions, the memory consumption keeps growing.
A new property be.engine.query.optimize.aggregate has been added
to fix this. Set its value to true to enable the optimization
of aggregate functions. The default value of the property is false.
BE-31001
After migrating schema from legacy ID to the new key-based ID lookup,
the TIBCO BusinessEvents application is not working when there are
unreferenced records in the database.
This is now fixed. Set the be.engine.id.migrated.allowAdjust to true
in your project CDD or be-engine.tra file for migrating applications
with unreferenced records.
BE-30994
An external JDBC client can connect to TIBCO BusinessEvents Apache
Ignite cluster without any SSL connectivity or user authentication.
Now, you can add the “enable-authentication” property and set its value
to true in the store.xml file to enable the user authentication
for Apache Ignite.
================================================================================
Environment
Windows, Linux and MacOS
Resolution
Please refer to attached hotfix readme file for installation instructions, affected files and list of fixes in this release.
Issue/Introduction
TIBCO BusinessEvents Enterprise Edition 6.2.2 Hotfix-01 is available
Attachments
TIBCO BusinessEvents Enterprise Edition 6.2.2 Hotfix-01 is availableget_app