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.1/hotfix-01 to download the Hotfix.
- Alternatively, you can use the direct portal link to download 6.3.1 Hotfix-01. 
6.3.1-hf1 Direct Download Link
================================================================================

Closed Issues in 6.3.1_HF-001 (This Release)

=================================================================================

BE-33815
getRuleStats() method is not working properly for concurrent threads.

BE-33808
Prisma cloud scan has reported BusinessEvents vulnerability.

BE-33807
The inference agent needs to be restarted after some days because the heap memory reaches 
the maximum limit due to XPath cache, which is not limited in BusinessEvents version 6.3.0.
To handle this issue, a new property com.tibco.xpath.cache.size is introduced 
that sets the cache size.
The default value of the property is 1000.
When this property is set, the cache removes the oldest entries when the limit is reached. 
This avoids the increase in memory growth.

BE-33799
In BusinessEvents 6.3.1, at runtime, the BE agent uses XPath 2.00 although XPath 1.0 
is configured in the project. This is because the XPath version is not loaded from  
the pom.xml file for the migrated projects.

BE-33779
The InvocationCount is not properly showing the count for Rules triggered or Rules called.
The com.tibco.be.metric.resolution property decides the length of the slab with a 
default value of 5 seconds.
Delayed slab process multiple is set by default to 3.
So, after a maximum of 15 seconds the final count is available by default, 
otherwise 3 * metric resolution.

BE-33768
Apache Tomcat is upgraded to the version 9.0.98 to address the 
Apache Tomcat CVE-2024-52316 vulnerability.

BE-33766
Apache Tomcat is upgraded to the version 9.0.98 to address the 
Apache Tomcat CVE-2024-50379 vulnerability and CVE-2024-54677 vulnerability.

BE-33746
The Python CLI command removes the BE_HOME entries from the configured machine when 
upgrading the BE applications in a TEA-environment from version 6.2.x to 6.3.1.

BE-33712
When Kafka event is send with Event.sendEvent(), an exception occurs in the 
BusinessEvents log but it is not captured in the BusinessEvents Rule or RuleFunction.
This is now resolved. Event.ext.sendEventExt() or Event.Ext.sendEventImmediate() 
catalog function can be used instead of Event.sendEvent() to catch the exception  
in BusinessEvents Rule or RuleFunction. 

BE-33710
When multiple parents are created with the same extID in different RTCs in project 
with In Memory object management, the new parent is loaded in Rules without any error.
But, it is not saved in the working memory in PostRTC. 
If the parent is loaded in another RTC, then it loads the parent which is created 
first with the RTC Operations and for the newly created parent the RTC Operations 
is missing. 
This is resolved now as in such a scenario, a duplicate extid exception occurs.

BE-33694
When a project library associated with the project contains files with no names 
but only with an extension, the state machine artifacts are not opening in 
BusinessEvents Studio.

BE-33678
In TIBCO BusinessEvents, now TTL can be set in ActiveSpaces Store catalog function 
for BusinessEvents entity. To support this feature, an optional parameter, 
"varargs [long... ttl]" is added to the put() catalog function.

BE-33677
If the cache grouping is enabled using property "be.ignite.cache.grouping.enable" 
with persistence as Shared Nothing, then the cache agent is not able to start 
and encounters "data region mismatch error".

BE-33634
When events are sent to BusinessEvents with JSON payload, NPE and out of memory 
exceptions occur during payload serialization.

BE-33633
There is an issue when a machine with no internet access tries to install Maven plugin 
during TIBCO BusinessEvents installation. The installer log shows an error or the 
installer hangs forever during the installation.  
This is now resolved by bundling the required dependencies in the installer itself. 
So, the dependencies are installed from the bundled repository instead of downloading 
them from a remote Maven repository.

BE-33602
In BusinessEvents version 6.3.1, the application instance status is stuck to
"Starting Up" in Admin GUI even though the instance is running in the backend.

BE-33598
When the studio-tools command "-core importExistingProject" is used to import an  
existing project and that the project's pom.xml refers to missing dependencies, 
a NullPointerException exception occurs.

BE-33595
A catalog function, Event.Ext.sendEventImmediate() is provided to ensure that 
a message is received and processed by the Kafka server when a Kafka message 
is published.
This catalog function returns result only when syncSender is true otherwise, 
the result is null. 
When the properties, kafka_message_offset and kafka_message_partition are added 
as Event properties, the catalog function returns the offset of the message or 
the published event with the returned offset and also returns the partition.

BE-33574
An error occurs with the Catalog function, Store.executeUpdate() and ActiveSpaces 4.x store, 
when executing Update, Insert, or Delete SQL queries. This has been resolved now.
The support has been added for  Update, Insert, or Delete SQL queries in 
Store.executeUpdate()  with ActiveSpaces 4.x store.

BE-33558
The CacheServer is not able to join the cluster because Ignite cluster 
allocates connections with IPs of the backup network To resolve this issue, 
the following two properties are set:
1. be.ignite.cluster.discovery.localhost - It is used to set the discovery localhost. 
   The value of this property is the IP address of the host machine and  
   the property is used for Ignite as the cluster provider.
2. be.engine.hostaddress - It is used to set the communication. 
   The value of this property is the local IP address for communication.

BE-33540
On startup, after the BusinessEvents agent is connected to a Pulsar channel, 
the agent creates a topic in default tenant and namespace to check if a Broker is running. 
This causes a startup error when connecting to a non-standalone Pulsar server.

BE-33347
When a project is migrated from BusinessEvents 5.2.0 to higher versions, below  
validation error is displayed:
[BW6] The referenced schema component has an error: Unresolved reference in Schema
[BW6] Unexpected output, no such element in the current context
There is an issue when multiple WSDL files are used and the WSDL files contain 
xs:import elements with no schemaLocation.
This is now resolved by adding a schemaLocation="./" attribute in each of the 
xs:import statements.
Also, envelope.xsd file is added in the schemas.

All Supported Platforms

Please refer to attached hotfix readme file for installation instructions, affected files and list of fixes in this release.

TIBCO BusinessEvents Enterprise Edition 6.3.1 Hotfix-01 is available.

hotfix readme