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.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‑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.
|
| Fixed in 7.1.7 | |
|---|---|
| Number | Resolution |
| Release 7.1.7 incorporates all fixes resolved 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.0.x and Limitations Resolved in 6.6.x for details. | |
| SB‑21880 |
An error in the Aggregate operator was causing expressions such as
firstval(input1).* to run
out of code size too soon. This was corrected.
|
| SB‑21799 | The error message caused by exceeding the maximum input packet size was clarified and improved. |
| SB‑21768 | The schema for the status port of the FXall Relationship Trading Provider adapter was optimized to use current StreamBase APIs. |
| 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.1.6 | |
|---|---|
| Number | Resolution |
| Release 7.1.6 incorporates all fixes resolved 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.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‑21700 |
It is valid to create a StreamBaseClient
instance as part of an sbunit test, and subscribe to an output stream or
enqueue to an input stream from that client. In previous releases, if you
stopped and restarted containers while this client was connected to the
server under test, the client failed to reconnect. This was corrected.
|
| 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‑21602 | An exception that could occur during initial connection using the Deutsche AutobahnFX Trading System adapter was fixed. |
| SB‑21583 | A null pointer exception that could be thrown during typechecking of SQL statements in a Query-JDBC operator was corrected. |
| SB‑21277 | A condition where a Union operator in a module in a loop could drop tuples was identified and corrected. |
| Fixed in 7.1.5 | |
|---|---|
| Number | Resolution |
| Release 7.1.5 incorporates all fixes resolved 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.0.x and Limitations Resolved in 6.6.x for details. | |
| SB‑21499 |
When using parameters in a server configuration file to specify data source
information, the JDBC Data Construct did not preserve parameter notation
such as ${ds} typed in the JDBC Data Source field. This was corrected.
|
| SB‑21493 | In previous releases, a disabled output stream could still update an associated dynamic variable, or prevent the module from compiling. This was fixed such that dynamic variables that depend on a disabled output stream are not updated. |
| SB‑21467 | When your selected the Skip this page next time option for the StreamBase Component Exchange dialog's legal panel, that panel still appeared on subsequent invocations of the dialog. This was fixed. |
| SB‑21438 | In previous releases, a port on which to run StreamBase Server specified in a server configuration file was honored for standard uses but ignored when running the same application as an embedded server as part of the StreamBase JUnit test framework. This was corrected. |
| SB‑21434 | If you renamed more than one canvas group in the same editing session, Studio was preserving only the last group rename, resulting in groups not appearing the next time you opened that module. The cause was found and corrected. |
| SB‑21398 | A formatting error that exposed an unexpanded {0} format placeholder in a typecheck message string was corrected. |
| SB‑21321 | Opening an EventFlow module from Subversion history or from the repository browser view would result in a ClassCastException error. This was corrected. |
| SB‑21179 | After running Studio's Zoom to Fit option, some arcs became misaligned and appeared to not quite touch the input port of the following component. This was corrected. |
| SB‑21100 | Using Studio's Layout application command could result in unexpected arc placements, sometimes taking paths far out of the way to arrive at the adjacent component. The cause was identified and fixed. |
| SB‑20577 | The maximum width of schemas was approximately doubled to avoid RuntimeException errors when attempting to compile applications with very wide schemas. The maximum width is around 2000 fields, but the exact number of fields that triggers this error condition depends on many factors, including list fields (whose member count is not known until actual use) and the presence and depth of nested fields. |
| SB‑19956 | The Trace Debugger in Studio could show doubled stream entries in the Search chooser. 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 did provide 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.
|
| Fixed in 7.1.4 | |
|---|---|
| Number | Resolution |
| Release 7.1.4 incorporates all fixes resolved in the release 7.0 series through release 7.0.10, and in the release 6.6 series through release 6.6.16. See Limitations Resolved in 7.0.x and Limitations Resolved in 6.6.x for details. | |
| SB‑21249 | When importing multiple table schemas that used private schemas from the same file, a Query Table could pick up an incorrect schema. This was fixed. |
| SB‑21198 | In previous releases, a Stack Overflow Error could be thrown while bundling an application contained in a project with inadvertently circular project references. The bundler was updated to better handle these conditions. |
| SB‑21161 | The Thomson Reuters RMDS Subscribing Input adapter, configured to process market feed and emit thin tuples, if it encountered an enumeration field with an invalid value, it generated an exception. This was fixed. |
| SB‑21158 | Certain applications that use large schemas that were successfully compiled by StreamBase Server 7.0.x were failing to compile with 7.1.x. This was corrected. |
| SB‑21116 |
The rfa.jar library provided by Thomson
Reuters was causing a Null Pointer Exception error when the library
received a STATUS_RESP message that did not contain status state for the
item stream. This error was corrected by upgrading the rfa.jar version shipped with StreamBase from
7.0.0 to 7.0.1.E4.
|
| SB‑21114 | In previous releases, using the Extract as Module command in the EventFlow Editor could result in several duplicate placeholder tables in the extracted Module Reference. This was corrected. |
| SB‑21098 |
In previous releases, when using an Edit Schema tab in the Properties view,
Studio could throw a Stack Overflow Error that referred to java.util.TreeMap when adding a field to a multilevel
schema. This was fixed.
|
| SB‑21096 |
The use of xi:include in a server
configuration file was not working as expected when sbd -f sbd.sbconf ... was run from a
directory with spaces in its name. This was corrected.
|
| SB‑21087 | Studio was leaking memory by leaving instances of the EventFlow Editor in the heap under certain circumstances. The cause was identified and corrected. |
| SB‑21085 | A corner case for unsupported, custom-generated application XML that passed typechecking in previous releases became invalid in StreamBase 7.x. StreamBase was updated to handle these cases. |
| SB‑21080 | When using the FIX Schema Designer, FIX fields of type UTCTimestamp, UTCDate, UTCDateOnly, UTCTimeOnly, Time, and LocalMktDate are now correctly mapped as StreamBase timestamp fields instead of int fields. |
| SB‑21058 | The popup Edit Expression dialog was not available when editing a dispatch expression for a Numeric dispatch style instance in the Concurrency tab of the Properties view for any component. This was corrected. |
| SB‑21056 | Studio could throw a Null Pointer Exception when you edited the named schema that defined a Query Table shared between parent and child modules. This was corrected. |
| SB‑21047 | Changes in interface files defined in one project were not causing Studio to rebuild modules in projects that referenced that project. This was fixed. |
| SB‑21044 | In previous 7.1.x releases, the interface editor would display an error when you created a new interface with a table schema that uses a private schema. This was corrected. |
| SB‑21020 | Using the EventFlow Editor's Extract as Module command followed by Undo was resulting in a Null Pointer Exception. This was fixed. |
| SB‑21007 | In previous releases of the EventFlow Editor, on a canvas with one Query Table and two unconnected Query operators all in vertical alignment, if the cursor passed over Query1 when dragging an association arc from the table to Query2, the arc connection would be grabbed by Query1. This was fixed. |
| SB‑20969 | Using the Extract as Module command in the EventFlow Editor could result in duplicate module parameters, which cause the extracted module to silently fail typechecking, leaving a Null Pointer Exception in the Error Log. This was corrected. |
| SB‑20960 | Several customer-reported Java errors thrown by Studio were corrected. These include Null Pointer Exceptions and Unhandled event loop exceptions seen while editing schemas and table schemas. |
| SB‑20944 | In previous 7.1.x releases, when using the Query operator with a JDBC data source and setting the explicit schema for the result set expected from a call to a stored procedure, the schema setting was not preserved when the module was saved. This was corrected. |
| SB‑20937 |
An issue in the IBM WebSphere MQ adapter with parsing XML messages into
tuples was corrected. Fields containing XML escape sequences such as
A & B were
inadvertently truncated, populating the tuple field with A instead of A & B.
|
| SB‑20889 | The Gather operator was updated to accept more than 31 incoming streams. |
| SB‑20867 | Using a Query operator configured to output no rows from the query, but also configured with a group-by clause, would halt StreamBase Server with an XmlRpcManager exception. The cause was found and fixed. |
| SB‑20859 | There were certain cases of dragging a module from the Package Explorer view to the canvas to form a Module Reference that worked in 6.6.x releases, but not in 7.x releases. The cause was identified and fixed. |
| SB‑20856 | Error messages returned from a failure of an sbadmin modifyContainer removeConnection command were updated to provide more information about the failure. |
| SB‑20808 |
When using the Query operator associated with a JDBC data source, calls to
certain stored procedures would return a No result
set error. The operator was updated to handle these conditions
without an error return, and the Result Settings tab documentation was updated to clarify
that you do not need to specify a schema for stored procedures if no result
set is expected.
|
| SB‑20804 | When reading a compressed input file, the Binary File Reader adapter was throwing a spurious WARN message about a protocol version mismatch. The adapter was updated to suppress this message. |
| SB‑20725 | CPU intensive modules with loops that were designated to run in multiple concurrent threads would exhibit unfair sharing of CPU resources on multiple CPU machines. This was corrected. |
| SB‑20703 | In the Data File Options dialog of the Feed Simulation Editor, StreamBase disallowed selecting Timestamp builder in the Map to file column if the First row as header check box was selected. This unnecessary restriction was removed. |
| SB‑20598 | Container connections specified in a StreamBase deployment file were not always started in the specified order, which could prevent some connections from occurring in a multiple sbd environment. This was fixed. |
| SB‑17816 | In previous releases, a custom simple function that returns void caused a Null Pointer Exception. This condition was corrected to report a typecheck error. |
| Fixed in 7.1.3 | |
|---|---|
| Number | Resolution |
| Release 7.1.3 incorporates all fixes resolved in the release 7.0 series through release 7.0.8, and in the release 6.6 series through release 6.6.14. See Limitations Resolved in 7.0.x and Limitations Resolved in 6.6.x for details. | |
| SB‑20772 | The Interactive Data PlusFeed Input adapter could produce a Java error message instead of timing out when the adapter or the containing StreamBase Server was shutting down. This condition only affected the adapter in releases 6.6.14, 7.0.7, 7.0.8, and 7.1.2, and was corrected as of this release. |
| SB‑20768 | Under certain circumstances, Studio could unnecessarily rebuild workspace projects more than necessary on changing project properties for a given project. The underlying cause was identified and corrected. |
| SB‑20758 | The TBF adapter was emitting a null pointer exception when its recovery session did not have a matching feed reconnect session. This was fixed. |
| SB‑20676 | The Query operator used with a JDBC Table data source was not saving explicit schemas correctly. This was fixed. |
| SB‑20642 |
In the Java Client Library, the internals of the SBServerManager and Dequeuer interfaces in the sb.unittest package were reworked to provide faster
dequeues.
|
| SB‑20605 | In previous releases, the TBF Input adapter could stop processing retransmit requests if messages arrived out of order on the multicast feed. This was fixed. |
| SB‑20585 |
The expression language's strptime() function now supports the %p format specifier, which parses an AM/PM specifier in
accordance with the current locale.
|
| SB‑20565 | An internal class was producing an error when included in debug output that was run with an elevated log level. This was corrected. |
| SB‑20559 | In previous releases, adapters that use a file resource property would re-dirty the containing module immediately after saving the containing module in Studio. This was fixed. |
| SB‑20521 |
As before, StreamBase Systems does not recommend overriding
the Operator.getName() method. However,
StreamBase internals are now protected from the consequences
if your application requires doing so.
|
| SB‑20517 | When the Studio preference setting Use middle mouse button to scroll instead of pan was selected, clicking with the middle mouse button in the EventFlow Editor would sometimes select an arc instead of scrolling. This was corrected. |
| SB‑20506 |
In the Containers tab of the Launch Configuration dialog, Studio
inadvertently allowed changing the name of the container named default, despite Studio requiring the primary application
module to run in default. Changing the name of
the default container is now disallowed in
that dialog.
|
| SB‑20473 | The Reuters Schema Designer feature lost its ability to connect to RFA6 servers after a recent update of the Reuters libraries. The cause was found and fixed. |
| SB‑20408 | The EventFlow Editor in Studio could flicker and redraw excessively after deleting many operators. The cause was found and fixed. |
| Fixed in 7.1.2 | |
|---|---|
| Number | Resolution |
| Release 7.1.2 incorporates all fixes resolved in the release 7.0 series through release 7.0.7, and in the release 6.6 series through release 6.6.14. See Limitations Resolved in 7.0.x and Limitations Resolved in 6.6.x for details. | |
| SB‑20614 | In previous releases of the FIX adapter (and all adapters based on it) when using the QuickFIX/J FIX engine, tuples with a non-null list field representing a repeating group could be converted into a FIX message where the group's NumInGroup field would have a value of zero. This was corrected. |
| SB‑20550 | In the Thomson Reuters RMDS Subscribing Input adapter, OMMData values with attribute isBlank=true are now discarded. |
| SB‑20512 | Implicit type coercion from long to double was unnecessarily strict, and was prevented in some cases by the Server runtime after Studio allowed the conversion. The rules for long to double coercion were relaxed. |
| SB‑20495 | Table schemas using named schemas were not being correctly added to applications when implementing an interface. This was fixed. |
| SB‑20469 | Module-scoped dynamic variables were not correctly recognized in operator expressions. This was fixed. |
| SB‑20466 | In previous releases, when using a Query read or delete operation on a Query Table, if you specified a group-by field and then used that same field as part of an aggregate output expression, the Query operation could result in an error. This was corrected. |
| SB‑20397 | An issue with the sorting of the names of named schemas was fixed. |
| SB‑20391 | The feed simulation for the RTD sample included with the StreamBase Adapter for Microsoft Excel had two columns out of order. This was corrected. |
| SB‑20325 | An earlier fix, SB-19792, uncovered a conflict between Studio and certain adapters, including the TIBCO Subscribing Input adapter, that were using older classloaders. The cause was identified and fixed. |
| SB‑20321 | A StackOverflowError was sometimes generated when saving portions of the Trading System Framework as a StreamBase bundle. This was fixed. |
| SB‑19883 | Modules that implement an interface underwent unnecessary typechecking whenever any other module or interface file was saved. This was fixed. |
| SB‑19875 | JMS embedded adapters were incorrectly handling white space in CDATA values in their configuration files. This was corrected. |
| Fixed in 7.1.1 | |
|---|---|
| Number | Resolution |
| Release 7.1.1 incorporates all fixes resolved in the release 7.0 series through release 7.0.6, and in the release 6.6 series through release 6.6.13. See Limitations Resolved in 7.0.x and Limitations Resolved in 6.6.x for details. | |
| SB‑20345 | A deadlock issue in the JMS adapter was detected and fixed. |
| SB‑20330 | The data dictionary for the Currenex adapter was updated to more accurately reflect the latest Currenex specification. |
| SB‑20300 | In some circumstances, the static evaluation feature added in release 7.1.0 was inadvertently changing -0.0 to 0.0 in expressions. This was corrected. |
| SB‑20299 |
The StreamBaseFIX FIX engine was updated with a mechanism to
specify FIX message storage policy on a per-session basis. New settings in
the adapter configuration file for the FIX adapter (and all
StreamBase adapters that use the StreamBaseFIX
engine) are <storage-factory> and
<storage-directory>. These settings
supercede the similar settings in the properties file, which allows per
session settings.
|
| SB‑20287 | The FIX adapter, and all StreamBase adapters that use the QuickFIX/J FIX engine, were updated to correct a problem in the engine whereby an output adapter would write out the fields of a repeating group in the order in which they appeared in the StreamBase schema instead of the order of the data dictionary. |
| SB‑20286 | A NullPointerException error could be emitted from the StreamBaseFIX FIX engine when parsing a FIX message with repeating groups. This was corrected. |
| SB‑20238 | In some instances, the QuickFIX/J and StreamBaseFIX FIX engines were not correctly handling the LOCALMKTDATE FIX data type. The cause was identified and corrected. |
| SB‑20210, SB‑18957 |
In the output of the statv2 stream, and therefore also in
StreamBase profiling reports, the hyphen+greater-than symbols
(->) on Queue information lines that
represents the division between the two sides of a queue, was changed to
two colons (::). This makes profiling report
information easier to export to XML format without special handling of the
> symbol.
|
| SB‑20200 | Tooltips displayed by hovering over an EventFlow canvas component sometimes remained on the screen after closing Studio. This was corrected. |
| SB‑20198 | In 7.1.0, when designating a generation method for a stream with an empty schema, clicking the Data File Options button in the Feed Simulation Editor resulted in an IndexOutOfBounds error. Starting with 7.1.1, the Data File Options dialog now opens, which allows you to specify a single column of timestamp data in such a file, for use with the Timestamp from column feature of the same dialog. See Using Timestamp from Column with Empty Schemas. |
| SB‑20175 | Studio selects, centers, and highlights the EventFlow component containing a search string found by Eclipse File Search, as described on Text Search in Studio. In previous releases, this feature failed to apply to Notes or text in Notes; this was corrected. |
| SB‑19869 | In previous releases, setting an explicit schema on an arc was not undoable in Studio. This was corrected. |
| Fixed in 7.1.0 | |
|---|---|
| Number | Resolution |
| Release 7.1.0 incorporates all fixes resolved in the release 7.0 series through release 7.0.5, and in the release 6.6 series through release 6.6.12. See Limitations Resolved in 7.0.x and Limitations Resolved in 6.6.x for details. | |
| SB‑20126, SB‑19909 | EventFlow Debugger: the blue highlighting for the current component was sometimes lost. This was fixed. |
| SB‑20047 | The FIX adapter, and all StreamBase adapters that use the QuickFIX/J FIX engine, were updated so that log files that store the last sequence number of received messages are now correctly closed when the adapter exits, which allows deletion and cleanup of such files without shutting down StreamBase Server. |
| SB‑19983 | EventFlow Debugger: stepping into a Filter operator could sometimes cause previously visited (and blue-highlighted) components to lose their highlighting. This was corrected. |
| SB‑19626 |
When using → from the Package Explorer view's context menu to
move an EventFlow file to another project folder, any associated
.sblayout file was sometimes not moved at the
same time. This was corrected.
|
| SB‑19592 |
Special treatment of a Studio project subfolder named Resources was removed in release 6.4.0. As of release
7.1.0, special treatment of a Resources
subfolder was removed from the sbfeedsim command as well.
|
| SB‑19420, SB‑19392 | In trace files, any blob fields are now hex encoded strings for better display. The Trace Debugger was updated to interpret and display hex encoded strings. |
| SB‑19202 | For Studio on Linux, the Reroute Arcs function's keyboard shortcut was changed to Shift+L. Studio's keyboard shortcut on Windows for that function is Ctrl+Alt+L, but on Linux using a Gnome-based desktop, that key combination locks the screen by default. |
| SB‑18943 | The keyboard shortcut Ctrl+Shift+B to toggle breakpoints on and off arcs was working in sequence if you had multiple arcs selected. This was corrected to toggle all selected arcs at once. |
| SB‑18787 | Attempting to set an explicit private schema for the result set on |
| SB‑18572 |
EventFlow Group information was moved from the XML stored in .sbapp files to .sblayout
files. The content of Notes remains in the .sbapp file, since Notes are effectively comments.
|
| SB‑17223 |
Precompiled archive files (.sbar) might
include a JDBC connection specification in the server configuration file of
the project being archived. In previous releases, an archive generated on a
build machine with a JDBC connection to a test JDBC database, would fail to
validate when run on a production server with a JDBC connection to a
different JDBC database. Starting with release 7.1.0, the tests for JDBC
configuration settings in an archive file were relaxed, which allows you to
configure separate test and production JDBC servers, as long as the
data-source name is the same. The
archive test also looks for identical quote strings, stored procedure
return type, batch size and can-reconnect specifications, but no longer
tests for machine-specific settings such as username and password, or the
server name in the JDBC connection string.
|
| SB‑16983 | A limitation where replicated Query Tables could not have field names that were StreamSQL reserved words was fixed. |
| SB‑15943 | The Property view in Studio can now display error and warning messages whose text occurs over multiple lines. |
| SB‑13159 | In previous releases, clicking the Home button in the standalone Help viewer opened a generic page on how to use Eclipse Help. This was corrected to open the home page of StreamBase documentation. |
| SB‑11979 | In a SQL statement specified in a Query operator connected to a JDBC data source, escaped curly braces were sometimes not interpreted correctly. This was fixed. |
| SB‑7389 |
Under some circumstances, an interval()
function such as interval("09:30:00") did not compile to a constant in a
compiled application. This was corrected to compile to a constant when
possible, with rare exceptions caused by the operating system's time zone.
|
| SB‑2547 | In previous releases of the Client Library, when buffering enqueues from more than one stream, tuples could arrive out of order. StreamBase clients now maintain tuple order the same with enqueue buffering enabled as disabled. With buffering enabled, if the enqueue buffer fills up, further writes to the server are done on a separate thread. |
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‑21843 | In the TableAccessor API, ClassCastException thrown if not using 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‑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‑19319 | Default location for explicitly included resource files in a bundle changed between releases 7.0.3 and 7.0.4. | |
| Description |
Release 7.0.3 contained an unannounced early release of the ability to
explicitly include resource files in a StreamBase bundle, using
sbbundle --include or the
Bundler project properties page in Studio.
In 7.0.3, files specified using the Bundler project properties page were
placed automatically at a path in the bundle that corresponded to the path
each file had relative to the Studio project root. Starting with release
7.0.4, Studio allows you to specify the target path in the bundle for each
entry, or you can elect to use the StreamBase default, the
bundle's |
|
| Workaround | Recreate in release 7.0.4 or later any bundle files you created in 7.0.3 that took advantage of explicit resource file inclusion. | |
| 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‑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‑14475 |
Entry in Studio Error Log view: Problems occurred when
invoking code for plug-in: "org.eclipse.ui.console".
|
|
| Description | The Error Log view in Studio might show an entry with the above description text and a stack dump that begins with org.eciipse.swt.SWTException: Device is disposed and includes lines early in its stack dump that refer to org.eclipse.swt.widgets.* and org.eclipse.ui.internal.console*. The source of this error is a known Eclipse problem and can be safely ignored. It does not affect the operation of Studio in any way. | |
| Workaround | None needed. | |
| 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‑14107 |
Entry in Studio Error Log view: error occurred while
unconfiguring items to uninstall.
|
|
| Description | Since release 6.4.0, an entry might be placed in the Eclipse Error Log view when you try to install third-party Eclipse plug-ins to Studio. The source of this error is a known Eclipse problem, Eclipse bug ID 279024. | |
| Workaround | Exit Studio, remove the Eclipse configuration directory (not your workspace directory), then restart Studio. The location of the configuration directory for your StreamBase version is described in Default Installation Directories. | |
| 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‑11152 | Error message shows on wrong Properties view tab for the Aggregate operator. | |
| Description | When setting up an Aggregate operator with a group option, some typechecking error messages show only in the General tab, not the Group Options tab where the error occurred. | |
| Workaround | None. | |
| 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‑6984 | Actions unavailable when all folders are selected. | |
| Description | After you collapse a Group in the EventFlow editor, selects all the items in the group. However, actions performed on the group do not succeed. For example, does not delete the items inside a group. | |
| Workaround | Uncollapse the group before performing the action. | |
| 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‑6356 | Large applications cannot be debugged in StreamBase Studio. | |
| Description | When running an application in debug mode in StreamBase Studio that contains many operators (in the range of hundreds, including all modules), it is possible to cause Studio to display and log an error message about running out of handles. The error message may vary, but the symptom is that Studio is unable to display all the intermediate streams in the Application Output View or the Manual Input View. | |
| Workaround |
Limit the number of output streams the application will expose when running
in debug mode, by setting the server's JVM property to include the following:
For example, setting the JVM arguments to include: |
|
| 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‑6241 | When an application is running in StreamBase Studio on Windows, the Manual Input view and other views can lose details. | |
| Description | This is a known Eclipse bug. The problem occurs when you use the tab key. Borders around fields, other decorations, and some controls can disappear. | |
| Workaround | Minimize and then maximize the window, or resize the affected view. | |
| 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‑5848 | Issue with parameterized modules and custom Java operators or embedded adapters. | |
| Description | In EventFlow applications, you cannot enter references to parameterized modules in custom Java operators or embedded adapters. This is due to a GUI limitation, currently under investigation, that prevents you from entering the required values. | |
| Workaround |
Embed your custom Java operator or custom embedded adapter in a
StreamSQL-defined module (see the APPLY MODULE
statement in the StreamSQL
Guide), and use an EventFlow module reference, through which you
optionally share parameter values.
|
|
| 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‑4625 | Spurious typecheck error when saving changes to a data construct associated with an operator. | |
| Description | In some circumstances StreamBase Studio generates a typecheck error with a message to remove a row that you cannot remove because the row is not displayed in the Properties view. This can occur when you have edited a data construct associated with an operator and then attempt to save the changes. | |
| Workaround | You can work around the typecheck error by forcing StreamBase Studio to reread your changes. For instance, cut and paste an existing row, or change one character and change it back. | |
| 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‑4160 | JVM crash during StreamBase application compilation. | |
| Description | When StreamBase Server first loads an application, it compiles it to Java code using the Sun Java compiler. Some StreamBase applications can cause the Sun Java compiler to crash during this phase. If this happens, StreamBase Server displays a stack trace that mentions OopFlow::build_oop_map. StreamBase is pursuing this issue with Sun, but in the meantime if you encounter this issue, contact StreamBase Systems for assistance in modifying your application to avoid the error. | |
| Workaround | Make slight changes to your application until the error no longer occurs. We are unfortunately unable to provide guidance about what specific changes to make. | |
| 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 renaming operators, editing Query Tables, copying schemas, adding operators from the Palette, 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‑3121 | Linux only: Firefox issue with StreamBase Studio Welcome page and Help. | |
| Description | On Linux, the StreamBase Studio Welcome page and Help require that Mozilla or Firefox is installed and can be located. If you removed Mozilla, or installed it in a non-standard location, or moved it, the Welcome page or Help may not appear. | |
| Workaround |
Before using Studio, set the environment variable MOZILLA_FIVE_HOME to the path of your Firefox installation.
For example, on Linux, set it to:
MOZILLA_FIVE_HOME=/usr/lib/mozilla-<
|
|
| 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‑2891 | Error messages while creating Java operators lack detail. | |
| Description |
Any exceptions during the creation of a Java operator from within
StreamBase Studio will result in a Can't
make new object: (operator name) message, with no additional
information.
|
|
| Workaround | Run the application in sbd directly for additional diagnostic information. Verify the correct JAR files are specified in your project's Custom Libraries. Verify the classes are in the JAR files. Verify that the manifests of the JAR files are correct. For more information, see Creating Java Clients. The error log may have additional diagnostics. | |
| SB‑2617 | For Java operators and modules, typechecking may occur regardless of connections. | |
| Description |
Java operators and modules are typechecked independently of their connections
to other components. For modules, this may result in errors that do not
clearly describe the problem. For example, if you have an application
containing a module with its inputs connected, then delete an input stream
that the module references, and then return to the referencing application,
the arc (connection) will be dropped. However the following typecheck message
will appear: Error in referenced application:
<input> lacks required attribute 'stream'.
|
|
| Workaround | None. | |
| 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‑2482 | Data sent to multiple streams may get out of order. | |
| Description | StreamBase Server does not preserve the relative ordering of input tuples received on different input streams. This affects the Client library, if tuples are enqueued to different streams. | |
| Workaround | In some cases you may be able to use a Merge operator to reorder your input data. However, note that the Merge operator can block in some situations and therefore may not be appropriate. In general, it is best to avoid sending data to different input streams in the first place, if the relative order of tuples on those streams must be preserved. | |
| 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‑806 | Explicitly-provided schema in loops are order sensitive. | |
| Description | If you use a loop, the order of the fields in your explicitly-provided schema must match that of the output schema. Otherwise you will get a typecheck error indicating that your explicitly-provided output schema does not match your actual output schema. | |
| Workaround |
Click on the loop arc, then in the Properties view click the option:
Update using the schema that StreamBase Studio detected
on one of the Union input ports. This action rearranges the order of
the explicitly-provided schema to match that of the input schema. You can
also manually change the order of the fields using the Properties View for
the loop arc.
|
|
| 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.
|
|