Contents
This topic lists the significant changes in the StreamBase 3.1.x release series.
StreamBase 3.1.16 adds the following features:
Two subcommands were added to the sbadmin command:
-
killConnection
client-idThis tells the server to close (kill) the connection associated with the specified
client-id. Client-ids can be determined with the listConnection command. -
killAllConnections
This command tells the server to close (kill) all connections currently attached to the server.
In both cases, clients receive notification that their connection has been closed in the same way they would be notified that the server has shut down.
To aid in the diagnosis of client connection problems, the listConnections command now provides a count of the number of tuples enqueued and dequeued per client. You can use these counts to determine that clients have become inactive.
A feature was added to the server to close connections that are determined to be idle. This feature is controlled by two new parameters in the configuration file:
-
idle-enqueue-client-timeout-ms
-
idle-dequeue-client-timeout-ms
An idle enqueue client is defined as a client that enqueued at least one
tuple, and has been idle for at least idle-enqueue-client-timeout-ms
milliseconds.
An idle dequeue client is defined as one that subscribed to at least one
stream at some point in the past, and has been idle for at least idle-dequeue-client-timeout-ms
milliseconds.
Clients that have both enqueued and subscribed are subject to both
settings. The server checks clients every idle-client-check-interval-ms. The actual
point at which a client is disconnected is approximately modulo idle-client-check-interval-ms. Values are
in milliseconds. Values greater than zero enable this feature; the default
is disabled.
In addition, a configuration parameter was added to control the interval at
which the server checks for idle connections: idle-client-check-interval-ms.
StreamBase 3.1.15 was a maintenance release. For more information, see the Resolved Limitations section of the Release Notes.
StreamBase 3.1.13 adds an enhancement that allows you to set a
limit on the maximum number of client connections. This can be used to
avoid resource contention during peak times. The feature is documented in
the StreamBase Server sb.sbconf
configuration file.
StreamBase 3.1.11 fixed a number of product limitations. For more information, see the Resolved Limitations section of the Release Notes.
StreamBase 3.1.7 was a maintenance release. See the Release Notes for resolved limitations.
StreamBase 3.1.5 fixed a number of product limitations. For more information, see the Resolved Limitations section of the Release Notes.
StreamBase 3.1.0 introduced the following new product features and important changes:
-
The .NET Client API, available on Windows only, can be used to program StreamBase client applications using the Microsoft .NET platform, in C#, Visual Basic, or C++. There are also new samples demonstrating .NET client applications. For more information, refer to the Creating .NET Clients topic.
-
Demo perspective. A new StreamBase Studio Demo perspective provides views and tools for the first-time user, demonstrating important StreamBase capabilities. You can open the Demo perspective directly from the Welcome page when you first open StreamBase Studio, or at any time by clicking → , then selecting
-
StreamBase is now available in two Editions:
-
Enterprise Edition: All product features are supported.
-
Developer Edition: provides most features, with the exceptions noted in the Comparison of StreamBase Editions topic.
-
-
An Expression Quick Reference in the Properties View provides additional help creating expressions in StreamBase operators.
-
StreamBase for Windows now includes an embedded JDK, which provides all the Java components needed to run StreamBase Studio. It is no longer necessary to install a JDK separately on Windows. For details, refer to the Supported Configurations topic in the Installation Guide.