TIBCO BusinessEvents Standard Edition 5.2.2 Hotfix 04 is available for download.
Article ID: KB0103197
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | - |
| Not Applicable | - |
Description
Description:
You can download this HotFix from the TIBCO Product Support ftp server, https://mft.tibco.com . You will need to provide your eSupport username and password to access the server.
Once you have successfully logged into the server, go to /AvailableDownloads/BusinessEvents/StandardEdition/5.2.2/hotfix-04 to download the fix appropriate for your edition and operating system platform.
================================================================================
Closed Issues in 5.2.2_HF-004 (This Release)
BE-24096
In TIBCO BusinessEvents WebStudio, the domain model list, in the business rule,
displayed the value which was removed earlier.
BE-24084
In TIBCO BusinessEvents WebStudio, checking null for the DateTime fields, in
rule templates, was giving a validation error.
BE-24078
There was no option to increase the default allocated TERR engine memory when it
is started with TIBCO BusinessEvents engine.
Now a new catalog function setJavaOptions is added to update the JVM settings
for the TERR engine:
public void setJavaOptions(java.lang.String javaOptions)
BE-24066
In certain situations, the Cluster Scheduler hanged when a Cache Server crashed.
Now a timeout has been introduced so that the Scheduler will not wait forever in
this situation and will subsequently fire at the configured scheduler interval.
The property to enable this timeout is:
be.engine.cluster.as.invocation.timeout=<timeout in millis>
BE-24065
The state timeout records were not deleted after the concept deletion when
timeouts were configured for the composite state.
BE-24042
The database connections in the pool were closed instead of freeing the
connection back to the pool.
BE-24041
There was no way to get the business rules details.
This was fixed by adding the Engine.ruleName function to return the currently
executing rule details.
BE-23942
The be-jdbcdeploy utility was generating wrong migration scripts.
BE-23910
All active worker threads were not complete when the inference agent was
shutdown.
This was fixed by adding two new properties:
- com.tibco.cep.runtime.threadpool.shutdown.timeout.seconds - Specifies time
(in seconds) to wait for the worker thread to complete before shutdown.
- be.engine.cluster.as.shutdown.wait.millis - Specifies time (in milliseconds)
to wait for the ActiveSpaces for the worker thread to complete before
shutdown.
================================================================================
Environment
All Supported Platforms
Issue/Introduction
TIBCO BusinessEvents Standard Edition 5.2.2 Hotfix 04 is available for download.
Feedback
Yes
No
Powered by
