Striim® 3.9.3 release notes


For evaluating Striim:

A production environment will require more memory and disk space.

Java SE JDK 7 and OpenJDK 7 are no longer supported. You must upgrade to version 8 before installing or upgrading to Striim 3.8 or later.

Using Striim with MySQL requires the MySQL Connector/J JDBC driver 5.1.46. If you are using an earlier version, you must upgrade it. See "Installing the MySQL JDBC driver" in the Installation and Configuration Guide.

Striim 3.9 has been verified with Oracle JDBC driver ojdbc8.jar. If you are using an earlier version, remove it and install ojdbc8.jar. See "Installing the Oracle JDBC driver" in the Installation and Configuration Guide.

Oracle has ended patch fixes for Oracle 11g and You must upgrade to 11g (or 12c to use OracleReader with this release.

The web client has been tested on Chrome. Other web browsers should work, but if you encounter bugs, try Chrome.

Changes that may require modification of your TQL code, workflow, or environment


As of 3.9.0, the default value of Column Delimiter has changed to | (pipe). This will cause no problems with existing applications unless the data being written contains the pipe character, in which case you will need to choose a different delimiter.


In previous releases, a flow that was deployed to a group with more than one agent was always deployed to all agents in the group, even when ON ONE was specified. In 3.8.6, this bug was fixed, and deployment to agents will be ON ONE or ON ALL as specified in the DEPLOY command.

If you are upgrading to 3.9.2 from a release earlier than 3.8.6, after the upgrade is complete, any applications with recovery enabled that were deployed to groups with more than one agent must be deployed ON ALL in order to pick up from the recovery checkpoint correctly.

Known issues

The following issues have been identified but not yet fixed as of this release. Additional known issues are mentioned in the relevant topics in the documentation.

HTTPReader is missing the Parser menu in the UI (DEV-1854)

Workaround: Use the console or import TQL.

Objects with the same name do not appear in UI (DEV-3172)

TQL allows you to use the same name for more than one object in the same application provided that the objects are all of different types (for example, source, stream, and target), but the UI will not display these objects.

Workaround: Rename the objects or edit using the console.

Can not rename object in flow editor (DEV-3556)

After saving an object in the flow editor, its name cannot be changed.

Workaround: Drop the object and recreate it, or modify it using console commands.

MAP settings are not exposed in the UI (DEV-4138)

The MAP clause of CREATE SOURCE ... OUTPUT TO is not exposed in the UI, though it can be created with the App Wizard.

Workaround: in the console, use DESCRIBE to view settings, ALTER to change them.

WActionStore silently discards events with null value for event type key (DEV-5599)

Creating a source using HTTPReader and DSVParser fails with error (DEV-5916)

Workaround: Have the sender include type=dsv in the URI. For example:

curl -X POST ""...

OracleReader DateTime values do not include milliseconds (DEV-5987)

Dashboard queries not dropped with the dashboard or overwritten on import (DEV-6068)

When you drop a dashboard, its queries are not dropped. If you drop and re-import a dashboard, the queries in the JSON file do not overwrite those already in Striim.

Workaround: drop the namespace.

FileReader filesequencer property not exposed in UI (DEV-6604)

Workaround: Use the console or import TQL.

SORTER objects do not appear in the UI (DEV-8142)

DatabaseWriter shows no error in UI when MySQL credentials are incorrect (DEV-8933)

If your DatabaseWriter Username or Password values are correct, you will see no error in the UI but no data will be written to MySQL. You will see errors in webaction.server.log regarding DatabaseWriter containing Failure in Processing query and command denied to user.

DatabaseWriter needs separate checkpoint table for each node when deployed on multiple nodes (DEV-11305)

Flow Designer is unresponsive when a type has a very large number of fields (DEV-11898)

Workaround: Use the console.

GRANT command wildcard does not work for objects (DEV-12146)

Commands such as GRANT ALL ON * *.* TO ROLE ... will fail.

Workaround: leave out the object element, for example, GRANT ALL ON *.* TO ROLE ....

Derby uses all available disk space and Striim crashes (DEV-15082)

When Striim is processing very large amounts of data at high velocity, Derby may fail to reclaim the unused space in the metadata repository, resulting in it eventually filling all available disk space and crashing. In this situation, Striim will crash and restart will fail.

Workaround: Use PostgresSQL or Oracle to host the metadata repository.

As a short-term workaround for Derby, use the following command to compress the metadata repository tables:

striim/bin/ -A compressDb

This uses a lot of Derby resources, so it should be performed when Striim is not busy.