Striim 3.9.4 / 3.9.5 documentation

What's new in Striim 3.9.4 and 3.9.5

Striim 3.9.5 includes only performance improvements, security updates, and bug fixes. See the Striim 3.9.5 release notes for a list of fixed customer-reported bugs.

The following improvements were new in Striim 3.9.4.

Application development

The Apps page can organize applications into user-defined groups.

Sources and targets

Change data capture


Administration and monitoring

  • When database connections to the metadata repository and persisted WActionStores are temporarily unavailable due to network problems or other issues, Striim will retry them (see Changing internal database connection retry settings).

  • When you recover an application, its status will be RECOVERING_SOURCES until recovery is complete, after which it change to RUNNING (see Recovering applications).

  • MON output for OracleReader sources includes additional information including the five oldest open transactions, the five transactions with the largest number of operations, the total number of operations in the cache, and recovery status (see Using the MON command).

  • When an application containing a BigQueryWriter, CosmosDBWriter, DatabaseWriter, HazelcastWriter, HBaseWriter, KinesisWriter, KuduWriter, or SpannerWriter target is stopped, any remaining data in the batch policy buffer is discarded. If recovery is enabled for the application (see Recovering applications), the discarded events will be re-read, so after recovery there will be no missing events.

Installation and configuration

  • When Deploying Striim using an Azure Marketplace Solution) you may use an existing VNET.

  • The Forwarding Agent can be configured to work across a NAT connection, commonly required when Striim is running in the cloud. See Configuring the Forwarding Agent.

  • The internal Derby instance is version

  • The internal Elasticsearch cluster is version 5.6.4.

  • The internal Kafka cluster is version

  • The bundled MapR client is version 5.1.

  • The bundled PostgreSQL JDBC driver is 42.2.2.