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 Windows C:\Program Files\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.
-
Take note of the following issues in the current StreamBase release.
For any 6.x release, if you have installed any preview release of StreamBase Studio on your computer, you must reset your perspectives in both StreamBase Studio and StreamBase Manager to pick up the changes in the final release.
In both StreamBase Studio and StreamBase Manager, invoke → . For StreamBase Studio, do this in all Studio perspectives including SB Authoring and SB Test/Debug.
Recent releases of StreamBase Studio use an Eclipse workspace format that is incompatible with the workspace from the 3.x release series. When a current release of Studio is first started, and it prompts for the location of its workspace, use the default location or specify a new, empty directory. Do NOT specify the location of a StreamBase Studio 3.x workspace.
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 6.5.4 | |
|---|---|
| Number | Resolution |
| Release 6.5.4 incorporates all fixes resolved in the release 6.4 series through release 6.4.12. See Release Notes for StreamBase 6.4.x for details. | |
| SB-16424 |
In previous releases, precompiled archive files (.sbar files) generated on Windows with the
sbargen command would
sometimes fail to run when moved to a Linux host. This problem was
identified and corrected.
|
| SB-16413 |
In previous releases, setting the Java system property streambase.queue-flush-interval to 0 to minimize latency
in client connections could result in dropped tuples. This was corrected.
|
| SB-16397 |
In custom code using the StreamBase Client API, when
performing a field lookup that involves two schema objects, a DEBUG message
was emitted at runtime warning that "Tuple.resolveField had to compare schemas slowly." This
was fixed.
|
| SB-16377 | The Windows installer was installing registry keys that are no longer used by StreamBase, including LogFile, LogLevel, LogToLogFile, CrashDump, CrashQuiet, and CrashPause. The installer was updated to stop installing those registry keys. |
| SB-16358 | In previous releases, when an application module was saved and another editor contained an application referencing the saved module file, Studio would not re-typecheck the module reference, and thus would not reflect schema changes on the module reference's output ports. This was corrected. A side effect of this fix is that you may see application editors that dirty themselves more often after a module they reference is saved. This is normal and is designed to ensure every application is up-to-date. |
| SB-16221 | Typecheck efficiency was improved throughout StreamBase Studio for cases such as adding an arc, inserting operators onto existing arcs, and when using the Quick Connect feature. |
| SB-16181 |
In StreamBase 6.3 and 6.4, a running StreamBase
Server was seen in operating system process listings as sbd-java[.exe]. This feature was inadvertently disabled
in 6.5.0, but is now restored in 6.5.4.
|
| SB-16143 | In 6.5.x releases before 6.5.4, the Trace Debugger failed to display the values for the first row in the table. This was fixed. |
| Fixed in 6.5.3 | |
|---|---|
| Number | Resolution |
| Release 6.5.3 incorporates all fixes resolved in the release 6.4 series through release 6.4.10. See Release Notes for StreamBase 6.4.x for details. | |
| SB-16182 | When using the automatic table replication feature, the container designated as LEADER would send the NON-LEADER two messages (a delete, then an insert) to designate a table update, potentially leading to lost data in a failover event. This was corrected to send update messages as a single, atomic update event. |
| SB-16162 | In previous releases, moving the downstream end of an arc exiting from a collapsed group on the EventFlow canvas could cause Java errors. Starting with release 6.5.3, you can no longer move such an arc while the group is collapsed; uncollapse the group first. |
| SB-16170 | An error converting the Query operator from 6.4 format to 6.5 format was corrected. |
| SB-16150 | Previous 6.5.x releases could generate a Java error when using a named schema as a declared schema for an output stream. This was fixed. |
| SB-16174 | The CSV File Writer adapter would sometimes throw a FlushTask error when resumed from suspended state. The cause was identified and corrected. |
| SB-16093 |
Studio could inadvertently double the parallel
parameter in the EventFlow XML in cases where two Query operators were both
marked to run in separate threads. This was fixed.
|
| SB-16071 | The previous version of the → and → dialogs were inserting a different adapter than the one selected. This was corrected by providing new dialogs to perform these functions, as described in EventFlow Keyboard Shortcuts. |
| SB-16065 |
In previous 6.5.x releases, the clientapi.jar
file (the file that implements the StreamBase Client API build
path library) inadvertently excluded the SLF4J classes. This caused
compilation errors for custom Java code that accessed classes such as
Logger. This issue was resolved.
|
| SB-16045 | In previous releases, the feed simulator, when used with a CSV input file, could incorrectly collapse adjacent columns when the delimiter was tab or space. This was corrected. |
| SB-15452 | The Threads view in the sbmonitor application occasionally showed inaccurate CPU time statistics because operator or adapter Runnables that used the RegisterRunnable interface were registered with the same name. This was corrected. |
| Fixed in 6.5.2 | |
|---|---|
| Number | Resolution |
| Release 6.5.2 incorporates all fixes resolved in the release 6.4 series through release 6.4.8. See Release Notes for StreamBase 6.4.x for details. | |
| SB-15962 | Under certain circumstances in recent releases, StreamBase Studio could fail to load custom or third-party Java code in JAR files called by custom Java operators or adapters, even when the JAR file was installed in the Studio project folder. The cause was identified and corrected in releases 6.4.9 and 6.5.2. |
| SB-15933 |
Support for the Appia FIX engine in the StreamBase FIX adapter
was adjusted to provide more flexibility in the BeginString message.
|
| Fixed in 6.5.1 | |
|---|---|
| Number | Resolution |
| Release 6.5.1 incorporated all fixes resolved in the release 6.4 series through release 6.4.8. See Release Notes for StreamBase 6.4.x for details. | |
| SB-15898 | The CSV File Reader adapter now reports a failure to open its specified CSV file on its event port, if enabled. |
| SB-15804 | The group-by feature of the Query operator for read operations (specified in the Group Options tab in the operator's Properties view) was inadvertently disabled in release 6.5.0. This was corrected. |
| SB-15108 | In release 6.5.0, the Trace Debugger was not correctly tracing tuples into the modules of a multiple module application. This was corrected. |
| Fixed in 6.5.0 | |
|---|---|
| Number | Resolution |
| Release 6.5.0 incorporated all fixes resolved in the release 6.4 series through release 6.4.6. See Release Notes for StreamBase 6.4.x for details. | |
| SB-15498 |
In previous releases, if any module parameters were specified for the main
application module, and that module was compiled into a precompiled archive
(.sbar) file, then StreamBase
Server would fail to run that .sbar
file. Now, the server verifies that any parameters set with the
module-parameters element in the
server configuration file at compile time are the same as at .sbar load time. If so, the .sbar is loaded and run; if not, the server issues an
error.
|
| SB-15376, SB-15377 | In previous Studio releases, when editing an expression in a Properties view cell using content assistance, when you clicked outside the content assistance popup, the popup would close, but the cell's editing mode would remain active. Under similar circumstances, Studio could attempt to revalidate the expression before the cell editing was complete. These issues were corrected. |
| SB-15307 |
The Javadoc for com.streambase.sb.Operator
was updated to explain what happens if exceptions occur during calls to
resume(), resumed(), suspend(), and suspended().
|
| SB-14758 |
The format string qualifier %z for the
strftime() function was corrected to adhere to the
documented standard.
|
| SB-14761 |
The sbargen command was
ignoring certain settings in the java-vm section of the specified server
configuration file, whereas StreamBase Server using the same
configuration file would locate and use those settings as expected. The
sbargen command was updated
to read the server configuration file the same way as the server.
|
For the list of issues resolved in previous releases, see:
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.
| 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 | Some Studio buttons no longer work with newer versions of Linux GTK. | |
| Description |
On recent Linux distributions that provide a very 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 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. |
|
| 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 |
|
| Workaround |
Call Janino as part of StreamBase's |
|
| 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. The issue and its workaround are described in Xulrunner Issues in StreamBase 6.4. |
|
| Workaround | These problems do not occur with Studio 6.5 or later. Studio 6.4 users, see Xulrunner Issues in StreamBase 6.4 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 |
|
| Workaround |
None needed. |
|
| SB-14133 | sb-config --cxx returns a setting for G++ 4.3 on newer Linux distributions | |
| Description |
On Linux, in StreamBase samples that build C++ code, some of
the example Makefiles show |
|
| Workaround |
On such systems, install GCC and G++ 4.2, and edit the Makefiles to specify
|
|
| 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-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 configuration directory is in
|
|
| 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 |
|
| Workaround |
Add another Filter operator and split the predicate settings between the two Filter operators. |
|
| SB-13303 | Reuters RFA Configuration File wizard cannot 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 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. Use the following procedure as a workaround:
|
|
| SB-13144 | Variables view does not refresh under some conditions. | |
| Description |
While debugging an application in Studio, after setting a list element value in the Variables view while the debugger is suspended, the Variables view may intermittently fail to refresh. |
|
| Workaround |
Close and reopen the Variables view. |
|
| 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 both Server and Studio 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 checkbox 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 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 |
|
| 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-11850 | Properties view Help button shows correct Help page but wrong TOC entry | |
| Description |
In the Properties view, when you click the circled question mark Help button, Studio Help opens showing the documentation entry for the currently open Properties view tab of the currently selected EventFlow component. However, the TOC entry in the Help window sometimes does not match the open page. |
|
| Workaround |
None. The correct Help page is shown. |
|
| SB-11387 | Visual debugger slows application execution. | |
| Description | Running an application while it is being debugged by the StreamBase visual debugger incurs a performance cost in terms of the peak message rate that the application can handle. For this reason, do not enable the debugger for production. Also, be aware of the possible changes in speed when enqueuing large amounts of data to an application being debugged. | |
| Workaround | None. | |
| 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-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-11130 | Focus in the Debug view is sometimes lost while stepping through debugging. | |
| Description | Focus in the Debug view can be intermittently lost while stepping through an application at high speed, such as when frequently pressing the F6 button. | |
| Workaround | If the focus becomes lost in the Debug view during execution stepping, you can reselect any operator in the execution stack of the Debug View and continue stepping. | |
| 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. | |
| 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-10971 | CSV Reader sample application must be reloaded. | |
| Description | The CSV Reader sample application from previous releases no longer passes typechecking in release 6.x. | |
| Workaround | Reload the CSV Reader sample shipped with release 6.x. | |
| SB-10486 (1) | On-disk format for query tables changes in 6.x. | |
| Description | The on-disk format for disk-based query tables changed in 6.0 as a result of adding support for hierarchical data and upgrading the underlying disk database library. | |
| Workaround | If you have query tables in existing applications, you must convert them to the new format by dumping to a CSV file in your current StreamBase release and reloading into the new StreamBase release. | |
| SB-10486 (2) | Hierarchical data restrictions. | |
| Description | Patterns by value do not support using nested data for their on value portion. Similarly, nested data 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-10298 | Hierarchical schemas defined in StreamSQL cannot be re-used in StreamBase Studio. | |
| Description | StreamBase does not provide a way to share a hierarchical schema between StreamSQL and EventFlow application types. | |
| Workaround | Use the Named Schemas and Saved Schemas features of Studio. | |
| #73006, 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. | |
| #69299, 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 a CompilationException: I/O exception: Not enough space error message from StreamBase Server. | |
| Workaround | Increase the size of your system's paging file. | |
| #56829, SB-7148 | Invalid byte error when opening EventFlow application. | |
| Description |
Studio sometimes fails to open an EventFlow application with this error:
org.xml.sax.SAXParseException: Invalid byte 1 of 1-byte UTF-8 sequence |
|
| Workaround |
Perform the following steps to recover:
|
|
| #55871, SB-7125 | Group labels can appear truncated. | |
| Description | Group labels longer than 12 characters are truncated and elided if the group is open, and truncated if longer than 5 characters if the group is closed. | |
| Workaround | Pad the end of the group label with space characters to prevent truncation. | |
| #52959, 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. | |
| #49739, 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. | |
| #48285, 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. | |
| #36261, SB-6838 | Studio 3.x workspaces not compatible with Studio 5.x. | |
| Description | StreamBase Studio 5.0 introduced a new workspace format that is incompatible with the workspaces from previous releases. Studio 5.0 detects an attempt to use a previous version's workspace and prevents you from proceeding. | |
| Workaround | Start Studio 5.0 with a new, empty workspace. Then use Import StreamBase Projects from StreamBase Studio 3.x. See Migrating Studio 3.x Projects. | |
| #35859, 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:
allows any intermediate stream that contains the pattern of a |
|
| #35743, 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. | |
| #35429, 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 as much as possible. | |
| #33330, 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. | |
| #27060, 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. | |
| #26888, 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.
|
|
| #26477, 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. | |
| #26255, 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 (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. | |
| #25228, SB-5628 | Include Package with Custom Java Functions. | |
| Description | If you use a custom Java function (simple or aggregate) with no package, javac returns a compile error. | |
| Workaround | Put the function in a package. | |
| #25009, SB-5602, #25004, 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. | |
| #15898, SB-5078 | C++ Custom Aggregate functions cannot return a string. | |
| Description |
Custom aggregate functions that are implemented in C++ cannot return a
string.
|
|
| Workaround | Create the custom aggregate in Java. | |
| #14807, SB-4951 | Problem running large applications in debug mode. | |
| Description |
Very large applications that run in standard mode may not start in debug
mode, with errors such as code too large.
|
|
| Workaround | Organize the application into smaller modules. | |
| #14763, SB-4937 | Problem when tuple in top-level module consumes large amounts of CPU time. | |
| Description | If the processing of a single tuple in the top-level module consumes a large amount of CPU time, contained parallel modules that are connected directly to output streams will see their output blocked until the tuple/operator releases the CPU and the tuples can be passed to the network. | |
| Workaround | Put the time-consuming computation into its own parallel module. This workaround may not solve the issue in all cases, because inter-module queues can grow very large, but may help in many cases. | |
| #14745, 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.
|
|
| #14207, 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. | |
| #13017, 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. | |
| #10674, SB-4225 | Some disk drive configurations can corrupt disk-based query tables. | |
| 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 checkbox labeled Enable write caching on the disk. Unchecking this box would prevent the problem from occurring. | |
| #10291, 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. | |
| #9620, 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 the StreamBase Studio Reference. | |
| #8174, 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. | |
| #7361, SB-3308, #2585, SB-1601 |
From Windows, the custom-simple-function and
custom-aggregate-function samples do not work
with Solaris server or 64-bit Linux server.
|
|
| Description |
On Windows, the installed custom-simple-function and custom-aggregate-function samples contain library files
(log.so and stdev.so, respectively) that are built for 32-bit Linux. These
custom functions will work properly only when StreamBase Studio
is connected to a 32-bit Linux server, not a Solaris server or a 64-bit Linux
server.
|
|
| Workaround |
To use the custom-simple-function and
custom-aggregate-function samples with a
Solaris server:
|
|
| #7191, SB-3260 | Using non-member Schema.Field to access a tuple does not throw a useful exception. | |
| Description |
The StreamBase client API 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. | |
| #6860, 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. | |
| #6539, SB-3121 | Mozilla 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 Mozilla installation.
For example, on Linux, set it to:
MOZILLA_FIVE_HOME=/usr/lib/mozilla-<
|
|
| #5400, 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, thus
the Java Operator can never emit any tuples.
|
|
| Workaround | None. | |
| #5389, 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 tar file instead of the RPMs to install StreamBase on Linux. | |
| #5327, 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. | |
| #4824, 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. | |
| #4451, SB-2507 | Java API IOException when client program is suspended. | |
| Description |
A program using the StreamBase Java API 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. | |
| #4289, 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 tools such as sbfeedsim, which replays recorded data. It also affects the client API, 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. | |
| #3236, 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. | |
| #2811, 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
.sbconf file to point the datadir element (within the <server> ... </server> 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.
|
|
| #2414, 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 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. | |
| #2197, 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. | |
| #2048, 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. | |
| #1838, SB-1039 | C++ code is not binary compatible between releases. | |
| Description |
If you use either the C++ client API, 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: libsbclient.so.4:
cannot open shared object file: No such file or directory
|
|
| Workaround | Recompile your C++ code from your original source against the new headers. | |
| #1456, 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.
|
|
| #1450, 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.
|
|
| #1395, 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.
|
|
