These are the release notes for TIBCO® Streaming 11.0.0. Please check here for any additional details regarding upgrades from previous versions, best practices, and useful tips for specific situations, use cases, and so on.
TIBCO® Streaming 11.0.0 adds the following updates and new features:
- Installation Location Changes
TIBCO® Streaming and TIBCO® Data Streams now install in default locations that include their product codes,
sfire-sfdsrespectively. For this product, the default install locations are
/opt/tibco/str/11.0on Linux and
tar.gzfiles from the
unpackaction of the
archive-bininstallers for these products and the StreamBase High Performance Fix Pack are now rooted at the product install root with no fixed prefix, so any destination you choose no longer must contain
- TIBCO® Streaming Now Supports Windows Server 2019
Windows Server 2019 is now a supported operating system for development and deployment.
- TIBCO® Streaming Now Supports AlmaLinux OS 8
AlmaLinux is now a supported operating system for deployment, and is the recommended migration path for applications deployed on CentOS Linux 8.
- TIBCO® Streaming Now Bundles Java 11.0.14
On all supported operating systems, the TIBCO Streaming installation kit provides the runtime components of Oracle JDK version 11.0.14 in a subdirectory of the StreamBase installation directory, for private use to run StreamBase program fragments and applications from within StreamBase Studio. As before, StreamBase detects and prefers a system-installed JDK, and uses the bundled JDK as a fallback. See further details about the JDK requirements of this release in the JDK entry of the Supported Configurations page.
- Studio Now Built on Eclipse 4.21
StreamBase Studio and StreamBase Manager are now based on Eclipse 4.21.
As with every major release, TIBCO strongly recommends using Copy projects into workspace option.> to import your projects from previous releases into a new, unused Studio 11.0 workspace. Be sure to use the
Once imported and updated to 11.0 format, do not reopen a 11.0 project with an earlier release of Studio.
- Studio Now has Docker Tooling Bundled
Eclipse Docker Tooling 5.4 version has been bundled with the StreamBase 11.0 version. This allows management of Docker images and Containers from within Studio. For more details on this open source software refer to Linux Tools Project/Docker Tooling/User Guide.
- TIBCO® Streaming Now Supports Logback 1.2.8 and Higher Versions
Logback 1.2.8 and higher is now a supported logging framework.
- LiveView Cluster-Wide Alerting is Now More Robust in the Face of Master Failure
Cluster-wide alerting is now more robust in ensuring alerts are not missed when an alert master fails. See the Cluster-wide Alert Configuration page for more information.
- Added Postgres Support for LiveView Metadata
Postgres 12.2 is now supported for LiveView Metadata server to store its metadata. For supported version details, refer to Supported Configurations.
- All the LiveView Adapters Now have Two New Features Available
The LiveView adapters now have two new features available. The first feature supports 'Runtime URLs', meaning you can set the LiveView URL any time during the life of the server. You can also change the LiveView URL to connect to at any time.
The second feature provides the option to use a 'compressed' LiveView connection. This can be very helpful for connections transferring large amounts of data and which have limited or metered bandwidth.
- The LiveView Client Now has Enhancements
The LiveView client has been modernized with auto completion and command history.
- A New LiveView Python Client
The LiveView Python client lets you query, publish, and monitor data from a LiveView server with Python.
- New Metrics Published for LiveView
The LiveView now publishes 7 new metrics. All existing LiveView metrics are now deprecated.
- TIBCO® Streaming Now Comes With PyDev Feature
PyDev is now a supported feature, which can help create python projects.
- Data Science Operators Can Now Be Accessed Using Palette Drawer
Data Science operators were accessible through Operators menu within the Insert tab. They can now be accessed using the palette drawer.
- The macOS Studio and Manager Bundle IDs Are Changed
Starting with this release, macOS Studio ID has changed from
com.streambase.sb.studio.productand Manager Bundle ID has changed from
com.tibco.ep.sbas per Apple guidelines. Check all default installation directories.
- Support Wizard Now Captures Thread Dump
Starting with this release, StreamBase Studio's Support wizard (in the Help menu) can now also capture and save a thread dump of the Studio JVM to assist in troubleshooting.
- Target Router Path Field Added to The Distributed Router Operator
The Target Router Path field has been added to the Distributed Router Operator to specify the fully-qualified path of the Distributed Router to which tuples are routed. This field is optional. The default value is the path of the Distributed Router Operator.
- Decision Table Operator Field Now Allows You to Enable Control And Status Ports
The Decision Table operator field now allows you to enable Control and Status ports so that they can be incorporated into the EventFlow. The
Enable Control Portand
Enable Status Portproperties can be used to specify if these ports should be enabled.
- TIBCO® Streaming Now Comes With Following New Adapters
RTPP (Real Time Payment Protocol) adapter: See the RTPP Adapter page for more information.
TIBCO FTL Control adapter: This adapter is used to control the connection to an FTL Realm server and to manage FTL groups within that server. This will help applications to start or stop the subscription from FTL Realm server while keeping the connection. See the TIBCO FTL Control Operator page for more information.
Metrics Publishing Adapter: This adapter allows users to define and publish labeled metrics to the Streaming Metrics API. See the Metric Publish Adapter page for more information.
- New Warm Start-Up Feature Added to TIBCO® Streaming
The Warm Start-Up feature allows engines running EventFlow fragments to be restarted without recompiling the fragment's EventFlow source code (e.g. sbapp files). Warm Start-Up is disabled by default and needs to be enabled in a StreamBase engine configuration by setting the "recompileBehavior" field to "REUSE" in the "streambase" section of the configuration.
- Parallel Region Queue Configuration Settings Added In Studio
This release comes with new parallel region queue config settings in Studio that can be defined per-operator. These settings can already be defined globally in the HOCON configuration but this new feature allows each operator to have its own settings.
- Added HTTP/2 Support In Streaming Web Server
Starting with release 11.0.0, TIBCO® Streaming Web Server supports HTTP/2 when SSL is configured.
- New StreamBase LDAP Auth Configuration Wizard
A new StreamBase LDAP Auth Configuration Wizard is added in Studio, that assists users with LDAP configuration file generation. This wizard validates entered information with provided server and generates the config file based on this information. You can access this wizard by selecting > > > or right-click on a project and selecting > > .
- Smaller Memory Footprint For Cloud Use
Starting from this release, the shared memory usage by a node for non-user data has been significantly reduced. Startup shared memory usage, in a 512 megabyte node, has dropped from 184 megabytes (36%) to 44 megabytes (8%).
- Remote Administration Over SSH To/From Windows Machines And From/To Linux Or Mac Machines Is Now Supported
Starting from this release, remote administration is supported from any client OS (Windows, Linux, Mac) to any server OS.
- The ep-maven-plugin Will Consider Eventflow Sources From src/test/eventflows
Starting with release 11.0.0, ep-maven-plugin will now consider eventflow sources from src/test/eventflows. These will be built and be available for local maven module testing. They will not get shipped in the eventflow fragment archive.
- Generated Code Refactoring Default Enabled
Starting with release 11.0.0, code refactoring is always enabled to avoid exceeding Java limits for generated module code.
- MQTT LV Recovery Sample is Added
Starting with release 11.0.0, an MQTT LV recovery sample is added. The recovery sample demonstrates elastic scaling with peer-based recovery for message buses that don't provide storage message ids. Both 'perfect' and 'imperfect' recovery is discussed.
- LiveView .NET driver now supports Linux
Starting with release 11.0.0, as part of this migration, consuming events in WPF events are now no longer automatically threaded and need to be done by users. The LiveView .NET adapter now packages the StreamBase lite DLL, compared to the previous full StreamBase DLL. LiveView works with both DLL versions.
The lite DLL has the following changes:
It works in .NET core/netstandard2.0.
It only supports tuple and actions.
It reduces date-time parsing options to ISO standard formats.
- Connect LiveView Server with TIBCO® Cloud Data Streams (TCDS)
The TCDS provides LiveView server URLs. Follow the steps to get the TCDS stream connectivity URL:
Login to TCDS.
Click on the Connection Info.
Copy the URL in the dialog box.
Get the authentication token from here.
- Artifact Management Server (AMS) Does Not Any Have Default Artifact Encoding
The AMS client adapter always forced the content field to have an encoding of ENCODING_ZIP_BASE64 when sent. Starting in 11.0, the content field will have a default encoding of NONE. If zip compression is desired, the encoding field should be set to ENCODING_ZIP_BASE64.
This release includes the following changes in functionality:
- No plain text READMEs for samples with HTML READMEs.
Starting with TIBCO Streaming 11.0.0, samples with HTML READMEs no longer include a plain text README. Studio will pick the appropriate format for any sample.
- C++ Client API for Microsoft Visual Studio 2012 removed
Starting with TIBCO Streaming 11.0.0, support for using the C++ client API from Microsoft Visual Studio 2012 has been removed. Programs that use the C++ client API in Windows should use Microsoft Visual Stuio 2019.
- The eFTL LV Recovery Sample now Uses the New eFTL 6.5.0 Storage Message Id
The eFTL LV recovery sample is updated to use the new eFTL 6.5.0 storage message id. This sample demonstrates elastic scaling based on peer-based recovery. The delayed recovery operator is now improved. The previous delayed recovery eFTL sample is removed. The new MQTT sample demonstrates delayed peer recovery for message buses that don't have message ids.
The following features are deprecated or removed as of Streaming 11.0.0.
- StreamSQL Deprecated
Stream SQL is deprecated and will be removed in a future release.
- CentOS Linux 7 and 8 Are Deprecated
Support for CentOS Linux 7 and 8 is deprecated as of Streaming 11. Because Red Hat has declared that CentOS Linux has reached end of life, there will be no security updates. Container or machine builds that relied on CentOS package repositories, such as Docker or Ansible, will not work and must be migrated to other compatible Streaming-supported Linux distributions.
For Streaming, the options are Red Hat Enterprise Linux, Oracle Linux, and AlmaLinux. AlmaLinux is the recommended option for container builds like Docker; use the image name
- RHEL 7, Oracle Linux 7 Deprecated
Support for Red Hat Enterprise Linux 7 and Oracle Linux 7 is deprecated and is expected to be removed in a future release.
- Windows Releases Before 2016 Deprecated
Support for Windows releases before 2016 is deprecated. Among currently supported Windows releases, Windows 7, 8.1, and Windows Server 2012 are thus deprecated. In Windows 10, support for builds before 1607 is deprecated.
- Microsoft Visual Studio 2013, 2015, and 2017 Deprecated for .NET Development
Use of these versions of Visual Studio for Streaming .NET client and operator development is deprecated and expected to be removed in a future release. Migration to Visual Studio 2019 is recommended.
- JDBC No Longer Supports Oracle 11g, Microsoft SQL Server 2008, and all versions of Vertica
JDBC support for Oracle 11g, Microsoft SQL Server 2008, and all versions of Vertica are removed in 11.0.0.
- Legacy HA Support Removed
The deprecated legacy HA support is removed in 11.0.0. Operators using the leadership property now report a typecheck error. Upgrade the module to remove this property by making a simple change in the module (e.g., operator name change) and save the module.
- Deprecated Support for Interfaces in a Resources Directory
Loading EventFlow from the resources directory is deprecated and will be removed in a future release. Eventflow files should all be located into
/src/test/eventflow. Use a qualified module name to reference the module in module references or extension points.
- Tuple Serialization Deprecated
With this release, serialization of the com.streambase.sb.Tuple abstract class is deprecated.
- Manually Enabling of Generated Code Refactoring is Deprecated
Refactoring of codes is enabled by default. Users can not use system properties to force the failed codes to be refactored to work around the Java limits.
This release contains the following migration and compatibility notes.
- Cross-Version Compatibility of Applications/Fragments
This release provides compatibility with application and fragment archives built with these versions:
Minimum version 10.5.0
Maximum version 11.0.0
This section describes known limitations as of the current release of TIBCO® Streaming. Each item includes a tracking number, description, and workarounds when possible.
|SB-51772||Studio should process-resources as part of typecheck construction.|
As of 11.0, Studio typechecking expects to find project resources on the Maven class path. This requires that projects, and their dependencies, have been built already, which will be the case when auto-build is enabled. If auto-build is not enabled, the build will fail, complaining that resources are missing.
Simply build the project(s) by hand manually, which may not be obvious to the user.
|SB-51201||Alibaba Fastjson Mitigation of Vulnerability CWE-502|
Some Streaming 11 adapters include a version of Alibaba Fastjson with a vulnerability classified as CWE-502. In Streaming 11 and later, all Fastjson parser instances are put into a safe mode that mitigates the vulnerability. The safe mode turns off the Fastjson feature that is vulnerable to such attacks. However, the vulnerability will still be flagged in tools that report dependency vulnerabilities. The following adapters are affected:
|Workaround||You can suppress the vulnerability in such tools as the OWASP Dependency Check Maven plugin.|
|SB-50988||Attempting to install TIBCO Streaming to a custom install directory whose length is more than 14 characters is likely to fail.|
Because of Windows limitations and features included in Studio, attempting to install Streaming to a custom install directory (MSI property SBINSTALLDIR) whose length is more than 14 characters is likely to fail.
|Workaround||Use the default install path, or try a shorter custom install directory.|
|SB-49471||The epdev offline maven command shows benign errors.|
Running the epdev offline maven command can show a number or Maven errors. However, the process does complete and work as expected. The display of these errors is expected to be corrected in an upcoming release.
|SB-49208||Project names with underlines cause problems for application projects with Docker and Kubernetes or Helm support.|
Studio-generated StreamBase Application projects that elect the Docker and Kubernetes options generate a Docker image without errors, but fail to deploy in Docker.
|Workaround||Start over with a new project name without underlines.|
This page describes the known limitations in the current release of TIBCO LiveView™. Each item includes a tracking number, description, and whenever possible, one or more workarounds.
|ClusterAlert||Cluster-wide Alert Group Restriction for Heterogeneous Clusters|
|Description||Nodes with only EventFlow engines in LiveView clusters must be in their own alert groups.|
|Workaround||See this page for cluster-wide alerting guidelines.|
|Description||New LiveView Fragment projects are created by default with a dependency on the
|Workaround||In both cases, you must both remove the
The correct way to create a new LiveView project without LiveView Web support is to change the
|SB‑45720||Failure to independently run or debug EventFlow modules in LiveView projects in 10.4.0 through 10.4.2.|
|Description||Many LiveView projects have StreamBase EventFlow modules that provide functionality such as publishers or transformers of data. In releases 10.4.0, 10.4.1, and 10.4.2, right-clicking such modules and selecting> (or ) to run or debug the module independent of the enclosing LiveView project resulted in an error. This feature was restored in release 10.4.3. Note that this limitation did not prevent running the project as a LiveView fragment with all EventFlow modules working; the limitation was only on running the EventFlow modules by themselves.|
|Workaround||If you are using one of the affected releases, you can;
|SB‑44494||Metadata store restriction for clusters containing LiveView and StreamBase fragments.|
|Description||The transactional memory metadata store type is only supported on
|Workaround||Use either the JDBC or H2 metadata store type when your cluster contains both LiveView and StreamBase fragments.|
|CQS-4800||Row level security — authentication not performed on results of already-registered queries and query-based alerts.|
|Description||Row level security (RLS) authentication and authorization is performed at the time when new query-based alerts and queries are registered with the LiveView server. LiveView does not perform authentication on the results of already-registered queries and query-based alerts; in order to get the expected results based on RLS authentication, you must re-register the queries with the server.|
|CQS-4748||Do not use the
|CQS-4641||Issuing queries with literal non-printing characters is not supported in query strings.|
|Description||Query strings with literal non-printing characters can cause issues. Non-printing characters are those below 0x20, excepting tab, carriage return, and line feed. Note that tables and query result sets are free to have any characters as values.|
|Workaround||Instead use StreamBase Unicode escape sequences, which looks like
|CQS-3855||Remote data source tables with sole primary key
|Description||When querying a remote data source's tables, all LiveView clients fail to open any remote table that uses a single primary
key named CQSInternalID.
This issue affects all LiveView clients, including TIBCO LiveView Desktop, TIBCO LiveView Web, the lv-client command line utility, and any custom client written using LiveView Client APIs.
The issue occurs when querying any remote data source, including: TIBCO StreamBase Query Tables, other LiveView servers, JDBC databases, TIBCO ActiveSpaces tables, and custom table providers.
|Workaround||You can use one of the following suggestions to enumerate the remote tables that you must avoid. 1. If your client can sort
its list of available remote tables, sort it by the Indexes column to isolate the tables that have only CQSInternalID as their
primary key. 2. Use the following query to determine the remote tables to avoid opening:
select * from LVTables where Indices=='CQSInternalID'
This section provides a list of errors corrected in release 11.0.0 of TIBCO® Streaming.
|Fixed in 11.0.0|
|TIBCO StreamBase® 11.0.0 incorporates all fixes resolved in the release 10.0 series through 10.6.2.|
|SB-31500||Earlier, there was no support for remote administration of node life-cycle on the Windows platform. Remote administration over SSH to/from Windows machines and from/to Linux or Mac machines is now supported.|
|SB-32314||The Distributed Router operator experienced errors while dispatching requests to remote nodes due to a race condition during startup of a remote node. This has been fixed.|
|SB-47954||When a new version of an artifact is deployed to an operator running in a parallel region or with multiplicity, all instances of the operator are updated with the new artifact. Previously the artifact deployment would fail with an "operator not found" error message.|
|SB-49861||StreamBase Studio would sometimes trigger a full workspace rebuild prior to a launch. This issue is fixed by ensuring that only what needs to be rebuilt (if anything) is built before a fragment launches.|
|SB-49982||Typechecking would report errors if resources were located in JAR files or non-StreamBase projects. This issue is resolved by adding all dependencies to the operator resource classpath. Now Studio typechecking can search for resources in all locations on the project's classpath.|
|SB-50508||The Decision Table operator's decision table would incorrectly fail to load with an error if the decision table contained a condition or action column of type "list of tuple". This has been fixed.|