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-03 to download the Hotfix.
Alternatively, you can use the direct portal link below to download 6.2.2 Hotfix-03.
https://support.tibco.com/s/hotfixes?id=a014z00000yk1jvAAA
================================================================================
Closed Issues in 6.2.2_HF-003 (This Release)
BE-31498
In TIBCO BusinessEvents, Apache Tomcat is upgraded to the version 9.0.73 to
address the Apache Tomcat CVE-2023-24998 vulnerability.
BE-31468
JSON serialization for large concepts takes a longer time.
BE-31444
JSON serialization for large event payloads takes a longer time.
BE-31425
Consider a scenario when Cache is enabled, and Several FTL channels (same resource)
are configured with different input destinations. In this case, Events are not
published to an outbound destination when unused FTL channels are disabled.
BE-31371
After upgrading from TIBCO BusinessEvents 4.x to TIBCO BusinessEvents 6.x.x,
NullPointerExceptions occur when loading concepts from the cache.
BE-31284
In the key-based ID lookup implementation, xinode conversion fails when loading
the concept with an empty reference.
BE-31282
Header values are not added in HTTP requests when the HTTP operation is set
to "Delete" and the requests are sent with the catalog function HTTP.sendRequest().
BE-31256
Jetty version is upgraded from 9.4.31 to 9.4.49 to address security vulnerabilities.
BE-31180
In TIBCO BusinessEvents, Java version is upgraded to 11.0.17.
BE-31173
TIBCO BusinessEvents observes slow performance with Apache Ignite locking implementation.
BE-31170
Explicit acknowledgment in the FTL channel is now supported.
Set "be.channel.ftl{destURL()}.com.tibco.ftl.client.subscriber.explicitack" property
to true for explicit acknowledgment.
BE-31169
OpenTelemetry tracing with TIBCO BusinessEvents and TIBCO FTL® is supported.
To use the same OpenTelemetry transaction when using OpenTelemetry tracing with
TIBCO BusinessEvents and TIBCO FTL, include the _traceparent field in the data format.
You can either set this field in the tibrealm.json file before starting the FTL server or
configure it through the FTL server by using its GUI interface.
BE-31168
When connecting TIBCO BusinessEvents to Apache Kafka® broker, the system property
sasl.jaas.config is not getting set for Apache Kafka® client.
BE-30982
Data replication does not work when host-aware replication is enabled
and different hostnames are set in the Cluster area ("Hostaware Hostnames").
BE-30744
In the key-based ID lookup implementation, consider a scenario when a concept is
deleted and then recreated in a rule by using the same extID. In this case, the rule
does not trigger correctly because the recreated concept is not identified as a new instance.
================================================================================
Please refer to attached hotfix readme file for installation instructions, affected files and list of fixes in this release.