Before you install StreamBase:
-
Read this Release Notes document.
-
Confirm that your target system matches the hardware and software requirements discussed on Supported Configurations.
-
Read the Installation Guide.
-
For a summary of what's new in this release, see New and Noteworthy.
-
If you are new to StreamBase, read Getting Started after installation.
-
See the documentation home page to begin exploring the StreamBase documentation. The StreamBase documentation set is available as part of your StreamBase installation in several ways:
-
From the installed file system, open the documentation home page in a web browser. The default locations are:
UNIX /opt/streambase/doc/index.html 32-bit Windows C:\Program Files\StreamBase Systems\StreamBase
.n.m\doc\index.html 64-bit Windows C:\Program Files (x86)\StreamBase Systems\StreamBase.n.m\doc\index.html -
In StreamBase Studio, select → from the menu.
-
On Windows, open → → → →
-
On UNIX at a terminal window's command prompt, run
sbhelp &. -
If you were provided an installation DVD-ROM, open
doc/index.htmlin a web browser.
-
Contact Information contains information about available support options. You can send us e-mail or get information from your StreamBase Systems representative about our support portal.
| Fixed in 7.3.3 | |
|---|---|
| Number | Resolution |
| Release 7.3.3 incorporates all fixes resolved in the release 7.2 series through 7.2.11, in the release 7.1 series through release 7.1.12, and in the release 6.6 series through release 6.6.24. See Limitations Resolved in 7.2.x, Limitations Resolved in 7.1.x, and Limitations Resolved in 6.6.x for details. | |
| SB‑24210 |
Version 7.3.3 provides a more comprehensive fix for the issue of possible
data corruption from concurrent calls from separate Java threads to
sendOutputAsync on the same operator than the
solution provided in 7.3.2.
|
| Fixed in 7.3.2 | |
|---|---|
| Number | Resolution |
| Release 7.3.2 incorporates all fixes resolved in the release 7.2 series through 7.2.11, in the release 7.1 series through release 7.1.12, and in the release 6.6 series through release 6.6.23. See Limitations Resolved in 7.2.x, Limitations Resolved in 7.1.x, and Limitations Resolved in 6.6.x for details. | |
| SB‑24368 | Using IN for a case-sensitive index would trigger a table scan. This was changed. |
| SB‑24210 |
In previous versions of 7.3, concurrent calls from separate Java threads to
sendOutputAsync on the same operator could
lead to duplicate data values and data loss. This has been corrected.
|
| SB‑24161 | In previous releases, Join operator Output Settings with no prefixes were serialized incorrectly. Upon being reloaded, they were reordered and given default prefixes such as "input2_". Now empty prefixes are preserved and outputs are maintained in their original order. |
| SB‑24077 |
You can now define Eclipse Classpath Variables on the sbbundle command line. For more information, see What Was New in StreamBase
7.3.2
|
| SB‑24015 | If you added or removed fields from a schema for a data construct (such as a query table), the identity of the primary key would be lost, even if the modified field were unrelated to the primary index. Now you can modify such a schema without affecting the primary index. |
| SB‑23958 |
In previous releases, the predicate dimension fields expression for a
control port to open, emit from, or close had to be a fully qualified field
name (specified in dot notation, such as input1.cost). In StreamBase 7.3.1 and later, you can omit
the qualifier and use just the field name in the expression.
|
| SB‑23907 | After hitting a breakpoint on an input stream's outgoing arc, the Variables view in the StreamBase Studio Debugger would be blank. The problem was that the line representing that arc in the Debug view was not automatically selected when the breakpoint was hit. This has been corrected. |
| SB‑23722 | The number of instances of a module can be configured with an expression, and the expression will be evaluated at application startup. |
| SB‑22171 |
The strftime function now supports formatting
instructions %e, %k and %l, which output a
leading space instead of a leading zero for one-digit values.
|
| Fixed in 7.3.1 | |
|---|---|
| Number | Resolution |
| Release 7.3.1 incorporates all fixes resolved in the release 7.2 series through 7.2.10, in the release 7.1 series through release 7.1.12, and in the release 6.6 series through release 6.6.23. See Limitations Resolved in 7.2.x, Limitations Resolved in 7.1.x, and Limitations Resolved in 6.6.x for details. | |
| SB‑23933 |
If the Java source folder for custom Java operators, adapters, or functions
was anything other than java-bin under a
Studio project root (as could happen when using Maven to manage the Java
files), then Studio was unable to load that operator, adapter, or function
during typechecking of the project. Studio would report that the class
could not be found. This was corrected.
|
| SB‑23930 | The XML-to-Tuple operator can populate tuple fields with XML attributes in one of two ways: (1) By using the special _ATTRIBUTES meta field, or (2) by creating a subfield with a name that matches the attribute name. The second technique was not working if the subfield's parent field was of type list<tuple>. This was fixed. |
| SB‑23912 | In previous releases, the expression language's strptime() function incorrectly interpreted time strings that specified the noon hour as a timestamp 12 hours later. This was corrected. |
| SB‑23905 | The upgrade to Eclipse 3.8 in StreamBase release 7.3 caused a regression that prevented the opening of Query Tables and dynamic variables in the Variables view of the EventFlow Debugger. The cause was identified and corrected. |
| SB‑23879 |
Two Unicode-handling bugs in StreamBase Studio were corrected. Even if
Studio was configured to be Unicode ready with the streambase.tuple-charset=UTF-8 setting, (1) the
Copy as ... options in the context menu of
the Application Output view would not correctly copy Unicode characters,
and (2) the New StreamBase Unit Test wizard could garble Unicode characters
in Java files created from the Application Output view.
|
| SB‑23726 | On Linux systems, an unpredictability in classpath loading order was resulting in a NullPointerException for the Alpha Trading Systems adapters. The classpath loading order was updated to assure a predictable order. |
| SB‑23608 | When enqueuing with a C++ or Python client and specifying an input stream by stream name in the default container without its qualifying path (that is, "in" rather than "default.in"), a performance penalty was incurred because the client would repeatedly query the server for stream properties rather than using the client side cache. The workarounds were to manually cache the StreamProperties object or use full stream path name. This limitation was lifted and the workarounds are no longer necessary. |
| SB‑23485 | In previous releases, an xi:include in a server configuration file could cause an error that referred to the Boost libraries when starting StreamBase Server as a Windows service. The cause was identified and corrected. |
| Fixed in 7.3.0 | |
|---|---|
| Number | Resolution |
| Release 7.3.0 incorporates all fixes resolved in the release 7.2 series through 7.2.8, in the release 7.1 series through release 7.1.11, and in the release 6.6 series through release 6.6.22. See Limitations Resolved in 7.2.x, Limitations Resolved in 7.1.x, and Limitations Resolved in 6.6.x for details. | |
| SB‑23739 | A busy loop that caused a thread in the IBM WebSphere MQ adapter to consume 100% of CPU time was identified and fixed. |
| SB‑23619 | When using the Wombat MAMA Input adapter, subscriptions that failed with a NOT_FOUND error were correctly removed from the adapter, but the underlying Wombat subscription was not destroyed. This was fixed. |
| SB‑23602 | An unusual race condition when starting multiple containers with synchronous container connections was fixed. |
| SB‑23336 | Dynamic variables in StreamSQL programs were updated to allow recursively referencing themselves in an update expression. |
| SB‑23137 | Documentation for previous 7.2.x releases continued to state that only jsbc enqueue could enqueue an empty tuple to an input stream defined with an empty schema. Actually, sbc enqueue gained that capability starting with 7.2.0. |
| SB‑22757 | The .NET Client Library was updated to behave more like the Java Client Library in one respect. Previously, when a DequeueResult.Interceptor returned null, the null was returned to its caller, which interrupted dequeuing. Now a null case no longer interrupts dequeuing. |
| SB‑22961 | The parsejson() expression language function, when used with expressions containing asterisk wildcards, could cause methods to grow beyond the Java 64K boundary. This was fixed. |
| SB‑21383 | In previous releases, an internal error at runtime occurred for Filter operators that were followed by output streams with schemas explicitly set to have compatible but differently ordered fields. This was corrected. |
| Fixed in 7.2.12 | |
|---|---|
| Number | Resolution |
| Release 7.2.12 incorporates all fixes resolved in the release 7.1 series through 7.1.12, in the release 7.0 series through release 7.0.12, and in the release 6.6 series through release 6.6.24. See Limitations Resolved in 7.1.x, Limitations Resolved in 7.0.x, and Limitations Resolved in 6.6.x for details. | |
| SB‑XXX | This was wrong. This was fixed. |
| Fixed in 7.2.11 | |
|---|---|
| Number | Resolution |
| Release 7.2.11 incorporates all fixes resolved in the release 7.1 series through 7.1.12, in the release 7.0 series through release 7.0.12, and in the release 6.6 series through release 6.6.24. See Limitations Resolved in 7.1.x, Limitations Resolved in 7.0.x, and Limitations Resolved in 6.6.x for details. | |
| SB‑24214 | The IBM WebSphere MQ input adapter was not reporting connection-down errors for some error codes. This was fixed. |
| SB‑24198 |
The format function, when it received a null,
would sometimes incorrectly return a previously received non-null value.
This was fixed.
|
| SB‑24066 | Query Operators lost their match settings when connected to Query Tables whose schemas were imported from Event Flow applications with typecheck errors. This was fixed. |
| SB‑24052 | Parent fields for some imported schemas were sometimes unavailable from the Properties View tab. This was fixed. |
| SB‑24034 | Name collisions between imported schemas' names and group names caused loading errors. The groups are now automatically renamed to prevent these errors. |
| SB‑23962 |
In certain cases, the calljava method with a
null argument incorrectly errored. This was fixed.
|
| SB‑23830 | A StreamBase Studio restart would remove the Own-Thread option from an existing, saved Extension Point operator. This was fixed. |
| SB‑23703 | Studio did not automatically add a file extension prior to checking for filename conflicts when a file had the same basename as its containing directory. This was fixed. |
| SB‑18565 | Editing a table's secondary index field sometimes reset the Order property of the associated Query operators. This was fixed. |
| Fixed in 7.2.11 | |
|---|---|
| Number | Resolution |
| Release 7.2.11 incorporates all fixes resolved in the release 7.1 series through 7.1.12, in the release 7.0 series through release 7.0.12, and in the release 6.6 series through release 6.6.24. See Limitations Resolved in 7.1.x, Limitations Resolved in 7.0.x, and Limitations Resolved in 6.6.x for details. | |
| SB‑24129 | If a marketfeed message in the Reuters adapter contained one or more invalid enumeration field values and the adapter's Send Enum Field Display Values was set, a message was incorrectly dropped. This was fixed. |
| SB‑24054 | The StreamBase .NET API tuple-field data accessors showed poor performance when using the GetField method to get null-valued fields. This was fixed. |
| SB‑24033 | If a user had multiple EventFlow editor windows open, and used the Add Note hotkey (/) to add a note in one open window and then switched windows without first closing the note, the note editor would remain active in the first window, rather than the active window. This means that any successive attempts to add notes in other windows would be saved to the original window, rather than the active window. This was fixed. |
| Fixed in 7.2.10 | |
|---|---|
| Number | Resolution |
| Release 7.2.10 incorporates all fixes resolved in the release 7.1 series through 7.1.12, in the release 7.0 series through release 7.0.12, and in the release 6.6 series through release 6.6.23. See Limitations Resolved in 7.1.x, Limitations Resolved in 7.0.x, and Limitations Resolved in 6.6.x for details. | |
| SB‑23933 |
If the Java source folder for custom Java operators, adapters, or functions
was anything other than java-bin under a
Studio project root (as could happen when using Maven to manage the Java
files), then Studio was unable to load that operator, adapter, or function
during typechecking of the project. Studio would report that the class
could not be found. This was corrected.
|
| SB‑23930 | The XML-to-Tuple operator can populate tuple fields with XML attributes in one of two ways: (1) By using the special _ATTRIBUTES meta field, or (2) by creating a subfield with a name that matches the attribute name. The second technique was not working if the subfield's parent field was of type list<tuple>. This was fixed. |
| SB‑23912 | In previous releases, the expression language's strptime() function incorrectly interpreted time strings that specified the noon hour as a timestamp 12 hours later. This was corrected. |
| SB‑23879 |
Two Unicode-handling bugs in StreamBase Studio were corrected. Even if
Studio was configured to be Unicode ready with the streambase.tuple-charset=UTF-8 setting, (1) the
Copy as ... options in the context menu of
the Application Output view would not correctly copy Unicode characters,
and (2) the New StreamBase Unit Test wizard could garble Unicode characters
in Java files created from the Application Output view.
|
| SB‑23853 | For 64-bit platforms, the .NET and C++ clients would sometimes not release Windows handles after a connection was terminated, so subsequent connection attempts would increase the handle counts. This was fixed. |
| SB‑23739 | A busy loop that caused a thread in the IBM WebSphere MQ adapter to consume 100% of CPU time was identified and fixed. |
| SB‑23726 | On Linux systems, an unpredictability in classpath loading order was resulting in a NullPointerException for the Alpha Trading Systems adapters. The classpath loading order was updated to assure a predictable order. |
| SB‑23619 | When using the Wombat MAMA Input adapter, subscriptions that failed with a NOT_FOUND error were correctly removed from the adapter, but the underlying Wombat subscription was not destroyed. This was fixed. |
| SB‑23608 | When enqueuing with a C++ or Python client and specifying an input stream by stream name in the default container without its qualifying path (that is, "in" rather than "default.in"), a performance penalty was incurred because the client would repeatedly query the server for stream properties rather than using the client side cache. The workarounds were to manually cache the StreamProperties object or use full stream path name. This limitation was lifted and the workarounds are no longer necessary. |
| SB‑23602 | An unusual race condition when starting multiple containers with synchronous container connections was fixed. |
| SB‑23485 | In previous releases, an xi:include in a server configuration file could cause an error that referred to the Boost libraries when starting StreamBase Server as a Windows service. The cause was identified and corrected. |
| SB‑23137 | Documentation for previous 7.2.x releases continued to state that only jsbc enqueue could enqueue an empty tuple to an input stream defined with an empty schema. Actually, sbc enqueue gained that capability starting with 7.2.0. |
| SB‑22757 | The .NET Client Library was updated to behave more like the Java Client Library in one respect. Previously, when a DequeueResult.Interceptor returned null, the null was returned to its caller, which interrupted dequeuing. Now a null case no longer interrupts dequeuing. |
| Fixed in 7.2.9 | |
|---|---|
| Number | Resolution |
| Release 7.2.9 incorporates all fixes resolved in the release 7.1 series through 7.1.11, in the release 7.0 series through release 7.0.12, and in the release 6.6 series through release 6.6.22. See Limitations Resolved in 7.1.x, Limitations Resolved in 7.0.x, and Limitations Resolved in 6.6.x for details. | |
| SB‑23770 | In recent 7.2.x releases, when developing a custom Java operator or adapter, if your custom class cannot load at runtime in Studio (perhaps because it failed to build), the settings in the Properties view for your operator or adapter would be inadvertently cleared. This was corrected so that a failure-to-load error no longer clears any Properties view settings. |
| Fixed in 7.2.8 | |
|---|---|
| Number | Resolution |
| Release 7.2.8 incorporates all fixes resolved in the release 7.1 series through 7.1.11, in the release 7.0 series through release 7.0.12, and in the release 6.6 series through release 6.6.22. See Limitations Resolved in 7.1.x, Limitations Resolved in 7.0.x, and Limitations Resolved in 6.6.x for details. | |
| SB‑23428 | The format of ContainerConnectionException error messages was updated to include the source container name, connection name, and endpoint name, in cases where this information is available. |
| SB‑23401 | The Thomson Reuters Schema Designer was updated to map Reuters type OMMTypes.UINT64 to StreamBase type long. |
| SB‑23355 | A Query Read operation was returning an incorrect result set if the range criteria for one of the index fields had a begin-to-end specification followed by an index field having a null specification. This was fixed. |
| SB‑23351 | When using Log4j as the logging back end with asynchronous loggers, queues log messages could get dropped on shutdown. This was fixed. |
| SB‑23347 | When using the StreamBaseFIX FIX engine's session handling, where a pending TestRequest would still be considered pending even after a disconnection-reconnection cycle. |
| SB‑23206 | The StreamBaseFIX FIX engine now correctly use username and password, in lowercase as shown, to fetch these settings in the StreamBaseFIX configuration file, to match the sample configuration file and the documentation. |
| SB‑22942 | A NullPointerException error could be thrown when using the EventFlow Debugger to try to see the values of a list stored in a Query Table. The debugger supports viewing lists in tuples in an arc, but not in Query Tables. The attempt to view lists in Query Tables is now correctly blocked, and no longer throws the error. |
| SB‑22299 | When using the EventFlow debugger, breakpoints before Error Output Streams were not hit. This was corrected. |
| SB‑20483 | In previous releases, opening the Breakpoint Properties dialog for an arc resulted in a large, empty dialog with a few lines of unhelpful text. This dialog is now fully populated with information that applies to the selected arc, and also supports the new conditional breakpoints feature. |
| Fixed in 7.2.7 | |
|---|---|
| Number | Resolution |
| Release 7.2.7 incorporates all fixes resolved in the release 7.1 series through 7.1.11, in the release 7.0 series through release 7.0.12, and in the release 6.6 series through release 6.6.22. See Limitations Resolved in 7.1.x, Limitations Resolved in 7.0.x, and Limitations Resolved in 6.6.x for details. | |
| SB‑23277 | An otherwise valid EventFlow module with Chinese characters in an operator's Description text would fail typechecking, despite having both Server and Studio Unicode settings as described in Unicode Support. The cause was identified and corrected. |
| SB‑23252 |
In previous releases, under certain conditions, embedded adapters would
incorrectly use the containing server's log level setting instead of the
adapter's independent log level setting. The conditions were: the
STREAMBASE_USE_CUSTOM_LOGGING environment variable was set to true, and the adapter was configured to log at the same or
a less verbose level than the server. This was corrected.
|
| SB‑23230 | The Thomson Reuters TREP-RT Subscribing Input adapter was incurring an exception in processing a market price message for each field not present in the adapter's schema, leading to less than optimal performance. This issue occurred only when the adapter's Disable Market Price View Requests was enabled (not the default), or when processing messages from a Thomson Reuters server that does not support view requests. The adapter was updated to respond correctly to these situations. |
| SB‑23072 | Query Table updates using a large number of fields were running into the JVM's 64K size limit for methods. The generation of these methods was optimized to reduce their size and allow more fields to be present. |
| SB‑23047 | A Query that contained a range bound, followed by an equality bound, where the equality bound was checking for nulls, always returned no results in previous 7.2.x releases. This was fixed. |
| SB‑22930 | In 6.6.x releases, double-clicking an entry in the Problems view both opened the affected EventFlow module and selected the operator with the problem. In previous 7.x releases, the same double-click opened the affected module but failed to select the affected operator. This was corrected such that the 6.6 behavior was restored. |
| Fixed in 7.2.6 | |
|---|---|
| Number | Resolution |
| Release 7.2.6 incorporates all fixes resolved in the release 7.1 series through 7.1.10, in the release 7.0 series through release 7.0.12, and in the release 6.6 series through release 6.6.21. See Limitations Resolved in 7.1.x, Limitations Resolved in 7.0.x, and Limitations Resolved in 6.6.x for details. | |
| SB‑23043 | In previous releases, a NullPointerException could result when deleting a parent schema from the EventFlow Editor's Definitions tab. This was fixed. |
| SB‑23030 | On Windows with release 7.2.5, StreamBase Server launched from the StreamBase Command Prompt could fail or hang under some circumstances if the server configuration file included XML comments. This was fixed. |
| SB‑23000 | When using the EventFlow Debugger without the Debug view open, breakpoints were hit but navigation to the hit breakpoint in the EventFlow Editor could not be shown. Starting with 7.2.6, on a breakpoint hit, the Debug view is opened if not already open. |
| SB‑22997 | After upgrading to release 7.2.5, a 7.1.x application that uses shared and placeholder Query Tables was failing to typecheck in Studio. The cause was identified and corrected. |
| SB‑22976 | When using the O E keyboard shortcut to place a Module Reference on the canvas, the gray data port did not initially appear if the referenced module contained only a shared Query Table. This was corrected. |
| SB‑22971 | A RuntimeException could occur when using the readTable API to read from a Query Table configured with a capture field. This was fixed. |
| SB‑22958 |
In the .NET Client Library, DequeueResult.GetTupleCount() was returning null
instead of 0 when Status==DequeueResult.TIMEOUT. This was corrected.
|
| SB‑22837 | A leak of Path resource memory from the graphics rendering code that supports Studio was corrected. |
| SB‑22752 | The prerequisites for the RPM method of installing StreamBase on Linux were updated so that installing StreamBase does not automatically require third-party libraries. |
| SB‑22731 |
In previous 7.2.x releases, disk-based Query Tables with indexes that
contained lists before the final element of the index could result in
Unexpected tag messages on the Console view.
This was fixed.
|
| SB‑22706 |
The expression language's new_tuple()
function could grow beyond the Java 64 Kbyte limit when given schemas with
over 60 fields. The function was refined to allow much larger schemas.
|
| SB‑22675 | In previous 7.2.x releases, Query operators could return an unexpected result set when the table was accessed through a module reference. This was corrected. |
| SB‑22628 | When using the EventFlow Debugger, a ClassNotLoadedException could occur when expanding a tuple variable in the Variables view. This was fixed. |
| SB‑22422 | A race condition on startup of StreamBase Server was affecting LiveView Server startup. The cause was identified and corrected. |
| SB‑22249 |
The error message that resulted from a failure to provide a numerical
argument for the -x option of the sbfeedsim command was misleading. This
was corrected with better error messages.
|
| SB‑21839 | The TableAccesor.delete() method did not provide a way to report a no-match result. This was corrected. |
| SB‑21487 | Studio could show an Error Log view error when deleting a project that had a file open in Studio. This was fixed. |
| Fixed in 7.2.5 | |
|---|---|
| Number | Resolution |
| Release 7.2.5 incorporates all fixes resolved in the release 7.1 series through 7.1.9, in the release 7.0 series through release 7.0.12, and in the release 6.6 series through release 6.6.20. See Limitations Resolved in 7.1.x, Limitations Resolved in 7.0.x, and Limitations Resolved in 6.6.x for details. | |
| SB‑22584 | Red error text in the Properties view of the Aggregate operator was not being cleared when the error condition was resolved. This was corrected. |
| SB‑22548 | When using the EventFlow Debugger, attempts to traverse a call stack could intermittently encounter a failure with a "source not found" error and an "invalid stack frame" exception. This issue was resolved. |
| SB‑22530 | When using the EventFlow Debugger, a DebugException with ObjectCollectedException error could appear in the Error Log View in rare cases when an internal call from the debugger to the debugged process failed because an argument in the call happened to be garbage collected before the remote call was able to start. This was fixed. |
| SB‑22500 | When using the EventFlow Debugger, three question marks could appear for the value of a timestamp field in the Variables view, with a ThreadNotSuspendedException appearing at the same time in the Error Log view. This was corrected. |
| SB‑22413 | StreamBase Systems discourages editing a project's server configuration file, or one of its component fragment files, in another editor outside of Studio while Studio is running. Nevertheless, if you do so, and forget to refresh the Studio project after such edits but before running Refresh Typecheck Environment, Studio no longer throws a Class Error. |
| SB‑22408, SB‑22364 |
In releases 7.2.3 and 7.2.4, Studio could lock up when attempting to edit a
server configuration file with one or more <xi:include> statements. This was corrected.
|
| SB‑22370 | The Thomson Reuters TREP-RT Subscribing Input adapter was updated to move its one-time initialization code to a later state of the adapter's start-up sequence. This avoids "time out on state change" errors. |
| SB‑22356 | In previous 7.2.x releases, properties for the currently selected Query operator were sometimes observed to load slowly into the Properties view. This was corrected, providing a significant speedup in property loading. |
| SB‑22006 | In previous 7.2.x releases, in a Query operator with Write-Update operation, set actions in the Additional Expressions grid sometimes failed to be reflected in the table fields pane on the left. This was fixed. |
| Fixed in 7.2.4 | |
|---|---|
| Number | Resolution |
| Release 7.2.4 incorporates all fixes resolved in the release 7.1 series through 7.1.8, in the release 7.0 series through release 7.0.12, and in the release 6.6 series through release 6.6.19. See Limitations Resolved in 7.1.x, Limitations Resolved in 7.0.x, and Limitations Resolved in 6.6.x for details. | |
| SB‑22346 | In previous 7.2.x releases, a Query operator with Write-Insert operation and the If row exists selection Update existing row using values in Fallback, could replace table values with null. This was corrected. |
| SB‑22330 | In previous 7.2.x releases, a Query operator with Write-Update operation upgraded from a pre-7.2 release could display an empty Action column in the Properties view Operation tab. This was fixed to show the Set action. |
| SB‑22327 | In previous 7.2.x releases, a Query operator with Write-Update operation used in a hygienic module could emit unexpected data as output. This was fixed. |
| SB‑22318 | EventFlow modules that use imported schemas or definitions could get flagged as needing to be saved despite having no changes in the module itself, in cases when an imported resource changed in its original location. This was corrected. |
| SB‑22317 | In previous releases, if you copied a Module Reference and disconnected the copy, the original Module Reference could lose its table association in the Tables tab of its Properties view. This was corrected. |
| SB‑22315 | In previous releases, using the Debug view's Terminate button would stop the debug session, then halt the running StreamBase Server instance without its usual shutdown procedures. This sequence of operations could fail to delete the disk Query Tables’ lock directory, which would then require deleting the lock directory manually before restarting the application. The Debug view's Terminate button was updated to perform the same clean shutdown of the Server as the Stop button in the top-level Studio toolbar. |
| SB‑22305 | In previous 7.2.x releases, the server could throw a ClassCastException when a Query Table was connected through Module References to an inner module with at least two levels of capture fields with identical schemas. This was fixed. |
| SB‑22302 | When using the StreamBase to StreamBase adapters with their Low Latency property disabled, duplicate data could be delivered in place of expected data. The cause was identified and corrected. |
| SB‑22300 | The error messages "missing parameter table" and "missing parameter operation" were revised to more clearly describe the problem using EventFlow terminology. In general, typecheck error messages that can be thrown by the server runtime were reviewed and updated for clarity and EventFlow relevance. |
| SB‑22223 | In previous 7.2.x releases, the indexof() function for lists of tuples became inadvertently sensitive to field order. The behavior of the function in 7.1.x was restored. |
| SB‑22133 | A client application built with the .NET Client Library and the .NET 4 framework could result in multiple System.IndexOutOfRangeException errors. This was corrected. |
| SB‑22098, SB‑22099 | In the Aggregate operator, the expression used for the opening policy is evaluated in a non-aggregate context and thereby must resolve to a simple function. In previous releases, no error or warning was issued if you used an aggregate function in the opening policy expression, and the module resulted in a NullPointerException at runtime. This case now has shows a typecheck error. |
| SB‑22092 | When the Union operator detects a schema mismatch, Studio shows a SchemaMismatchException error. The (go to error) and (compare schemas) links were moved to the beginning of the tooltip message for this error so that they are always available even for very wide schemas. |
| Fixed in 7.2.3 | |
|---|---|
| Number | Resolution |
| Release 7.2.3 incorporates all fixes resolved in the release 7.1 series through 7.1.8, in the release 7.0 series through release 7.0.12, and in the release 6.6 series through release 6.6.19. See Limitations Resolved in 7.1.x, Limitations Resolved in 7.0.x, and Limitations Resolved in 6.6.x for details. | |
| SB‑22259 | The Wombat MAMA Publishing Output adapter was updated to clarify WARN log messages from the adapter that occur when the feed dictionary changes, but the application still expects a field with a type defined in the previous dictionary. |
| SB‑22253 | In previous releases, when processing millions of tuples, if queues become very backed up, StreamBase Server begins to manage memory growth. After emitting WARN log messages about the queue backup, under certain rare conditions, some amount of queue data could be lost or inappropriately replayed. The cause was identified and corrected. |
| SB‑22234 | In previous 7.2.x releases, a Query Table that used a table schema, which in turn was composed with a parent schema would show incorrect red X typecheck error icons in the table's Properties view. This was corrected. |
| SB‑22214 | A typecheck error could occur on a Once adapter when the same module had a locally defined table schema that used a locally defined named schema. This was fixed. |
| SB‑22209 | An IndexOutOfBoundsException error was generated when renaming a table schema without using → . This was fixed. |
| SB‑22183, SB‑22178 | In previous 7.2.x releases, the default setting for the Query operator's Operation tab was changed compared to release 7.1. As of 7.2.3, this tab's default for the If no rows are found selection is restored to match input with null values both for new Query operators and those upgraded to 7.2 from existing modules. |
| SB‑22176 | In previous 7.2.x releases, the Sequence operator was missing its default values. This was corrected. |
| SB‑22134 | In projects upgraded to 7.2, some Query operators associated with Module References were reporting an incorrect typecheck failure about undefined tables. This was fixed. |
| SB‑22091, SB‑21514 | When using the EventFlow Debugger in previous releases, changing the value of a variable in the Variables view would fail, resulting in an error. A similar error could result from changing a dynamic variable in the Variables view. These conditions no longer generate an error. |
| SB‑22087 | In projects upgraded to 7.2, Query operators could sometimes appear with no input grid in the Output tab; closing and reopening the module would restore the input grid, but in the wrong location in the tab. The cause was identified and corrected. |
| SB‑22017 | Arc bend points on the EventFlow canvas were not correctly restored when reloading a module. This was fixed. |
| SB‑21890 | In previous 7.2.x releases, when you specified a Query operator with Delete operation, and also specified Where: All rows, the Order control was incorrectly activated. This was fixed. |
| SB‑21805 | When you enabled an error port on operators with no output ports, an error dialog would result, even though the error port was created correctly. The appearance of the error dialog was corrected. |
| SB‑20398 | The Copy Schema From dialog was updated to include output streams as a source of schemas to copy. |
| Fixed in 7.2.2 | |
|---|---|
| Number | Resolution |
| Release 7.2.2 incorporates all fixes resolved in the release 7.1 series through 7.1.7, in the release 7.0 series through release 7.0.12, and in the release 6.6 series through release 6.6.18. See Limitations Resolved in 7.1.x, Limitations Resolved in 7.0.x, and Limitations Resolved in 6.6.x for details. | |
| SB‑22090 | In some cases, a Map operator created in recent 7.1.x releases would show empty settings in the Properties view's Output Settings tab after importing into release 7.2. This was corrected. |
| SB‑22027 | In previous 7.2 releases, a Query operator performing a Write operation exhibited different output behavior depending on the Fallback option selected. This was fixed. |
| Fixed in 7.2.1 | |
|---|---|
| Number | Resolution |
| Release 7.2.1 incorporates all fixes resolved in the release 7.1 series through 7.1.7, in the release 7.0 series through release 7.0.12, and in the release 6.6 series through release 6.6.18. See Limitations Resolved in 7.1.x, Limitations Resolved in 7.0.x, and Limitations Resolved in 6.6.x for details. | |
| SB‑22072 | In previous releases, long-running, high-volume enqueuing clients could, in some circumstances, exhaust StreamBase Server's input queue buffer capacity, resulting in a disconnected client after the connection timed out. This was corrected. |
| SB‑21799 | The error message caused by exceeding the maximum input packet size was clarified and improved. |
| SB‑21589 | In previous releases, if you dragged the left side of an arc from an input stream and reconnected the arc to another component, the arc incorrectly gained a declared schema, using the schema of the input stream. This was corrected. |
| SB‑20656 | The Wombat MAMA Output adapter was verified to work over the TIBCO Rendezvous (RV) transport. You must obtain a Wombat library version that supports RV and is at least version 5.0.4 or later. |
| Fixed in 7.2.0 | |
|---|---|
| Number | Resolution |
| Release 7.2.0 incorporates all fixes resolved in the release 7.1 series through 7.1.6, in the release 7.0 series through release 7.0.11, and in the release 6.6 series through release 6.6.17. See Limitations Resolved in 7.1.x, Limitations Resolved in 7.0.x, and Limitations Resolved in 6.6.x for details. | |
| SB‑21768 | The schema for the status port of the FXall Relationship Trading Provider adapter was optimized to use current StreamBase APIs. |
| SB‑21655 | When using the optional StreamBaseFIX FIX engine, FIX tag values greater than about 33000 resulted in an error when loading the data dictionary. This was corrected. |
| SB‑20785 | In previous releases, the Copy Schema From dialog included imported schemas when showing the available schemas from a particular module. The was corrected to show only locally defined schemas for each module. |
| SB‑19477 |
Removing a nested field from a null tuple in a Map operator now leaves the
tuple as null, instead of changing it to a tuple filled with nulls. For
example, if you send the tuple (top(a,b,c)) to a Map operator that drops
field b, the resulting tuple is (top(a,c)). If top is null before the
Map, now it is null after the Map.
|
| SB‑17246 | The Trace Debugger would sometimes leave its color highlight in place after returning to the SB Authoring perspective. This was fixed. |
| SB‑13271 | Previous releases of the .NET Client Library did not provide a way to construct a new DequeueResult, while the Java Client Library provided SimpleDequeueResult for this purpose. This situation was corrected in the October 2011 refresh of the .NET API with the addition of the DequeueResult constructors. See Migrating .NET Clients. |
| SB‑12662 |
In previous releases of the .NET Client Library, using IsNull("wrong_field_name") threw the generic SEHException
instead of StreamBase.SB.NoSuchFieldException. This situation was corrected
in the October 2011 refresh of the .NET API as described above.
|
See the Release Note Archives for the list of issues resolved in previous releases.
This section describes known limitations in the current release of StreamBase. Each item includes a tracking number, description, and whenever possible, one or more workarounds.
Known limitations for using the EventFlow debugger are described separately, in the Limitations, Tips, and Tricks section of the Using the EventFlow Debugger page.
| SB‑23766 | Starting a StreamBase demo on OS X from the SB Demo perspective may cause StreamBase Studio to hang. | |
| Description | The SB Demo perspective may not launch demos consistently on OS X installations. | |
| Workaround | Force Quit StreamBase Studio and try to start the demo again. | |
| SB‑23741 | Studio crashes on older 32-bit Linux distributions. | |
| Description | A reported Eclipse bug causes Studio to crash on 32-bit Linux when attempting to render a non-empty EventFlow application. This problem is seen with 32-bit RHEL 4 and SuSE 10 distributions, and only with Studio 7.3.0 or later, where the base Eclipse installation is 3.8. | |
| Workaround | Try using a 64-bit version of the same distributions, where this problem does not occur. | |
| SB‑24218 | Rapid, repeated single-stepping In the StreamBase Studio Debugger can lead to a variety of errors | |
| Description | If you single-step quickly and repeatedly while debugging a StreamBase application, unpredictable errors can occur. The types of errors vary, and may include errors in the Error Log, problems with data in the Variables view, and in the worst case, a hang of Studio. | |
| Workaround | When possible, if you know which upstream arc at which you'd like to stop, instead of repeatedly single-stepping to get to that arc, right-click over the downstream arc and choose 'Run to Arc'. That method is often easier and faster, and it avoids problems that may occur due to single-stepping too quickly. | |
| SB‑22297 | Commented-out error input streams consume error tuples. | |
| Description | An error input stream, despite being disabled with the EventFlow comment-out feature, still catches errors thrown, but consumes any incoming errors and fails to pass them on. | |
| Workaround | To temporarily disable error streams, copy them to a placeholder module and remove them from the active module. | |
| SB‑22129 | Changing a nested sbconf file does not cause the containing project to rebuild. | |
| Description |
Server configuration files can be nested using the <sb-include> or <xi:include> elements as described on Using Modular Configuration
Files. When you save a change in a top-level sbconf file, the project
automatically rebuilds. However, when you save a change in a nested sbconf
file, rebuilding the project is not automatically triggered.
|
|
| Workaround | After editing a nested sbconf file, select the containing project in Studio's Package Explorer view, right-click, and from the context menu select → . You can also use the keyboard shortcut, Ctrl+F5. | |
| SB‑21843 | In the TableAccessor API, ClassCastException is thrown if not using a Tuple from TableAccessor#createRow | |
| Description |
If methods in the com.streambase.sb.operator.TableAccessor interface that
accept a Tuple are not provided a Tuple retrieved from TableAccessor#createRow, a ClassCastException may be
thrown by the API.
|
|
| Workaround |
Always use TableAccessor#createRow when using
TableAccessor API methods.
|
|
| SB‑21817 | EventFlow Debugger breakpoints not hit in files named with hyphens. | |
| Description | When using the EventFlow Debugger, some breakpoints are not hit when stepping through an EventFlow file whose name contains a hyphen. | |
| Workaround | Rename the file, either permanently or for the duration of the debugging session. | |
| SB‑20449 | Display issues with years before 2 AD. | |
| Description | The timestamp data type can hold timestamp values in the range -(2^62) to (2^62)-1, and can successfully display any future date in the next 146 million years and any past date to around year 2 AD. However, the year value for dates earlier than 2 AD may not display correctly. | |
| Workaround | None. | |
| SB‑20347 | Cannot run the eval() function with sbd --eval. | |
| Description | The eval() function is one of several expression language functions that do not run successfully at the command prompt with sbd --eval, but that run as expected in EventFlow and StreamSQL expressions. See Evaluating Expressions with sbd --eval. | |
| Workaround | None. | |
| SB‑19691 | Container connection command blocked by field name same as StreamBase reserved word. | |
| Description |
A container connection command, such as might be made with sbadmin modifyContainer addConnection is
blocked if the identifier of a stream, or a field name used in a --where clause is also in the StreamSQL or Expression
language reserved word list.
|
|
| Workaround |
Enter the reserved word in the container connection command using escaped
identifier syntax. For example: ...addConnection
"default.InStream=(sb://sbhost:14000/default.OutStr)" --where '#"size" ==
0'
|
|
| SB‑18548 | Warning messages about environment variables at application startup. | |
| Description | Under some circumstances, StreamBase Server can emit warning messages at startup that indicate an environment variable has changed since the application was compiled. In most cases, these warnings have no consequences and can be ignored. However, when the server is loading a bundle file that includes a precompiled archive file, an environment variable warning message has the unintended side effect that the server ignores the bundled archive file and recompiles the application from the bundled source files. The bundled application does run normally, but for very large applications, at the cost of the recompilation time. | |
| Workaround |
To avoid recompiling a bundled archive file, set the following system
property:
streambase.check-app-environment-variables-changed=false |
|
| SB‑18495 | Trace Debugger highlight colors do not clear automatically. | |
| Description | When closing or switching away from using the Trace Debugger perspective, the EventFlow Editor might still show color highlighting from the tracing session. | |
| Workaround | Close and reopen the EventFlow Editor. | |
| SB‑18294 | Union operator: sub-field order of tuple fields must match with strict options. | |
| Description | When using the Union operator with its Strict union or Declared schema options, the order of sub-fields of tuple fields must match exactly. This is in contrast with the default Loose union option, where strict sub-field ordering is no longer required. | |
| Workaround | None. | |
| SB‑18189 | Some Windows UI themes fail to render borders. | |
| Description | On some Windows UI themes, such as the Windows XP Classic theme, some UI elements are drawn without a border. This affects the JDBC SQL text box of the Query operator, among others. | |
| Workaround | Try a different Windows theme. | |
| SB‑18076 | Studio on Linux can hang when loading demo applications. | |
| Description | On Linux only, Studio can hang when attempting to load an EventFlow application from the demo perspective. | |
| Workaround | None. You must force Studio closed and restart it. | |
| SB‑18049 | Do not define StreamBase constants along with certain expression language functions. | |
| Description | A limitation prevents StreamBase constants from working correctly if any of certain expression language functions are used in the definition of the constant. Attempting to do so produces a typecheck warning. Overriding the warning results in a failure of the server to start. Functions affected by this limitation include: any custom C++ function, get_conf_param(), get_*_conf_param(), getContainer(), getErrorType(), getErrorAction(), getLeadershipStatus(), getNodeName(), getPath(), format(), regexmatch(), regexmatch_ignorecase(), regexsplit(), split(). | |
| Workaround | Define the same constant as a dynamic variable. | |
| SB‑17414 | Order of layout parameters changed one time after import into 6.5 or later. | |
| Description |
When importing an EventFlow module created with StreamBase 6.4 or earlier
into StreamBase 6.5 or later, some layout parameter lines may shift positions
in the .sblayout file (or .sbapp file if you do not use separate layout files). This
may affect difference comparisons or version control systems.
|
|
| Workaround | The reordering of layout parameter lines is a one-time occurrence after the first save in StreamBase 6.5 or later. Thereafter, these lines are stored consistently with each save. | |
| SB‑17306, SB‑17182 | Unexpected property changes can result from typecheck errors in a module from which other modules import. | |
| Description | If you define schemas and table schemas in a definitions module, such as module A, and introduce a typecheck error into module A, then any currently open module, such as B, that imports schemas from module A also shows a typecheck error. If you then visit the Properties view for a failing Query Table component in module B, that table's imported table schema disconnects, and may result in properties updating themselves in the disconnected state. On save, the Query Table no longer refers to the imported table schema. | |
| Workaround |
Correct the error in the definitions module A prior to reselecting the
imported table schema in the Table Settings tab of the Properties view for
Query Tables in module B.
To avoid this situation, StreamBase Systems recommends as a best practice that your definitions modules contain only schema definitions and no tuple processing components at all. The sole exception is a Note component whose text can warn other developers not to edit the canvas or place logic components there in any way. If your definitions module, A, does contain tuple processing components, and you inadvertently introduce a typecheck error in module A, then avoid selecting any component in any module that imports from module A. Instead, correct the error in and save module A, which removes the error condition from all importing modules. |
|
| SB‑16594 | Extract as Module feature copies items instead of importing them. | |
| Description | The Extract as Module feature makes a copy of the source module's definitions and named schemas, and places the copies in the newly created module. Best practice would be to import those features from the source module to the new module, and to copy all imports from the source to new modules. | |
| Workaround | After using Extract as Module, manually convert the copied definitions and named schemas to imports. | |
| SB‑16555 | Doubled menu items in Windows Start menu. | |
| Description |
The Start menu should be cleared when a previous StreamBase release is
uninstalled, so that you only see menu entries for the most recently
installed release. However, on systems with more than one StreamBase release
installed (such as releases 6.4 and 6.5), the uninstaller can sometimes fail
to remove the old entries from the Start menu. In previous releases, this was
not an problem, because the new installer (for, say, 6.5.3) would simply
overwrite the same entries for the previously installed release (say, 6.5.1).
However, starting with release 6.5.4, the StreamBase installer now adds the release number to Start menu entries for the StreamBase Command Prompt and for links to documentation. If an uninstaller fails to clean up the Start menu for a previous 6.5 release, you may see both old and new style links. |
|
| Workaround | Uninstall the most recently installed release (such as 6.5.4). Manually remove its entire Start menu folder (such as → → ), then reinstall the new release. | |
| SB‑15750 | Issues when pinning StreamBase icons to the Windows 7 task bar. | |
| Description | StreamBase Studio runs well on on Windows 7, with some minor exceptions related to Windows 7's new pinning feature. These issues are the following: (1) When Studio is running, if you pin its task bar button to the task bar, the pinned button shows the generic Java icon, not the StreamBase icon; and when launching Studio from this pinned button, Windows 7 tries to run Java without Studio. (2) For the StreamBase Help Viewer, no Pin to Task Bar context menu appears. Studio shares these Windows 7 issues with all Java-based programs. | |
| Workaround | You can pin the desktop Studio icon to the task bar, or pin the Studio entry in the All Programs menu to the task bar. In these cases, the Studio task bar button does get the correct StreamBase icon, but when launching from a button so pinned, a second button appears in the task bar for the duration of the Studio session. | |
| SB‑15736, SB‑15731 | Unresponsive Studio buttons with newer versions of Linux GTK. | |
| Description | When running Studio releases 6.5.0 through 6.5.4 on recent Linux distributions that provide a new release of the GTK libraries, a known Eclipse bug prevents certain buttons in the Studio user interface from responding to clicks. Keyboard shortcuts for the same functions are still active. | |
| Workaround | This bug does not affect the supported Linux distributions. If you install Studio 6.5.0 through 6.5.4 on an unsupported Linux distribution, you can work around the issue by setting the environment variable GDK_NATIVE_WINDOWS=1 in the shell or script you use to start Studio. Studio releases 6.5.5 and 6.6.x are based on Eclipse 3.5.2, which does not exhibit this behavior. | |
| SB‑14862 |
Custom Java operators and adapters cannot include their own janino.jar.
|
|
| Description |
The StreamBase Server executable, sbd[.exe], incorporates a customized
version of the Janino libraries that include bug fixes that have not yet been
absorbed by the Janino project. If you attempt to include the standard
janino.jar implementation of Janino as part of
a custom operator or adapter, that JAR file conflicts with the version
embedded in sbd.
|
|
| Workaround |
Call Janino as part of StreamBase's server.jar,
or see http://code.google.com/p/janino-streambase for public
access to StreamBase's Janino bug fixes.
|
|
| SB‑14847 | Studio on Linux fails to start, instead showing org.eclipse.swt.SWTError. | |
| Description | This issue affects only StreamBase Studio 6.4.x releases, which are based on Eclipse 3.4, and only when installed on a Linux system that also has an installation of Firefox 3.x, or other Mozilla-based browser. | |
| Workaround | These problems do not occur with Studio 6.5 or later. Studio 6.4 users, see Xulrunner Issues in StreamBase for instructions. | |
| SB‑14239 | Recordings in Studio fail to play back against streams with imported schemas. | |
| Description | Since release 6.4.0, applications can use the Module Imports feature of the EventFlow Editor's Definitions tab to import schemas. If you use the Studio Recordings view to record the operation of such an application, it fails to play back. | |
| Workaround | Create a local copy of the imported schema in the application module that contains the stream, and specify the copy for use by the stream. Then re-record the application. | |
| SB‑14133 | sb-config --cxx returns a setting for G++ 4.3, 4.4, or 4.5 on newer Linux distributions | |
| Description | On Linux, in StreamBase samples that build C++ code, some of the example Makefiles show sb-config --cxx as the correct usage to determine the G++ compiler to use. On newer Linux distributions, this command returns the distribution's default G++ 4.3, 4.4, or 4.5 compiler, which is not supported for building StreamBase client code, and sb-config does not honor the CC and CXX environment variables. | |
| Workaround |
On such systems, install GCC and G++ 4.2, and edit the Makefiles to specify
CXX=g++-4.2.
|
|
| SB‑13398 | Filter operators with very large predicate settings may result in a runtime EvalException error. | |
| Description |
Filter operators with several output ports and complex expressions to
evaluate for each port may result in a com.streambase.sb.runtime.exceptions.EvalException error
when attempting to run the application that contains such a filter.
|
|
| Workaround | Add another Filter operator and split the predicate settings between the two Filter operators. | |
| SB‑13303 | Reuters RFA Configuration File wizard appears to not connect under Windows Vista or Windows 7. | |
| Description | Under Windows Vista and Windows 7, you can run the Reuters RFA Configuration File wizard, but the wizard's Test Connectivity page shows a red X and the Test Connection button remains dimmed. | |
| Workaround | This wizard makes changes to the Windows registry, and under the Vista and Windows 7 security model, registry changes require administrator permissions. For these operating systems, use the procedure described in Special Steps for Windows Vista and 7. | |
| SB‑13113 | Application output view does not display UTF-8 characters. | |
| Description | Both StreamBase Server and StreamBase Studio are fully capable of processing and displaying Unicode character sets, but neither is set to do so by default. | |
| Workaround | Follow the instructions in Unicode Support to configure StreamBase Server, Studio, and any StreamBase client applications to process the UTF-8 character set. | |
| SB‑13021 | JDBC database errors related to string lengths. | |
| Description | Due to the removal of string lengths in StreamBase as of release 6.3, some static checking of JDBC table sizes is no longer possible. This can lead to database-specific errors, possibly including data truncation, if a StreamBase application attempts to insert into a JDBC table string values that are too wide for the JDBC table's schema. | |
| Workaround | None. | |
| SB‑12824 | Java and C++ format doubles differently. | |
| Description |
When displaying integer-like values of type double, Java code outputs the
value with a decimal point and zero appended (34.0), whereas C++ code outputs
the same value without those features (34). Thus, the same double values
output to stdout with sbc dequeue and jsbc dequeue are formatted differently.
|
|
| Workaround | None. | |
| SB‑12403 | Pattern operator's error output port is not operational | |
| Description | You can enable an error output port for the Pattern operator as for any operator, using a check box on the General tab of the Properties view. However, such a port for the Pattern operator is not working. | |
| Workaround | None. | |
| SB‑12401 | Clients connecting to sbproxy with misconfigured SSL may hang. | |
| Description | Client applications attempting to make a secure connection to StreamBase Server by means of the sbproxy server may hang if the client or server is not configured to support SSL. | |
| Workaround | Carefully review your SSL configuration setup. | |
| SB‑12136 | On 32-bit Windows, some third-party applications can interfere with StreamBase Server starting. | |
| Description | In recent releases, StreamBase Server is started by default with a requested maximum memory size of 512 or 1024 MB. Certain third-party applications, including Apple's Bonjour program, load themselves in the middle of available RAM, which can prevent StreamBase Server from reserving a contiguous block of memory. | |
| Workaround | You can (1) reduce StreamBase Server's maximum memory size request by adjusting the server configuration file as described in Java VM Memory Settings, (2) remove the competing program, such as Bonjour, or (3) upgrade to a supported 64-bit platform. | |
| SB‑11964 | Case-sensitive Unicode regular expressions require Java 1.6. | |
| Description |
When running StreamBase with Java 1.5, with Unicode support enabled as
described in Unicode Support, the |
|
| Workaround | To have both case-sensitive regular expressions and Unicode support, you must run StreamBase with Java 1.6, which is the default JDK shipped with StreamBase. | |
| SB‑11279 | JDBC Operator, no blob inserts with DB2 and batching. | |
| Description | Due to DB2 driver issues, the JDBC Operator cannot insert blob fields when batching is on. This issue is specific to DB2 and does not affect other supported databases. | |
| Workaround | None. | |
| SB‑11245 | RFA/Java Configuration: Test Connection sometimes fails with RTIC servers. | |
| Description | The RFA/Java Configuration Wizard and Reuters Schema Designer, under certain conditions when used with an RTIC server, fail to access the server. This occurs when using the Configuration Wizard's Test Connection button and the Schema Designer's Discover Services and Start FIDs Lookup tools. | |
| Workaround | None needed. Despite the reported connection failures, the RFA/Java configuration file generated by the wizard is valid and usable by the Reuters RMDS subscribing adapter. | |
| SB‑11117 | Test Editor might not update changes in an open Feed Simulation file. | |
| Description | If a StreamBase Feed Simulation file is modified while a Test Editor is open that references that feed simulation, the Test Editor may not update its contents until it is closed and reopened. | |
| Workaround | Close the Test Editor before editing a Feed Simulation file referenced in the test. | |
| SB‑10983 | Reuters RFA Publishing Adapter not shipped for Linux | |
| Description | Because of a change in C++ libraries, the Reuters RFA Publishing external adapter is not shipped for Linux in StreamBase 6.x or 7.x. | |
| Workaround | Use the new Reuters RMDS Publishing embedded adapter. | |
| SB‑10792 | The Query operator converts a JDBC data type differently when using explicit schemas than when using database data types. | |
| Description |
When explicit schemas are used, the Query operator does not use database
metadata to determine the mapping between JDBC data types and StreamBase data
types. The JDBC data type Types.TIME is normally
converted to an interval timestamp since it has a time, but no date
component. But when explicit schemas are used, there is no database type
information, so Types.TIME is converted to an
absolute timestamp.
|
|
| Workaround | None. | |
| SB‑10486 | Hierarchical data restrictions. | |
| Description | Patterns by value do not support using the tuple data type for their on-value portion. Similarly, tuple subfields cannot be used as the index or primary key of a Query Table. | |
| Workaround | Design schemas so that the intended sort field or key is a top-level numeric or timestamp field, as described in StreamBase Pattern Matching Language. | |
| SB‑10363 | No StreamBase data type corresponding to Sybase timestamp. | |
| Description |
When used with Sybase data sources, StreamSQL fails to convert timestamps,
resulting in typecheck errors. This is because the Sybase timestamp is based on the Sybase varbinary data type.
|
|
| Workaround |
In StreamSQL code that will be used for Sybase data sources, use the
Sybase datetime
data type instead of timestamp.
|
|
| SB‑8698 | Aggregate dimensions do not support advance on infinite dimensions. | |
| Description |
In an Aggregate operator's Properties View, the Dimensions tab includes a
setting for Window Size. One of the size options is Do
not close window based on this dimension. If selected, this dimension
cannot cause the closing of a new window for the Aggregate. If a new window
is never opened, this creates an infinite sized window that never closes (for
the life of StreamBase Server instance). Application designers may set up
this feature, for example, to ensure that an Aggregate processes an entire
day's volume of streaming data. However, a limitation is that Aggregates with
infinite dimensions do not support an Advance value that you set in the
Opening Policy.
|
|
| Workaround | None. | |
| SB‑8640 | Java Operator with zero inputs does nothing. | |
| Description |
While it is not an error to create a Java operator with zero input ports, the
processTuple method will never be called, and
thus the Java operator can never emit any tuples.
|
|
| Workaround | None. | |
| SB‑8297 | Files edited outside StreamBase Studio are not refreshed in Studio automatically. | |
| Description |
For .sbapp and .sbfs files that were created using StreamBase Studio and
are still open in Studio, modifications made using an external editor are not
automatically refreshed in the current Studio Editor session.
|
|
| Workaround | If edits are made outside of Studio and you now want to use the latest file, right-click the project that contains the changes you made and select Refresh. | |
| SB‑7550 | Limit on Feed Simulation Editor fields. | |
| Description | Very large feed simulations with more than about 160 fields can crash StreamBase Studio when you click the Customize Fields button. | |
| Workaround | Limit the size of feed simulations or break large simulations into two pieces. | |
| SB‑7446 |
Starting a StreamBase application fails with a Not
enough space error.
|
|
| Description |
On small systems, StreamBase may run out of virtual memory during the
pre-compilation phase. This is reported as an error message from StreamBase
Server: CompilationException: I/O exception: Not enough
space
|
|
| Workaround | Increase the size of your system's paging file. | |
| SB‑7148 | Invalid byte error when opening EventFlow application. | |
| Description |
Studio sometimes fails to open an EventFlow application with this error:
|
|
| Workaround |
Perform the following steps to recover:
|
|
| SB‑7075 | Changing perspectives can rearrange the Studio toolbar. | |
| Description | The position of toolbar sections can change when you go from perspective to perspective, especially when going from the Authoring to the Demo perspective and back. | |
| Workaround | Eclipse toolbars do not have fixed locations, so this is expected behavior. | |
| SB‑6862 | Not all databases have native blob support. | |
| Description | For example, Microsoft SQL Server and Sybase do not have blob support. For these databases, you can write blobs into varbinary and possibly other types. But when blobs are read from a select statement, they are returned as strings, not blobs. | |
| Workaround | Add a Map operator and convert the string to a blob. | |
| SB‑6346 | Custom function C++ code typechecking is delayed until the application is generated. | |
| Description | Most portions of a StreamBase application are typechecked in real time as you add features to an EventFlow or StreamSQL application. However, starting with release 5.0, typechecking for a custom function written in C++ is delayed until the application is generated and run. | |
| Workaround | None. Be aware that typechecking errors may not be reported as usual when using custom C++ functions. | |
| SB‑6327 | StreamBase Server cannot run applications that generate class files with too long a name. | |
| Description | If you use modules, StreamBase can generate internal class names that are too long for the native file system, causing problems running StreamBase Server. | |
| Workaround | To avoid this problem, use small module reference names and minimize module nesting. | |
| SB‑5882 | Tuple dimensions do not reset counter when another dimension closes a window early. | |
| Description | A tuple-based dimension that closes due to other dimensions (for example, after another dimension times out) does not reset its counter. When this happens, the next window will close based on the total number of tuples received, resulting in a partially full dimension. | |
| Workaround | None. | |
| SB‑5779 | SBAPP-to-SSQL Conversion Assistant resets module parameters to default values. | |
| Description | If you run the SBAPP-to-SSQL Conversion Assistant on an EventFlow application that makes use of module parameter references, the resulting StreamSQL application does not have any module parameter references. They are replaced by their default values. | |
| Workaround | After the conversion, edit the StreamSQL file to add the non-default module parameter values. | |
| SB‑5749 | Feed Simulation Editor's data rate edit and save Issue on Linux. | |
| Description | In StreamBase Studio, the Feed Simulation Editor lets you set the rate in number of tuples per second at which data will be generated for a stream. On Linux only, if you use the keyboard to enter an integer in the Data Rate text box, the new value might not be saved. | |
| Workaround | After clicking into the text box and entering the value, press Enter or change the cursor's focus (for example, press Tab). Then press the Save icon or enter Ctrl+S. Note that if you press Ctrl+S while your cursor is within the Data Rate text box, the new value is not saved. You must press Ctrl+S again. | |
| SB‑5602, SB‑5599 | Embedded Adapters and StreamSQL. | |
| Description |
In StreamSQL applications, you cannot specify that an embedded adapter should
start in a paused state, and you cannot manage
the state of a running adapter in a StreamSQL application (although you can
with EventFlow applications).
|
|
| Workaround | Use an EventFlow application with embedded adapters. | |
| SB‑4931 | SBAPP-to-SSQL Conversion Assistant does not support parallel operators. | |
| Description | If your EventFlow application file has individual operators that are marked for parallel operation, the SBAPP-to-SSQL Conversion Assistant cannot generate equivalent functionality in the generated StreamSQL application because there is no direct analogy for parallel operators in StreamSQL. | |
| Workaround |
After the conversion, if appropriate for your application (no dependencies on
data in other operations), you can use an APPLY
PARALLEL MODULE statement or APPLY PARALLEL
JDBC statement in the StreamSQL file. For details on the APPLY statement, see the StreamSQL Guide.
|
|
| SB‑4854 | Typecheck problem with DB2 JDBC data sources. | |
| Description |
SQL INSERT statements submitted to a JDBC data source in a Query operator or
in an APPLY JDBC statement may pass typechecking even when they contain
errors. This problem was detected only with an IBM DB2 data source.
For example, the following statement passes typechecking even if the named table or fields do not exist in the JDBC data source:
APPLY JDBC DB2 "INSERT INTO mytable (id, name) VALUES({id},
{name})" FROM InStream INTO OutStream;
|
|
| Workaround | Run the StreamBase application. If an error occurs against an INSERT statement, verify that the table name is correct. You can validate the INSERT statement by running it against a test database. | |
| SB‑4559 | Join timeout is not asynchronous. | |
| Description | Join timeout in the Join operator is not asynchronous. That is, the Join operator does not remove a tuple from its buffer until the timeout has passed and another tuple arrives on the same input stream. Tuples received on one input stream do not affect the buffer of the other input stream. | |
| Workaround | None. | |
| SB‑4225 | Some disk drive configurations can corrupt disk-based Query Tables if power fails. | |
| Description | Some caching disk drives do not guarantee the sequencing of disk writes, nor do they guarantee that all the writes to the drive have actually happened. This behavior improves disk performance, but at the risk of data corruption in the event of a power outage or equipment failure. StreamBase is vulnerable to this kind of data corruption if your StreamBase application uses disk-based Query Tables. | |
| Workaround | Disk drives with this behavior usually have a driver-level setting to turn this capability on or off. For example, the driver may present you with a check box labeled Enable write caching on the disk. Unchecking this box would prevent the problem from occurring. | |
| SB‑3955 | Finding sbd process failure details. | |
| Description | When StreamBase Studio runs an application, it launches the server process in the background. If the server process fails for any reason, Studio tries to report the reason to you. However, the actual message that Studio displays may not contain enough information,depending on the failure. | |
| Workaround | To get more information about the reason for the sbd process failure, open the Eclipse Error Log View, as described in Error Log View. | |
| SB‑3585 | Inconsistent support for undo in StreamBase Studio. | |
| Description | Many editing operations in Studio cannot be undone. This includes operations such as copying schemas, editing definitions, editing feed simulations, and so on. | |
| Workaround | The Revert command in the File menu can be used to undo all changes since the last time a file was saved. | |
| SB‑3260 | Using non-member Schema.Field to access a tuple does not throw a useful exception. | |
| Description |
The StreamBase Client library does not throw a useful exception if you
inadvertently reference the wrong schema while using Schema.Field to access a Tuple. Under
C++, no exception is thrown and memory corruption may occur. Under Java, an
ArrayIndexOutOfBoundException is thrown.
This applies both to using fields from other schemas, or to using the Field objects that were used to create the Schema. Fields that are used to create a schema are not fully initialized, and so you must get the actual Field from the new Schema object in order to access the fields of a Tuple. |
|
| Workaround | None via the API. You must examine your client code and verify that the correct Schema is referenced. | |
| SB‑2931 |
Relocatable RPMs install incorrect symbolic links in /usr.
|
|
| Description |
The Linux RPM packages are relocatable. This means that the default
installation location of /opt/streambase can be
changed to a different location. However, if this is done, symbolic links are
still installed in /usr/bin and /usr/lib that point to /opt/streambase.
|
|
| Workaround | Either edit the symbolic link by hand, or use the archive file installer instead of the RPMs to install StreamBase on Linux. | |
| SB‑2507 | Java Client library IOException when client program is suspended. | |
| Description |
A program using the StreamBase Java Client library may receive an unexpected
IOException if it is suspended (using either Ctrl+Z, or kill
-SIGSTOP). The IOException is thrown when the program is resumed, or
placed in the background. The exception may be thrown even if there is no
network traffic at the time. This issue does not apply to Windows systems.
|
|
| Workaround | Do not suspend StreamBase clients written in Java. | |
| SB‑1969 | StreamBase Studio on Windows triggers Windows firewall when running Server. | |
| Description | Users of StreamBase Studio on Windows may find that the Windows Firewall, or a third-party firewall product, prompts for permission to continue when first starting StreamBase Server. The message may refer to javaw or to StreamBase Server by name. This is expected behavior of Windows firewalls. You must grant the requested permission in order to continue using StreamBase Server on this machine. | |
| Workaround | After granting permission once, you should not be prompted about this again. | |
| SB‑1769 |
LockDirectoryException error encountered when
starting StreamBase Server.
|
|
| Description |
There may be a number of cases when you would encounter the
LockDirectoryException error. If the message indicates File exists, either another instance of StreamBase Server is
currently running or the prior instance of Server was improperly shut down.
|
|
| Workaround |
If another StreamBase Server instance is running, change the server
configuration file to point the datadir element
to a different directory. If there is no other Server instance running, you
must manually delete the directory named in the File
exists message.
|
|
| SB‑1289 | IPv6 addresses not supported. | |
| Description | StreamBase Server can only connect to IPv4 addresses. If you try to connect using IPv6 addresses, the connection is refused. | |
| Workaround | None. | |
| SB‑1164 | Issues with certain older Linux kernel versions. | |
| Description | Linux kernel versions 2.6.8-10 have a known bug in their thread handling code. This bug can cause sbd to exit immediately after servicing its first client request. For more information, see http://www.ussg.iu.edu/hypermail/linux/kernel/0410.2/1650.html. | |
| Workaround | This bug was fixed in Linux kernel 2.6.11. This does not affect the Linux distributions currently supported by StreamBase. If you are running an older kernel in the 2.6.8-10 range, then set the environment variable STREAMBASE_IGNORE_SIGHUP=1 to work around this problem. Set the variable in the login environment in which StreamBase Server will run. | |
| SB‑1039 | C++ code is not binary compatible between releases. | |
| Description |
If you use either the C++ Client library, plug-in functions, or plug-in
aggregates, you must recompile them from source in order to use them in each
new release. Without recompiling, StreamBase returns an error message at
runtime.
bin/sbd: error while loading shared libraries ... cannot open shared object file: No such file or directory |
|
| Workaround | Recompile your C++ code from your original source against the new headers. | |
| SB‑804 | init.d script uses a hard-coded port number. | |
| Description |
UNIX only. If you change /opt/streambase/etc/sbd.sbconf to point to a port other
than 10000, then the stop, restart, and status commands in
the /etc/init.d/streambase script do not work
as expected. Those commands assume that sbd is running on port 10000.
|
|
| Workaround |
Edit the commands in the /etc/init.d/streambase
script to use the -p option, to force sbd to run on the same port specified in
the modified sbd.sbconf file.
|
|
| SB‑765 | Clients that exceed page limit buffer size disconnect with no explanation. | |
| Description | When a StreamBase client exceeds its maximum number of pages (for example, because it's not dequeuing fast enough to keep up with the rate at which tuples are being generated), StreamBase Server disconnects the client and prints a message saying that it has done so. However on the client side, no error is reported. Instead, it looks like an unexplained dropped connection. | |
| Workaround |
Edit the server configuration file for the Server that processes your
application, and increase value of the max-client-pages parameter.
|
|