TIBCO BusinessEvents Enterprise Edition 6.3.0 Hotfix-04 is available
Article ID: KB0100184
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | 6.3.0 hotfix-04, 6.3.0 HF-04, 6.3.0 HF4 |
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.3.0/hotfix-04 to download the Hotfix.
- Alternatively, you can use the direct portal link to download 6.3.0 Hotfix-04.
================================================================================
Closed Issues in 6.3.0_HF-004 (This Release)
BE-32712
The pid$ index is not created for the new table created in *-migrate.sql script
when the database is migrated from legacy to keybase lookup.
BE-32694
Under the load, a native query executing multiple times returns extid as an
Object type instead of String.
To resolve this issue, the following system properties that manages sleeptime
and retrycount for a thread executing query are added:
be.query.thread.sleep. The default value is 5ms.
be.query.retry.count. The default value is 5.
BE-32693
In TIBCO BusinessEvents, Apache Tomcat is upgraded to the version 9.0.87 to
address the Apache Tomcat CVE-2024-24549 vulnerability and the Apache Tomcat
CVE-2024-23672 vulnerability.
BE-32687
The CDD property, com.tibco.be.http.client.useExpectContinue continues to print
even if it is set to false in BE 6.3.0.
BE-32682
The event payload of outbound event, HTTP.sendRequest() is created in XML format
though the JSON flag is enabled.
This occurs when:
1. The project XPATH 1.0 is enabled.
2. Add CDD property, com.tibco.datamodel.xml=false or the property is not set.
BE-32681
The HTTP header, Content-type is added twice to the HTTP request when the
outbound event property, content_type is mapped with a value.
BE-32667
In the KafKa channel, if Poll Previous Messages field is selected, then messages
are retrieved based on the timestamp given in the Polling Timestamp field.
BE-32661
The swagger-UI component is upgraded. The file is located at the following path:
BE_HOME/apps/tibco/be/6.3/lib/ext/tpcl/swagger/swagger.zip/swagger-ui.js
BE-32660
In BE-TEA-Deployment, a space is missing in the deployed tra file
java.property.be.trace.roles when multiple log patterns are added.
BE-32652
There is an issue when the JSON flag is enabled for the HTTP input destination.
The content-type is set to "text/xml;charset=UTF-8" for replyEvent instead of
"application/json".
BE-32626
The catalog function Cluster.DataGrid.CacheLoadConceptsByExtIdByUri() loads the
concepts only from Ignite cache. It fails to load the concepts from the backing
store if not available in cache.
BE-32613
Concepts are not created properly when the JSON payload has null value fields.
BE-32612
Under the load,the agents stop after some time with an OutOfMemory exception.
To resolve this issue,made changes to avoid registration for changes to work list cache
for non-persistent Cache poller and applied similar changes for database based poller.
Use below proprty for scheduler engine
com.tibco.cep.runtime.scheduler.registerCacheEvents=false
BE-32578
When the cache size of an entity in Ignite reaches its limit, the eviction does
not trigger as expected. As a result, the data region encounters an Out of Memory
error and the cache node crashes.
BE-32577
There is a mismatch of entries while writing the bulk cache in Ignite cache and
the database. All the records are not written using the newID.
BE-32564
In TIBCO Administrator, the global variables defined in the project library are
not being overridden for BE 6.3.0 project.
BE-32559
HTTP uses the proxy that is enabled for all the requests at a time.
As a result, HTTP.sendRequest() times out.
BE-32555
BE 6.3.0 payload has different namespace prefix than that in BE 5.6.
In 6.3.0, the prefix starts with ns:1n instead of ns:0n.
A new property, be.serialization.inline.namespaces, is added.
The value of the property is set to true to declare the namespace at the level
where it is first referenced. It is not declared at the top of the
document unlike when the value of the property is set to false.
The default value of the property is false.
BE-32544
BE 6.3.0 payload has different namespace prefix than that in BE 5.6 for xsi:type.
Environment
All Supported Platforms
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.3.0 Hotfix-04 is available
Feedback
Yes
No
Powered by
