StreamBase Release Note Archives

Contents

Limitations Resolved in 7.4.x
Limitations Resolved in 7.3.x
Limitations Resolved in 7.2.x
Limitations Resolved in 7.1.x
Limitations Resolved in 7.0.x
Limitations Resolved in 6.6.x

This page summarizes the history of limitations resolved in previous StreamBase releases.

Limitations Resolved in 7.4.x

Fixed in 7.4.5
Number	Resolution
TIBCO StreamBase® release 7.4.5 incorporates all fixes resolved in the release 7.3 series through 7.3.12.
SB‑27670	The Bidirectional Socket adapter was updated to provide speed improvements.
SB‑27514	A High Performance FIX Engine session with a mid-day session gap could prevent an acceptor from accepting connections. The cause was identified and corrected.

Fixed in 7.4.4
Number	Resolution
TIBCO StreamBase® release 7.4.4 incorporates all fixes resolved in the release 7.3 series through 7.3.11.
SB‑27574	An issue with nested lists when using the Log adapter's custom format expression field was fixed.
SB‑27497	Using a declared expression as an argument to included tuple expressions could cause compilation errors with signatures like `File Unknown, Line -1, Column -1: Expression "_vnnn" is not an rvalue`. This was corrected.
SB‑27466	When a Metronome operator was configured to Drop delayed tuples it could incorrectly emit timestamps in the future, instead of the most recently seen timestamp within its specified interval. This was fixed.
SB‑27441	Calling unique() on the output of another list function sometimes caused a code generation error or a null pointer exception at run time. This was corrected.
SB‑27381	The TIBCO StreamBase® Adapter for Exegy was ignoring its isAggreated flag for subscription requests, causing prices to be returned in the default format (merged or expanded) of the XCAPI library. The library returns expanded prices by default in versions prior to 3.2.0 and merged (aggregated) prices thereafter. This was fixed
SB‑27364	When multiple schemas were moved from one application to another by refactoring, inconsistent serialization resulted, generating typecheck errors. This was fixed
SB‑27352	Query operator connections to data constructs that used escaped identifiers were not being loaded correctly. This was fixed.
SB‑27305	Removing an arc issuing from a sub-module could make an application's internal state inconsistent with its Eventflow representation. This was fixed.
SB‑27303	Under certain conditions, removing a Filter operator predicate from the Predicate Settings tab triggered a null pointer exception. This was fixed.
SB‑27297	Previously, When a Query operator's input schema was not compatible with the schema of the table that it was reading or writing, a compile error resulted. Now, a typechecking error is generated that describes the problem. In addition, implicit casts to String type, which was formerly deprecated, is now disallowed. Instead of generating a warning, attempts at such casts now produce a typechecking error.
SB‑27293	In the 7.4.3 release, when attempting to run an EventFlow application from Studio created a compilation exception, its sbd process failed to exit, consuming processor cycles and potentially preventing Studio from launching subsequent applications. This was fixed.
SB‑27288	The TIBCO StreamBase® Adapter for Deutsche Bank Autobahn FX Rapid was reporting quotes as Indicative instead of Tradable. This was fixed.
SB‑27256	In certain use cases, the CSV File Reader input adapter caused typecheck errors because it hard-coded schema names for outbound tuples that could clash with existing schema names. This was fixed
SB‑27251	In very rare instances when many StreamBase clients attempted to connect to a server simultaneously, the server could enter an unresponsive state from which it was unable to recover. The cause was identified and corrected.
SB‑27192	In previous 7.4.x releases, selecting an arc on the canvas failed to display the EventFlow editor prompt Select the input/output stream <name> to declare a schema that you could click to immediately edit its schema. This was corrected.
SB‑27188	Previously, when you used expressions as secondary table indexes, those indexes would not be used, causing a table scan to be performed. This was fixed.
SB‑27164	The FIX adapter could run out of memory as a result of making continued attempts to connect while a counterparty is down. This was corrected.
SB‑27090	To fix a divide-by-zero issue, the `slope()` and `intercept()` functions were modified to return zero when a window contains a single point (that is, one row) or multiple identical points (that is, duplicate rows containing the same values).
SB‑27056	Query operators displayed the names of tuples whose types were named schemas simply as "tuple," rather than keeping the names of the named schemas. This was fixed, so that named schemas are no longer anonymous in output schemas.
SB‑27031	When a StreamBase server was running an application on a debug port, the Manual Input view in the SB Test/Debug perspective could fail to connect to it, reporting `No Running StreamBase Application`. This was fixed.
SB‑26798	In some situations, such as in Aggregate windows, assigning values to tuple subfields could cause all of the fields to acquire the same value. For example, specifying: (1 AS a, 2 AS b, 3 AS c) AS myTuple might produce an erroneous result like: (1 AS a, 1 AS b, 1 AS c) This was corrected.
SB‑26627	Exporting a bundle from StreamBase Studio could fail with a class loader exception such as `Lcom.streambase.fastjson.parser.Feature; cannot be loaded via the given classloader`. This was fixed.
SB‑26408	StreamBase Studio reported spurious typecheck errors for valid parent schemas when passed down through multiple levels of module imports. This was corrected.
SB‑25298	When configured for the log4j logging back end, the StreamBase server failed to log shutdown messages. If the StreamBase server fails to start as a result of a port conflict, the resulting port-conflict shutdown message was lost, making it hard to diagnose this condition. This was fixed.
SB‑24246	Environment variables used within StreamBase configuration files of bundled applications could fail to get expanded. In some cases, this caused the bundled application to fail to launch. This was corrected.

Fixed in 7.4.3
Number	Resolution
TIBCO StreamBase® release 7.4.3 incorporates all fixes resolved in the release 7.3 series through 7.3.11, and in the release 7.2 series through 7.2.15.
SB‑27044	Metronome and Heartbeat operators indicated typecheck errors when custom functions were used in interval expressions. This was fixed.
SB‑26921	When importing a named schema to use as a table schema in the Interface Editor, the schema's fields failed to display in the Primary Index tab, forcing the user to manually copy and paste the fields into the Edit Table Schema dialog to assign index fields. This was fixed.
SB‑26912	Previously, the CSV File Writer output adapter provided no notification if its output file were deleted during execution, causing its output to be silently discarded. This is fixed, so that now this condition generates a status event of type `Error` on the event port.
SB‑26878	Using a custom function in an adapter property field could cause spurious typecheck errors, which could be ignored. This was fixed.
SB‑26860	When reopening a saved table schema in which the primary index type was set to Hash, StreamBase Studio reset the index type to Btree. This was fixed.
SB‑26856	Calling `mergelist()` or `filterlist()` from user functions caused compilation errors. This was fixed.
SB‑26838	Calling `sort()` from user functions caused null pointer exceptions. This was fixed.
SB‑26763	Certain FIX counterparties violate the FIX spec during logon when the initial logon message contains ResetSeqNumFlag(141)=Y by replying with a logon message that does NOT also contain 141=Y. Because this is incorrect behavior, by default the High-Performance FIX Engine will refuse the logon reply and disconnect from the counterparty. If you wish the engine to overlook the omission and consider the logon reply valid, add the following line to your `fixengine.properties` file: `ignoreSeqNumTooLowAtLogon=true`
SB‑26885	The File Reader Input adapter was updated to handle fast rates of incoming control port tuples specifying names of file to be read. Prior to this fix, the adapter might read the same file multiple times instead of processing multiple files in sequence.
SB‑26804	At startup, an application with deeply nested modules could generate a `ConcurrentModificationException`. This was fixed.

Fixed in 7.4.2
Number	Resolution
TIBCO StreamBase® release 7.4.2 incorporates all fixes resolved in the release 7.3 series through 7.3.11, and in the release 7.2 series through 7.2.15.
SB‑26819	A threading issue prevented the File Writer adapter from appending data to or overwriting an existing file. This was fixed.
SB‑26818	Errors were received when attempting to disable the control and status ports of the File Writer output adapter. These were fixed.
SB‑26815	Invoking `join()` more than once within an Aggregate operator raised a `ClassFormatError` warning and prevented the application from producing further output. This was fixed.
SB‑26744	When configuring a Pattern operator, selecting `value` as the Window Type without first specifying a field for Order Field resulted in a Null Pointer Exception. This was corrected, and now results in a typecheck error. Important The Pattern operator's `polling-interval` parameter is no longer supported, and causes an error if it is present. To correct your applications, open your EventFlow module's `.sbapp` files in a text editor and search for the string `polling-interval`. If found, remove the entire `<param>` element that contains that string.
SB‑26732	Setting tuple fields to `null` could cause the fields to be set to tuples of null fields instead of null tuples. This was fixed.
SB‑26720	The High-Performance FIX adapter would hang when logging off if the counter-party did not send a Logout reply message. This was fixed.
SB‑26689	StreamBase apps containing Aggregate operators whose emit and emit-all parameters had the same predicate, or whose close and close-all parameters had the same predicate, would cause compilation errors with the signature: `name is not an rvalue`. This was fixed.
SB‑26676	The skeleton file produced by sbd -s failed to parse on RHEL 4 and earlier RHEL 5 distributions due to an apparent bug in their ICU (International Components for Unicode) library. This issue is now sidestepped by making sure that generated StreamBase configuration files contain the ASCII single-quote character instead of the same character in UTF-8 encoding.
SB‑26674	The TIBCO StreamBase Output Adapter for TIBCO Spotfire Automation Services was incorrectly reporting a typecheck error when using Microsoft Windows authentication and a password was supplied. This was fixed.
SB‑26660	Errors in expressions that referenced a field name specified with the `old.` prefix could cause a Null Pointer Exception. This was fixed.
SB‑26590	StreamBase Studio project configuration synchronization now correctly creates project-relative paths in cases where the project does not physically reside under the workspace root.
SB‑26583	After using a named schema in a Java operator, if you set that schema to Private Schema in the Edit Schema tab, the module no longer typechecked, even though the schema did not change. The Definitions tab showed the schema as (unnamed) and would not allow you to remove it, and once saved, StreamBase Studio would no longer open the module. This was fixed.
SB‑26421	A malformed `formatstring` argument passed to the `parse_time()` function caused StreamBase server to crash after its first invocation. This issue was corrected such that the server now warns at start-up time if it detects a `parse_time()` function with a malformed `formatstring`.
SB‑26198	Initialization of the TIBCO StreamBase® Operator for TIBCO ActiveSpaces® would fail when connecting to the ActiveSpaces Metaspace took too long. This was fixed.
SB‑25581	When installing StreamBase Studio as an Eclipse plug-in from the StreamBase Studio Eclipse Update Site, it is no longer necessary to clear the Group Items By Category check box in order to see available updates.
SB‑22750	In the JMS adapter documentation, the configuration example for ActiveMQ servers incorrectly specified the `<jms-server>` `connection-factory-name` attribute as `org.apache.activemq.ActiveMQConnectionFactory`. The string was changed to `ConnectionFactory`, which is a correct value.

Fixed in 7.4.1
Number	Resolution
TIBCO StreamBase® release 7.4.1 incorporates all fixes resolved in the release 7.3 series through 7.3.11, and in the release 7.2 series through 7.2.15.
SB‑26517	The sbconf file synchronizer introduced in release 7.4.0 now correctly handles path names containing trailing slashes.
SB‑26441	The TIBCO StreamBase IBM WebSphere MQ Output Adapter option Queue When Connection Down was added in 7.3.10 to make the adapter queue rather than reject tuples when the connection to the MQ server is down, and then process the queued tuples when the connection is restored. Now, when this option is NOT selected, status messages are issued when a tuple is sent to the MQ server, allowing the application to know whether or not the tuple was published. This restores the behavior prior to 7.3.10.
SB‑26436	The TIBCO StreamBase Output Adapter for UDP (Sender) was causing high CPU loads while connected. This was fixed.
SB‑26429	Sometimes attempting to link a data arc to a module with placeholder tables did not work, even when table names and schemas matched. As a result of this fix, now when a data arc to a table in a referenced module is deleted, all mappings to the table or reference at the other end of the data arc are cleared.
SB‑26398	Previously, you were not able to use named schemas inside a function's body or inside the first argument to `eval` (as when using `sbd --eval "expr" file.sbapp`) or `compile` without explicitly including them. Now you can reference a named schema, such as Point, like this: eval("Point(1 AS x, 2 AS y)", Point()) In previous releases, you would need to use the full expression: eval("Point(1 AS x, 2 AS y)", tuple(* AS *), Point())
SB‑26389	The TIBCO StreamBase Input Adapter for Deutsche Bank Market Data did not properly set the arrival time when using a variant of CustomSpot or CustomSwap. This was fixed.
SB‑26340	Due to changes in StreamBase Studio 7.4.0 to make StreamBase lists compatible with Java arrays, custom function resolvers for custom Java functions with generic list arguments failed. This is now corrected, so that you can use `List<T>` arguments in Custom Function Resolvers.
SB‑26295	StreamBase Studio did not properly initialize default values for adapter properties relating to a capture field strategy, and as a consequence sometimes failed to find capture field conflicts. This was corrected.
SB‑26284	In previous releases, the feed simulation Data File Options dialog let you choose a data file in a different directory than the .sbsf file itself, but did not store the path to the file. This caused the Timestamp from column option to fail, and other problems. In the current release, this is fixed. Feed simulations now store paths to data files, which can be either absolute or relative to the feed simulation folder.
SB‑26274	In some cases, the state of the First row as header option in the feed simulation Data File Options dialog was not being properly stored in between invocations of the dialog. This was fixed.
SB‑26236	In 7.4.0, custom functions could have variable numbers of arguments, but a `<custom-function>` element for such a function in the .sbconf file would execute only if the `args="auto"` attribute was set. Starting with 7.4.1, if you want to declare individual `<arg>` elements, you must include in your `<custom-function>` element a new attribute, `isVarargs="true"`.
SB‑26226	In 7.4.0, EventFlow lists passed as arrays to custom Java functions could not exceed two dimensions, whether called via a function alias or via `calljava()`. This is still the case when using a function alias, but you can now use `calljava()` to pass higher-dimension lists as arrays. See Creating Custom Java Functions in the API Guide for details.
SB‑26045	The function data type introduced in release 7.4.0 enabled definitions of functions that return literals, but StreamBase did not allow such functions or lists of functions with any return type to be manually enqueued to input streams. This was fixed.
SB‑26008	When previewing data files, the feed simulation Data File Options dialog would sometimes incorrectly display `read error; lines will be dropped while running simulation`. This was corrected.
SB‑25895	In release 7.4.0, multithreaded use of a typecheck-time schema for a Java operator that accesses fields in a tuple could result in spurious errors about an incorrect schema. This was fixed.
SB‑25886	In feed simulation Processing Options, when selected, the Timestamp from column now defaults to first value read, not zero.
SB‑25317	If the actual binding of a capture field conflicted with another field already in the schema, StreamBase would throw a compile-time error, or no error at all, but the application would not show the erroneous component in either case. This was fixed. Typecheck errors are now thrown in these cases.
SB‑25105	In 7.4.0, if a launch configuration had the Allow Remote Java Debugging check box selected, and if the user launched that configuration in Run mode, then the application would not successfully start. This was fixed.
SB‑25090	When creating a feed simulation using a data file for an input stream having no fields, it was not possible to declare First Row as Header or to select a timestamp column by name. This was fixed.
SB‑24416	In some cases, copying and renaming an interface would cause a typecheck error in any referencing modules. This was fixed.
SB‑24008	The feed simulation Data File Options dialog was showing incorrect previews of CSV files when the First Row as header option was selected and the Lines to skip option was set to 1 or higher. This was fixed.

Fixed in 7.4.0
Number	Resolution
TIBCO StreamBase® release 7.4.0 incorporates all fixes resolved in the release 7.3 series through 7.3.10, and in the release 7.2 series through 7.2.15.
SB‑26189	The Database Change Data Capture input adapter will no longer re-publish all changes in the log upon start. Instead, it now gets the last change number and starts from that point on. In addition, the issue with "too many open cursors" was fixed.
SB‑26188	Selecting a field name in the feed simulation editor's Customize Fields dialog would sometimes scroll the selected row out of view. This was fixed.
SB‑26167	The StreamBase Studio debugger failed to launch when a StreamBase .sbapp contained one or more operators whose names were escaped because they contained characters other than letters, numbers and underscores, for example, `#"big-agg!"`. This was fixed.
SB‑26140	Using nested fields as primary indexes in Query tables shared across modules raised the error "Current module contains no placeholder tables to be configured." This problem did not occur when referencing a table within its own module. This was fixed.
SB‑26131	For imported projects having feed simulations that read data files with non-default column mappings, the feed simulation editor incorrectly displayed default values (i.e., 1,2,3...) in the Map to file column of the Column mapping table. Although the simulation would use the correct column mappings, the UI did not reflect this. This UI issue was corrected.
SB‑26097	Error messages appeared in the StreamBase Studio Error Log if a custom feed simulation reader was not configured properly. These unnecessary messages have been suppressed.
SB‑26000	Operators and adapters were mangling escaped field identifiers (such as `#"abc:xyz"`) into normal identifiers (`abcxyz`). This was fixed.
SB‑25943	The feed simulation Data File Options UI did not register changes in the delimiter that the user made. This was fixed.
SB‑25925	When selected, the First Row as Header check box in the feed simulation editor was cleared every time the feed simulation file was saved. This was fixed.
SB‑25885	Calling new_tuple(), new_tuple_subset(), or new_tuple_subset_loose() with a named schema as the first argument, for example, new_tuple(MySchema(), 3 AS a, 4 AS b), returned a null result unless the named schema was fully specified in the first argument, for example new_tuple(MySchema(1 AS a, 2 AS b), 3 AS a, 4 AS b). With this release, it is no longer necessary to include a specification of the named schema. That is, new_tuple(MySchema(), 3 AS a, 4 AS b) now produces a fully-formed new tuple. As previously, any fields in the given schema that are not referenced in arguments 2 and higher will be null in the new tuple.
SB‑25877	The feed simulation editor was unable to preview data files compressed using BZ2 format, even though it could read and use them in simulations. Now it can.
SB‑25875	In StreamBase Studio 7.3.x, dynamic variables were not visible to the Gather operator's output target list. Now they are.
SB‑25831	When EventFlow applications having Query operators containing old.<fieldname> references were converted to SSQL, either the SSQL file would fail to typecheck, saying the "old." fields do not exist, or the SSQL would run but might not return a correct result. This was fixed.
SB‑25725	Both the simple and aggregate standard deviation and variance functions for populations (`stdevp` and `variancep`) returned null for inputs of size 1 when the result should have been 0. This was fixed. Note that the `stdev` and `variance` functions (for sample data) still properly return null for inputs of size 1.
SB‑25658	In previous releases, Query table insert and update operations that referenced unqualified field names created ambiguities in the following use cases: INSERT; if duplicate, UPDATE UPDATE; if not found, INSERT In such cases, the unqualified field names were automatically assigned as `input.` at runtime without any notification. Now, StreamBase Studio issues warnings in the Problem view for projects containing ambiguous references. For example: the reference to field "X" is ambiguous; you must qualify the field reference with one of "input.", "input1.", "old." As these warnings may become errors in a future release, it is best to fully qualify potentially ambiguous field names either with Quick Fix or manually rather than to suppress the warnings. For information about quick-fixing these issues, see Fixing New Typecheck Warnings in Query Operators.
SB‑25657	Previously, if you imported a child schema and used it in a Query Table, although fields from its parent schema were visible, they could not be used as indexes. Now they can.
SB‑25654	Applications could fail to launch if they had Aggregate operators with a Predicate dimension configured to evaluate emit and close predicates before adding tuples to its window which referenced fields from the input stream. Users would receive an error message such as 'Runtime exception: Internal error generating operator Aggregate: Attempted to dereference nonexistent field...' This was fixed.
SB‑25498	Previously if you provided `Tuple.setfield` with a different number of fields than the schema object contained, it would error. Now, the map does not have to contain the same number of entries.
SB‑25340	You can now create a Delta Stream for placeholder query tables. Previously this was only possible for private and shared query tables.
SB‑25203	Accessing a .sbint file specifying a Query Table with an empty secondary index would silently produce errors when data was inserted into the table. Specifying an empty index is still an error, but is now is caught in typecheck. The error message is 'Secondary index `n` is empty in `tablename`'.
SB‑25201	Using parameters with escaped identifiers (such as `#_A100_`) in an Iterate operator's Condition or Filter fields failed to typecheck with a "Field not available from any stream" error. This was fixed.
SB‑25194	In previous release, some BSON operations with timestamp data types would throw an "unsupported BSON type" runtime exception. This was fixed.
SB‑25146	Enabling dequeuing in sbadmin would start all output adapters regardless of their "Start with application" setting, moving them from NOT_YET_STARTED state to STARTED state when the container sent dequeue=ENABLED. Input adapters displayed the same behavior with the enqueue=ENABLED command. This was fixed, so that these commands no longer implicitly start adapters.
SB‑25096	`sbd --eval` now processes the `-f` argument to configure all applicable settings before evaluating an expression.
SB‑24953	When specifying a Sequence Identifier for the Sequence operator, you can now specify any suitable numeric field from the input stream rather than having to create a new field to hold sequence values.
SB‑24781	When a Query operator performs an insert, it is now possible to specify the `old` prefix in an output list, just as it was possible with query updates. Previously, `old` was disabled on the output list. When the operation is an insert, the value of all the fields in the `old` tuple is `null`.
SB‑24664	Typechecking a schema with a capture field could cause a Null Pointer Exception if the capture field's Capture Type was null. This was fixed; failing to specify a Capture Type now generates a typechecking error, as it should.
SB‑24662	References to environment variables in `sbd.sbconf` were not respected when running apps within StreamBase Studio. Even after setting a launch configuration environment variables, the configuration file obtained variable values from StreamBase Studio. Now, when launching from within studio, all environment variables set in the launch configuration are used when parsing the configuration file.
SB‑24583	In previous versions, a the expression for a declared variable in a target list could be evaluated multiple times, which could lead to inconsistent or incorrect results if the expression included calls to functions like `random()`. In this version, declared variable value expressions are evaluated at most once.
SB‑24424	The aggregate operator sometimes output tuples whose values were incorrectly calculated when the intermediate emission property value did not divide evenly into the window size or advance property values. This issue was resolved.
SB‑23819	You can now create dynamic variables without first needing to create a stream.
SB‑23709	When a client disconnects from the StreamBase server, the information in the disconnecting client message now includes the client's IP address. Also, the severity of this message was raised from INFO to WARN.
SB‑23636	Declaring a variable more than once or duplicating a field name in a field grid did not cause any typecheck error, but did cause an error at run time. Now declaring or adding the same name more than once generates a "Field named <name> already exists" error.
SB‑23632	Calling `String.format` with `calljava` is now supported.
SB‑23187	The Join and Gather operators were unable to use module dynamic variables for setting certain properties. This was fixed.
SB‑22847	sbadmin issued an incorrect and confusing error message when you attempted to add a nonexistent container connection more than one time. (The message indicated that that the connection already did exist.) A failed attempt to add a container connection also made it impossible to subsequently add that connection without restarting the server. This was fixed.
SB‑22815	The second argument to `parse_time()`, the format string, was formerly required to be a string literal. The function now accepts for that argument an expression that evaluates to a `simpleDateFormat` string.
SB‑22182	The application/extension section in sbd.sbconf and .sbdeploy files now support all the same configuration options.
SB‑22129	Server configuration files that included nested files via `<sb-include>` or `<xi:include>` elements only caused a project to rebuild when the top-level sbconf file changed, and not when saving changes to any nested sbconf file. Now, changing any included file triggers rebuilding of the project.
SB‑21337	Inserting an operator before in an arc containing a breakpoint would delete the breakpoint. This was changed to move the breakpoint to the arc upstream of the inserted operator.
SB‑19921	The Stop and Pause buttons on feed simulations did not become disabled at end of file. This was fixed so that they are both disabled when the Run button is enabled. Both the tuple count and speed are preserved from the initial pass through the data.
SB‑12403	Enabling an error port for the Pattern operator on the General tab of its Properties view created a port that was not functional. Now Pattern operator errors are issued through that port instead of incorrectly being sent to the console.
CQS‑2270	With certain very large query predicates that contain multiple nested AND and OR clauses, StreamBase server may consume very large heap sizes. This was fixed.

Limitations Resolved in 7.3.x

Fixed in 7.3.12
Number	Resolution
TIBCO StreamBase® release 7.3.12 incorporates all fixes resolved in the release 7.2 series through 7.2.15 and in the release 7.1 series through 7.1.12.
SB‑27288	The TIBCO StreamBase® Adapter for Deutsche Bank Autobahn FX Rapid was reporting quotes as Indicative instead of Tradable. This was fixed.
SB‑27251	In very rare instances when many StreamBase clients attempted to connect to a server simultaneously, the server could enter an unresponsive state from which it was unable to recover. The cause was identified and corrected.
SB‑26912	Previously, the CSV File Writer output adapter provided no notification if its output file was deleted during execution, causing its output to be silently discarded. This is fixed, so that now this condition generates a status event of type `Error` on the event port.
SB‑26819	A threading issue prevented the File Writer adapter from appending data to or overwriting an existing file. This was fixed.
SB‑26818	Errors were received when attempting to disable the control and status ports of the File Writer output adapter. These were fixed.
SB‑26763	Certain FIX counterparties violate the FIX spec during logon when the initial logon message contains ResetSeqNumFlag(141)=Y, by replying with a logon message that does NOT also contain 141=Y. Because this is incorrect behavior, by default the High-Performance FIX Engine refuses the logon reply and disconnects from the counterparty. If you wish the engine to overlook the omission and consider the logon reply valid, add the following line to your `fixengine.properties` file: `ignoreSeqNumTooLowAtLogon=true`
SB‑26720	The High-Performance FIX adapter would sometimes hang when logging off if the counterparty did not send a Logout reply message. This was fixed.
SB‑26676	The skeleton file produced by sbd -s failed to parse on RHEL 4 and earlier RHEL 5 distributions due to an apparent bug in their ICU (International Components for Unicode) library. This issue is now sidestepped by making sure that generated StreamBase configuration files contain the ASCII single-quote character instead of the same character in UTF-8 encoding.
SB‑26462	The TIBCO StreamBase Input Adapter for Wombat MAMA no longer tries to report transport connect/disconnect/quality messages for TIBRV middleware.
SB‑26441	The TIBCO StreamBase IBM WebSphere MQ Output Adapter option Queue When Connection Down was added in 7.3.10 to make the adapter queue rather than reject tuples when the connection to the MQ server is down, and then process the queued tuples when the connection is restored. Now, when the Queue When Connection Down option is NOT selected, status messages are issued when a tuple is sent to MQ, which allows the application to know whether the tuple was published or not. This restores the behavior for releases prior to 7.3.10.
SB‑26436	The TIBCO StreamBase Output adapter for UDP (Sender) was causing high CPU load while connected. This was fixed.
SB‑26421	A malformed `formatstring` argument passed to the `parse_time()` function caused StreamBase server to crash after its first invocation. Also, providing a non-literal string (such as a string field) for the `formatstring` argument caused a compile-time error that was difficult to diagnose. These issues were corrected such that the server now warns at start-up time if it detects a `parse_time()` function with a malformed `formatstring`, and issues an error tuple on any invocation of `parse_time()` with a non-literal `formatstring` argument.
SB‑26198	Initialization of the TIBCO StreamBase® Operator for TIBCO ActiveSpaces® would fail when connecting to the ActiveSpaces Metaspace took too long. This was fixed.
SB‑26082	The StreamBase Installation Guide for Linux indicated that you could use the RPM installer without having root privileges. This statement was incorrect and was removed. You can, however, perform a Linux installation from an archive-bin installer without needing root privileges.
SB‑25581	When installing StreamBase Studio as an Eclipse plug-in from the StreamBase Studio Eclipse Update Site, it is no longer necessary to clear the Group Items By Category check box in order to see the available updates.

Fixed in 7.3.11
Number	Resolution
TIBCO StreamBase® release 7.3.11 incorporates all fixes resolved in the release 7.2 series through 7.2.15 and in the release 7.1 series through 7.1.12.
SB‑26389	The TIBCO StreamBase Input Adapter for Deutsche Bank Market Data did not properly set the arrival time when using a variant of CustomSpot or CustomSwap. This was fixed.
SB‑26283	Specifying `null` as a value for a field without giving it a data type produced a null pointer exception in StreamBase Studio. This was fixed such that failing to specify the data type of a null field now generates a typecheck error to indicate that this is not a legal field specification.
SB‑26229	Declaring or including a nested field using its original name could create a compile error. For example, `DECLARE data.name AS name` failed (but `DECLARE data.name AS newName` worked). This was fixed so that the two field names can be the same.
SB‑26187	When generating a layout file from an EventFlow file by selecting Extract To Layout File from the StreamBase menu, the EventFlow file could lose its entire contents. However, this only occurred when the EventFlow application was created in StreamBase Studio on another OS platform in which different line ending characters are used. This issue was corrected.
SB‑26097	Error messages appeared in the Error Log view in StreamBase Studio if a custom feed simulation reader was not configured properly. These unnecessary error messages were suppressed.
SB‑26046	Under certain condition StreamBase would fail to compile and launch applications with errors similar to "`CompilationException: CompileException: File Unknown, Line -1, Column -1: Expression "_v605" is not an rvalue`". This was fixed.
SB‑25979	The HA Heartbeat adapter can now specify the network interface when in multicast mode.
SB‑25317	If the actual binding of a capture field conflicted with another field already in the schema, StreamBase would throw a compile-time error, or no error at all, but the application would not show the erroneous component in either case. This was fixed. Typecheck errors are now thrown in these cases.
SB‑25275	In free form mode, the StreamBase Admin operator failed to recognize certain sbadmin subcommands, resulting in runtime errors. The operator now recognizes the same commands as the sbadmin command does when used at the command prompt.
SB‑25004	Refactoring a named schema to rename it in StreamBase Studio raised fatal I`nvocationTargetException` and `IndexOutOfBoundsException` errors. This was fixed.
SB‑24416	In some cases, copying and renaming an interface would cause a typecheck error in any referencing modules. This was fixed.
CQS‑2270	With certain very large query predicates that contain multiple nested AND and OR clauses, StreamBase server could consume very large heap sizes. This was fixed.

Fixed in 7.3.10
Number	Resolution
TIBCO StreamBase® release 7.3.10 incorporates all fixes resolved in the release 7.2 series through 7.2.15 and in the release 7.1 series through 7.1.12.
SB‑25879	The .NET Client API would sometimes not recover all memory at an Unsubscribe request. This was fixed.
SB‑25687	The .lvconf file editor at times would flag an application element as having an error (for example, not able to find a resource needed by an adapter) even when the configuration file would run. This has been corrected.
SB‑25671	Given certain valid JSON input, `jsontobson` would throw an IllegalArgumentException that would prevent proper processing of the current tuple in an application. This has been corrected. Note that you can use the function `catchexception` to work around any exception raised during evaluation of functions or expressions.
SB‑25664	When running on 64-bit Windows platforms, the HTTP Reader, IRC Reader, POP3 Reader, and SMTP Reader Input Adapters would fail to find all available network interfaces, such that the only detectable IP address was 0.0.0.0. This has been fixed.
SB‑25549	When using the parameter `maxRequestResendInBlock` in the `fixengine.properties`, the second `ResendRequest(2)` for the next block of messages contained a bad `EndSeqNo(16)` field value that caused a `Reject(3)` and no resends occur following the first block. This has been corrected.
SB‑25542	The StreamBase TREP-RT subscribing adapter, when configured for the market feed message model, incorrectly populated blob tuple fields with the contents of Reuters Opaque fields. This has been fixed.
SB‑24559	Changing a Generation Method setting for a customized feed simulation field did not show the change in the UI until another field there received focus. This has been fixed.

Fixed in 7.3.9
Number	Resolution
TIBCO StreamBase® release 7.3.9 incorporates all fixes resolved in the release 7.2 series through 7.2.15 and in the release 7.1 series through 7.1.12.
SB‑25504	In previous releases, the .NET operator always loaded the sbd-java.exe.config rather than its own DLL file. The following behaviors have now been implemented in the .NET operator: If a file named MyAssembly.dll.config is found alongside the target assembly, this file will be loaded as the application's configuration file. You can override the new behavior by using the new operator property `NET App Configuration File Name`, which allows you to explicitly specify a configuration file to load instead.

Fixed in 7.3.8
Number	Resolution
TIBCO StreamBase® release 7.3.8 incorporates all fixes resolved in the release 7.2 series through 7.2.15 and in the release 7.1 series through 7.1.12.
SB‑25242	Creating JMS container connections did not utilize `jms-connections-defaults` settings, as documented in Connecting Container Streams Through JMS. This has been fixed.
SB‑25420	The UBS Trading Components handler was not correctly parsing the tenor values submitted by the user. This has been fixed and the Tenor checking has also been updated to reflect version 1.19 of the UBS market data spec in relation to Tenor values allowed.
SB‑25325	The behavior of the IBM WebSphere Output Adapter adapter has changed when Quick Connection-Down Detection is disabled. The adapter now avoids making any reference to a remote disconnected queue when this property is disabled.
SB‑25072	The list of fields for setting values for feed simulations after specifying the Generation Method as Enumerated did not display until a control in the dialog was clicked. Now that list of fields displays without having to click a control.
SB‑25146	Enabling dequeuing in sbadmin would start all output adapters regardless of their "Start with application" setting, moving them from NOT_YET_STARTED state to STARTED state when the container sent dequeue=ENABLED. Input adapters displayed the same behavior with the enqueue=ENABLED command. This has been fixed, so that these commands no longer implicitly start adapters.
SB‑24938	Including a trailing slash on paths when setting the `TMP` environment variable prevented sbd from launching .sbapp files. This has been fixed.
SB‑24494	In StreamBase Studio, switching an Aggregate operator dimension from one type to another (e.g., from tuple to predicate) sometimes did not delete the previous dimension's parameters, producing a "spurious parameters" warning. This has been fixed.

Fixed in 7.3.7

Number Resolution

TIBCO StreamBase® release 7.3.7 incorporates all fixes resolved in the release 7.2 series through 7.2.15 and in the release 7.1 series through 7.1.12.

SB‑25325 The IBM WebSphere Output Adapter, in order to quickly detect connection-down conditions, periodically reads the depth of the base queue. Doing so for remote base queues results in a 2068 (MQRC_SELECTOR_NOT_FOR_TYPE) error. The adapter therefore no longer reads the depth of remote base queues, regardless of the setting of the Quick Connection-Down Detection property.

SB‑25314 In the Thomson Reuters Enterprise Platform for Real-Time Contribution Output Adapter, the default number of digits to the right of the decimal point in encoding REAL64 values was changed from 0 to 4 to match that used in encoding REAL32 values. For more control over the number of digits used, see Data Model in the Adapter's documentation.

SB‑25299 The TREP-RT Contribution Adapter incurred a NullPointerException in processing an ACK response message if no OMM state was present in the message. This was fixed.

SB‑25035 A regression in StreamBase Studio 7.2 could cause feed simulations from .sbfs files to error if a stream contained sub-tuples. This has been fixed.

SB‑25021 In previous versions, TableAccessor.getSchema() could return an equivalent but different object to the result of getSchema() on a returned table row. Accessing a table row using the non-identical schema could cause a performance problem. Now they return identical values.

SB‑24965 The XML to Tuple Java operator was excluding empty values of any type instead of parsing them as the NULL_VALUE_REPRESENTATION property value. This has been fixed.

SB‑24882 Changing the color of data arcs and stream arcs in Studio preferences did not change their appearance on the canvas until Studio was restarted. This has been fixed.

SB‑24050 When using the StreamBaseFIX FIX engine, a FIX adapter configured to run as initiator would not automatically attempt to reconnect when a FIX connection was abnormally terminated. This has been fixed.

SB‑24947

SB‑22083

The following fixes were made to the Exegy Input adapter:

The TradingAction event no longer fails with a null pointer exception when the Include Adapter Latency property is enabled.
Instead of always reporting as a refresh, Trading Action messages now report a trading action command.
You can now send conflation commands to the Exegy server by setting the maximum quote rate value for the adapter as well as sending an optional maxQuoteRate value with each subscription input.
Instead of reporting null values, dictionary output tuples now are populated correctly.

SB‑24891 Restarting an initiator application for a StreamBase FIX adapter failed when an alternate FIX dictionary was being used. This has been fixed.

SB‑24337 Studio applications containing a Map operator that concatenates a string with a timestamp (e.g. "time1: " + to_milliseconds(now()) ) in more than one expression generated a CompilationException when run, even though they typechecked. This has been fixed.

SB‑23684 A warning message for the Morningstar Quotes Feed Input adapter was updated to display the Feed Type to help diagnose instances when it may be incorrectly set.

SB‑23528 At times the Wombat MAMA input adapter stopped responding to subscription requests for non-priced symbols. This happened after repeatedly subscribing and unsubscribing to the same set of symbols, because the expired subscriptions were not being cleared from memory. This has now been fixed. The MAMA publisher will now send out an expired message when it removes subscriptions when they time out due to inactivity.

SB‑23356 A race condition can lead to occasional null pointer exceptions that surface in the Log adapter when the adapter is configured for asynchronous logging. This has been fixed.

SB‑22686

If authentication was enabled, the StreamBase Admin operator required valid values for the Username and Password properties to execute commands on the local StreamBase server instance. This has been changed, so that a username and password are no longer required when the Remote Server property is not selected.

The Username and Password properties for this operator are now deprecated and will be removed in a future release. For remote servers running under authentication, specify the username and password as part of the Server URI.

SB‑22531 The StreamBase Admin operator would autocomplete tuple identifiers starting with input. and input1., but Studio would then typecheck with a message saying "The field 'input' (or input1) is not available from any stream." This has been fixed, so that input., input1., and no prefix are now all equally acceptable.

SB‑19808 When the Wombat input adapter tried to push incoming int and long values into a double field, the resulting values would be null. This has been fixed to promote int and long values to doubles where the schema calls for it.

Fixed in 7.3.6
Number	Resolution
TIBCO StreamBase® release 7.3.6 incorporates all fixes resolved in the release 7.2 series through 7.2.14, in the release 7.1 series through 7.1.12, and in the release 6.6 series through 6.6.25.
SB‑24919	The all-in rate for spot legs was populated from the bid/ask tuple's spotRate field rather than its allInRate field. This was corrected.
SB‑24914	Removing a condition from a conditional breakpoint on an arc was not possible after deleting the predicate from the Conditional (suspend when true) dialog, because doing so disabled the OK button. This was fixed.
SB‑24877	Limitations resolved in StreamBase 7.2.6 sometimes affected performance when Tuple fields in Java operators were accessed using Schema.Field objects. The performance problem was resolved.

Fixed in 7.3.5
Number	Resolution
TIBCO StreamBase® release 7.3.5 incorporates all fixes resolved in the release 7.2 series through 7.2.13, in the release 7.1 series through 7.1.12, and in the release 6.6 series through 6.6.25.
SB‑24720	Under certain circumstances, an unauthenticated user could dequeue tuples from StreamBase with the StreamBase Excel add-in. This bug has been fixed.
SB‑24678	Disconnecting from the StreamBase Monitor API could raise the error: `Attempted to read or write protected memory. This is often an indication that other memory is corrupt.` This has been fixed. Users of prior releases can call `StreamBaseMonitor.Close()` to avoid raising the error.
SB‑24659	The Aggregate operator's Predicate dimension now accepts boolean aggregate expressions for the closing and emitting from all windows in addition to boolean simple expressions. The Edit dimension dialog for predicate dimensions now has clarified descriptions for all of the predicate expressions. See Aggregate Operator: Predicate-Based Dimension Options for further details.
SB‑24590	In Studio, editing Java Operator properties of type "expression" had content assist that would offer stream qualified field names (e.g. `input1.myfield`). At runtime, this would result in an error such as: `In expression "input1.myfield" for field "CommandLine": the field "input1" is not available from any stream`. As expressions are configured to a particular input port, Studio was corrected to offer only unqualified field names from the applicable stream (e.g. `myfield`).
SB‑24312	StreamBase Studio would sometimes indicate the typecheck error 'Schema <name> uses an existing name' when referencing an imported Named Schema from a .sbint file, even when no such conflict existed. This has been fixed.
SB‑24236	Formerly, precompiled StreamBase application archive (`.sbar`) files generated on Windows failed to run on UNIX platforms with a `class not found` exception, and now they do. To fix an application you precompiled in Windows to avoid this problem, recompile it in the current version of StreamBase Studio.
SB‑24136	In prior 7.3 releases, when the system was overloaded with message volume and queues grew to their maximum size, processing could stall until a timeout period elapsed (default 1000 ms). This prevented new messages from being added to the queue, even if space became available in the queue sooner. Log messages would notify administrators of this condition. The queue behavior could reduce total throughput and increase jitter in an overload scenario. This has been fixed.

Fixed in 7.3.4
Number	Resolution
TIBCO StreamBase® release 7.3.4 incorporates all fixes resolved in the release 7.2 series through 7.2.11, in the release 7.1 series through 7.1.12, and in the release 6.6 series through 6.6.24.

Fixed in 7.3.3
Number	Resolution
TIBCO StreamBase® release 7.3.3 incorporates all fixes resolved in the release 7.2 series through 7.2.11, in the release 7.1 series through 7.1.12, and in the release 6.6 series through 6.6.24.
SB‑24210	Version 7.3.3 provides a more comprehensive fix for the issue of possible data corruption from concurrent calls from separate Java threads to `sendOutputAsync` on the same operator than the solution provided in 7.3.2.

Fixed in 7.3.2
Number	Resolution
TIBCO StreamBase® release 7.3.1 incorporates all fixes resolved in the release 7.2 series through 7.2.11, in the release 7.1 series through 7.1.12, and in the release 6.6 series through 6.6.23.
SB‑24368	Using IN for a case-sensitive index would trigger a table scan. This was changed.
SB‑24210	In previous versions of 7.3, concurrent calls from separate Java threads to `sendOutputAsync` on the same operator could lead to duplicate data values and data loss. This has been corrected.
SB‑24161	In previous releases, Join operator Output Settings with no prefixes were serialized incorrectly. Upon being reloaded, they were reordered and given default prefixes such as "input2_". Now empty prefixes are preserved and outputs are maintained in their original order.
SB‑24077	You can now define Eclipse Classpath Variables on the `sbbundle` command line. For more information, see What Was New in StreamBase 7.3.2
SB‑24015	If you added or removed fields from a schema for a data construct (such as a query table), the identity of the primary key would be lost, even if the modified field were unrelated to the primary index. Now you can modify such a schema without affecting the primary index.
SB‑23958	In previous releases, the predicate dimension fields expression for a control port to open, emit from, or close had to be a fully qualified field name (specified in dot notation, such as `input1.cost`). In StreamBase 7.3.1 and later, you can omit the qualifier and use just the field name in the expression.
SB‑23907	After hitting a breakpoint on an input stream's outgoing arc, the Variables view in the StreamBase Studio Debugger would be blank. The problem was that the line representing that arc in the Debug view was not automatically selected when the breakpoint was hit. This has been corrected.
SB‑23722	The number of instances of a module can be configured with an expression, and the expression will be evaluated at application startup.
SB‑22171	The `strftime` function now supports formatting instructions `%e`, `%k` and `%l`, which output a leading space instead of a leading zero for one-digit values.

Fixed in 7.3.1
Number	Resolution
TIBCO StreamBase® release 7.3.1 incorporates all fixes resolved in the release 7.2 series through 7.2.10, in the release 7.1 series through 7.1.12, and in the release 6.6 series through 6.6.23.
SB‑23933	If the Java source folder for custom Java operators, adapters, or functions was anything other than `java-bin` under a Studio project root (as could happen when using Maven to manage the Java files), then Studio was unable to load that operator, adapter, or function during typechecking of the project. Studio would report that the class could not be found. This was corrected.
SB‑23930	The XML-to-Tuple operator can populate tuple fields with XML attributes in one of two ways: (1) By using the special _ATTRIBUTES meta field, or (2) by creating a subfield with a name that matches the attribute name. The second technique was not working if the subfield's parent field was of type list<tuple>. This was fixed.
SB‑23912	In previous releases, the expression language's strptime() function incorrectly interpreted time strings that specified the noon hour as a timestamp 12 hours later. This was corrected.
SB‑23905	The upgrade to Eclipse 3.8 in StreamBase release 7.3 caused a regression that prevented the opening of Query Tables and dynamic variables in the Variables view of the EventFlow Debugger. The cause was identified and corrected.
SB‑23879	Two Unicode-handling bugs in StreamBase Studio were corrected. Even if Studio was configured to be Unicode ready with the `streambase.tuple-charset=UTF-8` setting, (1) the Copy as ... options in the context menu of the Application Output view would not correctly copy Unicode characters, and (2) the New StreamBase Unit Test wizard could garble Unicode characters in Java files created from the Application Output view.
SB‑23726	On Linux systems, an unpredictability in classpath loading order was resulting in a NullPointerException for the Alpha Trading Systems adapters. The classpath loading order was updated to assure a predictable order.
SB‑23608	When enqueuing with a C++ or Python client and specifying an input stream by stream name in the default container without its qualifying path (that is, "in" rather than "default.in"), a performance penalty was incurred because the client would repeatedly query the server for stream properties rather than using the client side cache. The workarounds were to manually cache the StreamProperties object or use full stream path name. This limitation was lifted and the workarounds are no longer necessary.
SB‑23485	In previous releases, an xi:include in a server configuration file could cause an error that referred to the Boost libraries when starting StreamBase Server as a Windows service. The cause was identified and corrected.

Fixed in 7.3.0
Number	Resolution
TIBCO StreamBase® release 7.3.0 incorporates all fixes resolved in the release 7.2 series through 7.2.8, in the release 7.1 series through 7.1.11, and in the release 6.6 series through 6.6.22.
SB‑23739	A busy loop that caused a thread in the IBM WebSphere MQ adapter to consume 100% of CPU time was identified and fixed.
SB‑23619	When using the Wombat MAMA Input adapter, subscriptions that failed with a NOT_FOUND error were correctly removed from the adapter, but the underlying Wombat subscription was not destroyed. This was fixed.
SB‑23602	An unusual race condition when starting multiple containers with synchronous container connections was fixed.
SB‑23336	Dynamic variables in StreamSQL programs were updated to allow recursively referencing themselves in an update expression.
SB‑23137	Documentation for previous 7.2.x releases continued to state that only jsbc enqueue could enqueue an empty tuple to an input stream defined with an empty schema. Actually, sbc enqueue gained that capability starting with 7.2.0.
SB‑22757	The .NET Client Library was updated to behave more like the Java Client Library in one respect. Previously, when a DequeueResult.Interceptor returned null, the null was returned to its caller, which interrupted dequeuing. Now a null case no longer interrupts dequeuing.
SB‑22961	The parsejson() expression language function, when used with expressions containing asterisk wildcards, could cause methods to grow beyond the Java 64K boundary. This was fixed.
SB‑21383	In previous releases, an internal error at runtime occurred for Filter operators that were followed by output streams with schemas explicitly set to have compatible but differently ordered fields. This was corrected.

Limitations Resolved in 7.2.x

Fixed in 7.2.16
Number	Resolution
Release 7.2.16 incorporates all fixes resolved in the release 7.1 series through 7.1.12, in the release 7.0 series through release 7.0.12, and in the release 6.6 series through release 6.6.25. See Limitations Resolved in 7.1.x, Limitations Resolved in 7.0.x, and Limitations Resolved in 6.6.x for details.
SB‑25420	The UBS Trading Components handler was not correctly parsing the tenor values submitted by the user. This has been fixed and the Tenor checking has also been updated to reflect version 1.19 of the UBS market data spec in relation to Tenor values allowed.
SB‑25146	Enabling dequeuing in sbadmin would start all output adapters regardless of their "Start with application" setting, moving them from NOT_YET_STARTED state to STARTED state when the container sent dequeue=ENABLED. Input adapters displayed the same behavior with the enqueue=ENABLED command. This has been fixed, so that these commands no longer implicitly start adapters.

Fixed in 7.2.15

Number Resolution

Release 7.2.15 incorporates all fixes resolved in the release 7.1 series through 7.1.12, in the release 7.0 series through release 7.0.12, and in the release 6.6 series through release 6.6.25. See Limitations Resolved in 7.1.x, Limitations Resolved in 7.0.x, and Limitations Resolved in 6.6.x for details.

SB‑24965 The XML to Tuple Java operator was excluding empty values of any type instead of parsing them as the NULL_VALUE_REPRESENTATION property value. This has been fixed.

SB‑24947

SB‑22083

The following fixes were made to the Exegy Input adapter:

The TradingAction event no longer fails with a null pointer exception when the Include Adapter Latency property is enabled.
Instead of always reporting as a refresh, Trading Action messages now report a trading action command.
You can now send conflation commands to the Exegy server by setting the maximum quote rate value for the adapter as well as sending an optional maxQuoteRate value with each subscription input.
Instead of reporting null values, dictionary output tuples now are populated correctly.

SB‑24891 Restarting an initiator application for a StreamBase FIX adapter failed when an alternate FIX dictionary was being used. This has been fixed.

SB‑23684 A warning message for the Morningstar Quotes Feed Input adapter was updated to display the Feed Type to help diagnose instances when it may be incorrectly set.

SB‑23356 A race condition can lead to occasional null pointer exceptions that surface in the Log adapter when the adapter is configured for asynchronous logging. This has been fixed.

SB‑22686

Fixed in 7.2.14
Number	Resolution
Release 7.2.14 incorporates all fixes resolved in the release 7.1 series through 7.1.12, in the release 7.0 series through release 7.0.12, and in the release 6.6 series through release 6.6.25. See Limitations Resolved in 7.1.x, Limitations Resolved in 7.0.x, and Limitations Resolved in 6.6.x for details.
SB‑24939	The .NET Client API methods StreamBaseClient.Enqueue(String, List<Tuple>) only enqueued the first tuple in the given list rather than all tuples in the list. This was fixed.
SB‑24919	The all-in rate for spot legs was populated from the bid/ask tuple's spotRate field rather than its allInRate field. This was corrected.
SB‑24877	Limitations resolved in StreamBase 7.2.6 sometimes affected performance when Tuple fields in Java operators were accessed using Schema.Field objects. The performance problem was resolved.

Fixed in 7.2.13
Number	Resolution
Release 7.2.13 incorporates all fixes resolved in the release 7.1 series through 7.1.12, in the release 7.0 series through release 7.0.12, and in the release 6.6 series through release 6.6.25. See Limitations Resolved in 7.1.x, Limitations Resolved in 7.0.x, and Limitations Resolved in 6.6.x for details.
SB‑24823	The XML-to-tuple operator incurs a null pointer exception during the validation of an ATTRIBUTES field in the Edit Schema tab if the field is of type `list` but the list element is not of type `tuple`. This was fixed.
SB‑24792	The `VenueTime` field is now populated in top- and depth-of-book tuples by the DB Classic and Rapid FIX market data handlers.
SB‑24766	When set up to connect to alias queues, the IBM WebSphere MQ Input and Output Adapters also connect to the underlying base queue to promptly detect failed connections to the MQ server. Now, when connecting to an alias queue, the adapters still open the base queue, but with inquire access only.
SB‑24762	The `VenueName` field is now populated by the Deutsche Bank AutobahnFX Classic and Rapid FIX market data handlers.
SB‑24655	The 29West input and output adapters can now exchange nested pre-defined messages with non-StreamBase applications.
SB‑24485	The FXall provider adapter was upgraded to support FXall TCPI 4.0.0.1. In particular, An optional `MidRate` field was added to the price leg schema and `FixingDate`, `MidRate`, and `USILeg` fields were added to the leg schema.
SB‑24172	A .NET client that invoked `Tuple.SetField("top.nested",value)` when field `top` was null could generate a Null Pointer Exception. This was fixed.

Fixed in 7.2.12
Number	Resolution
Release 7.2.12 incorporates all fixes resolved in the release 7.1 series through 7.1.12, in the release 7.0 series through release 7.0.12, and in the release 6.6 series through release 6.6.24. See Limitations Resolved in 7.1.x, Limitations Resolved in 7.0.x, and Limitations Resolved in 6.6.x for details.
SB‑24572	In populating tuple fields of type timestamp from XML attributes, the XMLToTuple operator's Date/Time Format property was being ignored, and the timestamp was being treated as an interval rather than an absolute time. This was fixed.
SB‑24478	In previous releases, the Log Output adapter would sometimes perform unnecessary tuple transformations, leading to worse performance. This was fixed.
SB‑24457	The Saxo Bank FIX adapter now contains a new class, SaxoQFJMessageInterceptor, to complete the adapter functionality.

Fixed in 7.2.11
Number	Resolution
Release 7.2.11 incorporates all fixes resolved in the release 7.1 series through 7.1.12, in the release 7.0 series through release 7.0.12, and in the release 6.6 series through release 6.6.24. See Limitations Resolved in 7.1.x, Limitations Resolved in 7.0.x, and Limitations Resolved in 6.6.x for details.
SB‑24214	The IBM WebSphere MQ input adapter was not reporting connection-down errors for some error codes. This was fixed.
SB‑24198	The `format` function, when it received a null, would sometimes incorrectly return a previously received non-null value. This was fixed.
SB‑24066	Query Operators lost their match settings when connected to Query Tables whose schemas were imported from Event Flow applications with typecheck errors. This was fixed.
SB‑24052	Parent fields for some imported schemas were sometimes unavailable from the Properties View tab. This was fixed.
SB‑24034	Name collisions between imported schemas' names and group names caused loading errors. The groups are now automatically renamed to prevent these errors.
SB‑23962	In certain cases, the `calljava` method with a null argument incorrectly errored. This was fixed.
SB‑23830	A StreamBase Studio restart would remove the Own-Thread option from an existing, saved Extension Point operator. This was fixed.
SB‑23703	Studio did not automatically add a file extension prior to checking for filename conflicts when a file had the same basename as its containing directory. This was fixed.
SB‑18565	Editing a table's secondary index field sometimes reset the Order property of the associated Query operators. This was fixed.

Fixed in 7.2.11
Number	Resolution
Release 7.2.11 incorporates all fixes resolved in the release 7.1 series through 7.1.12, in the release 7.0 series through release 7.0.12, and in the release 6.6 series through release 6.6.24. See Limitations Resolved in 7.1.x, Limitations Resolved in 7.0.x, and Limitations Resolved in 6.6.x for details.
SB‑24129	If a marketfeed message in the Reuters adapter contained one or more invalid enumeration field values and the adapter's Send Enum Field Display Values was set, a message was incorrectly dropped. This was fixed.
SB‑24054	The StreamBase .NET API tuple-field data accessors showed poor performance when using the GetField method to get null-valued fields. This was fixed.
SB‑24033	If a user had multiple EventFlow editor windows open, and used the Add Note hotkey (/) to add a note in one open window and then switched windows without first closing the note, the note editor would remain active in the first window, rather than the active window. This means that any successive attempts to add notes in other windows would be saved to the original window, rather than the active window. This was fixed.

Fixed in 7.2.10
Number	Resolution
Release 7.2.10 incorporates all fixes resolved in the release 7.1 series through 7.1.12, in the release 7.0 series through release 7.0.12, and in the release 6.6 series through release 6.6.23. See Limitations Resolved in 7.1.x, Limitations Resolved in 7.0.x, and Limitations Resolved in 6.6.x for details.
SB‑23933	If the Java source folder for custom Java operators, adapters, or functions was anything other than `java-bin` under a Studio project root (as could happen when using Maven to manage the Java files), then Studio was unable to load that operator, adapter, or function during typechecking of the project. Studio would report that the class could not be found. This was corrected.
SB‑23930	The XML-to-Tuple operator can populate tuple fields with XML attributes in one of two ways: (1) By using the special _ATTRIBUTES meta field, or (2) by creating a subfield with a name that matches the attribute name. The second technique was not working if the subfield's parent field was of type list<tuple>. This was fixed.
SB‑23912	In previous releases, the expression language's strptime() function incorrectly interpreted time strings that specified the noon hour as a timestamp 12 hours later. This was corrected.
SB‑23879	Two Unicode-handling bugs in StreamBase Studio were corrected. Even if Studio was configured to be Unicode ready with the `streambase.tuple-charset=UTF-8` setting, (1) the Copy as ... options in the context menu of the Application Output view would not correctly copy Unicode characters, and (2) the New StreamBase Unit Test wizard could garble Unicode characters in Java files created from the Application Output view.
SB‑23853	For 64-bit platforms, the .NET and C++ clients would sometimes not release Windows handles after a connection was terminated, so subsequent connection attempts would increase the handle counts. This was fixed.
SB‑23739	A busy loop that caused a thread in the IBM WebSphere MQ adapter to consume 100% of CPU time was identified and fixed.
SB‑23726	On Linux systems, an unpredictability in classpath loading order was resulting in a NullPointerException for the Alpha Trading Systems adapters. The classpath loading order was updated to assure a predictable order.
SB‑23619	When using the Wombat MAMA Input adapter, subscriptions that failed with a NOT_FOUND error were correctly removed from the adapter, but the underlying Wombat subscription was not destroyed. This was fixed.
SB‑23608	When enqueuing with a C++ or Python client and specifying an input stream by stream name in the default container without its qualifying path (that is, "in" rather than "default.in"), a performance penalty was incurred because the client would repeatedly query the server for stream properties rather than using the client side cache. The workarounds were to manually cache the StreamProperties object or use full stream path name. This limitation was lifted and the workarounds are no longer necessary.
SB‑23602	An unusual race condition when starting multiple containers with synchronous container connections was fixed.
SB‑23485	In previous releases, an xi:include in a server configuration file could cause an error that referred to the Boost libraries when starting StreamBase Server as a Windows service. The cause was identified and corrected.
SB‑23137	Documentation for previous 7.2.x releases continued to state that only jsbc enqueue could enqueue an empty tuple to an input stream defined with an empty schema. Actually, sbc enqueue gained that capability starting with 7.2.0.
SB‑22757	The .NET Client Library was updated to behave more like the Java Client Library in one respect. Previously, when a DequeueResult.Interceptor returned null, the null was returned to its caller, which interrupted dequeuing. Now a null case no longer interrupts dequeuing.

Fixed in 7.2.9
Number	Resolution
Release 7.2.9 incorporates all fixes resolved in the release 7.1 series through 7.1.11, in the release 7.0 series through release 7.0.12, and in the release 6.6 series through release 6.6.22. See Limitations Resolved in 7.1.x, Limitations Resolved in 7.0.x, and Limitations Resolved in 6.6.x for details.
SB‑23770	In recent 7.2.x releases, when developing a custom Java operator or adapter, if your custom class cannot load at runtime in Studio (perhaps because it failed to build), the settings in the Properties view for your operator or adapter would be inadvertently cleared. This was corrected so that a failure-to-load error no longer clears any Properties view settings.

Fixed in 7.2.8
Number	Resolution
Release 7.2.8 incorporates all fixes resolved in the release 7.1 series through 7.1.11, in the release 7.0 series through release 7.0.12, and in the release 6.6 series through release 6.6.22. See Limitations Resolved in 7.1.x, Limitations Resolved in 7.0.x, and Limitations Resolved in 6.6.x for details.
SB‑23428	The format of ContainerConnectionException error messages was updated to include the source container name, connection name, and endpoint name, in cases where this information is available.
SB‑23401	The Thomson Reuters Schema Designer was updated to map Reuters type OMMTypes.UINT64 to StreamBase type long.
SB‑23355	A Query Read operation was returning an incorrect result set if the range criteria for one of the index fields had a begin-to-end specification followed by an index field having a null specification. This was fixed.
SB‑23351	When using Log4j as the logging back end with asynchronous loggers, queues log messages could get dropped on shutdown. This was fixed.
SB‑23347	When using the StreamBaseFIX FIX engine's session handling, where a pending TestRequest would still be considered pending even after a disconnection-reconnection cycle.
SB‑23206	The StreamBaseFIX FIX engine now correctly use username and password, in lowercase as shown, to fetch these settings in the StreamBaseFIX configuration file, to match the sample configuration file and the documentation.
SB‑22942	A NullPointerException error could be thrown when using the EventFlow Debugger to try to see the values of a list stored in a Query Table. The debugger supports viewing lists in tuples in an arc, but not in Query Tables. The attempt to view lists in Query Tables is now correctly blocked, and no longer throws the error.
SB‑22299	When using the EventFlow debugger, breakpoints before Error Output Streams were not hit. This was corrected.
SB‑20483	In previous releases, opening the Breakpoint Properties dialog for an arc resulted in a large, empty dialog with a few lines of unhelpful text. This dialog is now fully populated with information that applies to the selected arc, and also supports the new conditional breakpoints feature.

Fixed in 7.2.7
Number	Resolution
Release 7.2.7 incorporates all fixes resolved in the release 7.1 series through 7.1.11, in the release 7.0 series through release 7.0.12, and in the release 6.6 series through release 6.6.22. See Limitations Resolved in 7.1.x, Limitations Resolved in 7.0.x, and Limitations Resolved in 6.6.x for details.
SB‑23277	An otherwise valid EventFlow module with Chinese characters in an operator's Description text would fail typechecking, despite having both Server and Studio Unicode settings as described in Unicode Support. The cause was identified and corrected.
SB‑23252	In previous releases, under certain conditions, embedded adapters would incorrectly use the containing server's log level setting instead of the adapter's independent log level setting. The conditions were: the STREAMBASE_USE_CUSTOM_LOGGING environment variable was set to `true`, and the adapter was configured to log at the same or a less verbose level than the server. This was corrected.
SB‑23230	The Thomson Reuters TREP-RT Subscribing Input adapter was incurring an exception in processing a market price message for each field not present in the adapter's schema, leading to less than optimal performance. This issue occurred only when the adapter's Disable Market Price View Requests was enabled (not the default), or when processing messages from a Thomson Reuters server that does not support view requests. The adapter was updated to respond correctly to these situations.
SB‑23072	Query Table updates using a large number of fields were running into the JVM's 64K size limit for methods. The generation of these methods was optimized to reduce their size and allow more fields to be present.
SB‑23047	A Query that contained a range bound, followed by an equality bound, where the equality bound was checking for nulls, always returned no results in previous 7.2.x releases. This was fixed.
SB‑22930	In 6.6.x releases, double-clicking an entry in the Problems view both opened the affected EventFlow module and selected the operator with the problem. In previous 7.x releases, the same double-click opened the affected module but failed to select the affected operator. This was corrected such that the 6.6 behavior was restored.

Fixed in 7.2.6
Number	Resolution
Release 7.2.6 incorporates all fixes resolved in the release 7.1 series through 7.1.10, in the release 7.0 series through release 7.0.12, and in the release 6.6 series through release 6.6.21. See Limitations Resolved in 7.1.x, Limitations Resolved in 7.0.x, and Limitations Resolved in 6.6.x for details.
SB‑23043	In previous releases, a NullPointerException could result when deleting a parent schema from the EventFlow Editor's Definitions tab. This was fixed.
SB‑23030	On Windows with release 7.2.5, StreamBase Server launched from the StreamBase Command Prompt could fail or hang under some circumstances if the server configuration file included XML comments. This was fixed.
SB‑23000	When using the EventFlow Debugger without the Debug view open, breakpoints were hit but navigation to the hit breakpoint in the EventFlow Editor could not be shown. Starting with 7.2.6, on a breakpoint hit, the Debug view is opened if not already open.
SB‑22997	After upgrading to release 7.2.5, a 7.1.x application that uses shared and placeholder Query Tables was failing to typecheck in Studio. The cause was identified and corrected.
SB‑22976	When using the O E keyboard shortcut to place a Module Reference on the canvas, the gray data port did not initially appear if the referenced module contained only a shared Query Table. This was corrected.
SB‑22971	A RuntimeException could occur when using the readTable API to read from a Query Table configured with a capture field. This was fixed.
SB‑22958	In the .NET Client Library, `DequeueResult.GetTupleCount()` was returning null instead of 0 when `Status==DequeueResult.TIMEOUT`. This was corrected.
SB‑22837	A leak of Path resource memory from the graphics rendering code that supports Studio was corrected.
SB‑22752	The prerequisites for the RPM method of installing StreamBase on Linux were updated so that installing StreamBase does not automatically require third-party libraries.
SB‑22731	In previous 7.2.x releases, disk-based Query Tables with indexes that contained lists before the final element of the index could result in `Unexpected tag` messages on the Console view. This was fixed.
SB‑22706	The expression language's `new_tuple()` function could grow beyond the Java 64 Kbyte limit when given schemas with over 60 fields. The function was refined to allow much larger schemas.
SB‑22675	In previous 7.2.x releases, Query operators could return an unexpected result set when the table was accessed through a module reference. This was corrected.
SB‑22628	When using the EventFlow Debugger, a ClassNotLoadedException could occur when expanding a tuple variable in the Variables view. This was fixed.
SB‑22422	A race condition on startup of StreamBase Server was affecting LiveView Server startup. The cause was identified and corrected.
SB‑22249	The error message that resulted from a failure to provide a numerical argument for the `-x` option of the sbfeedsim command was misleading. This was corrected with better error messages.
SB‑21839	The TableAccesor.delete() method did not provide a way to report a no-match result. This was corrected.
SB‑21487	Studio could show an Error Log view error when deleting a project that had a file open in Studio. This was fixed.

Fixed in 7.2.5
Number	Resolution
Release 7.2.5 incorporates all fixes resolved in the release 7.1 series through 7.1.9, in the release 7.0 series through release 7.0.12, and in the release 6.6 series through release 6.6.20. See Limitations Resolved in 7.1.x, Limitations Resolved in 7.0.x, and Limitations Resolved in 6.6.x for details.
SB‑22584	Red error text in the Properties view of the Aggregate operator was not being cleared when the error condition was resolved. This was corrected.
SB‑22548	When using the EventFlow Debugger, attempts to traverse a call stack could intermittently encounter a failure with a "source not found" error and an "invalid stack frame" exception. This issue was resolved.
SB‑22530	When using the EventFlow Debugger, a DebugException with ObjectCollectedException error could appear in the Error Log View in rare cases when an internal call from the debugger to the debugged process failed because an argument in the call happened to be garbage collected before the remote call was able to start. This was fixed.
SB‑22500	When using the EventFlow Debugger, three question marks could appear for the value of a timestamp field in the Variables view, with a ThreadNotSuspendedException appearing at the same time in the Error Log view. This was corrected.
SB‑22413	TIBCO discourages editing a project's server configuration file, or one of its component fragment files, in another editor outside of Studio while Studio is running. Nevertheless, if you do so, and forget to refresh the Studio project after such edits but before running Refresh Typecheck Environment, Studio no longer throws a Class Error.
SB‑22408, SB‑22364	In releases 7.2.3 and 7.2.4, Studio could lock up when attempting to edit a server configuration file with one or more `<xi:include>` statements. This was corrected.
SB‑22370	The Thomson Reuters TREP-RT Subscribing Input adapter was updated to move its one-time initialization code to a later state of the adapter's start-up sequence. This avoids "time out on state change" errors.
SB‑22356	In previous 7.2.x releases, properties for the currently selected Query operator were sometimes observed to load slowly into the Properties view. This was corrected, providing a significant speedup in property loading.
SB‑22006	In previous 7.2.x releases, in a Query operator with Write-Update operation, set actions in the Additional Expressions grid sometimes failed to be reflected in the table fields pane on the left. This was fixed.

Fixed in 7.2.4
Number	Resolution
Release 7.2.4 incorporates all fixes resolved in the release 7.1 series through 7.1.8, in the release 7.0 series through release 7.0.12, and in the release 6.6 series through release 6.6.19. See Limitations Resolved in 7.1.x, Limitations Resolved in 7.0.x, and Limitations Resolved in 6.6.x for details.
SB‑22346	In previous 7.2.x releases, a Query operator with Write-Insert operation and the If row exists selection Update existing row using values in Fallback, could replace table values with null. This was corrected.
SB‑22330	In previous 7.2.x releases, a Query operator with Write-Update operation upgraded from a pre-7.2 release could display an empty Action column in the Properties view Operation tab. This was fixed to show the Set action.
SB‑22327	In previous 7.2.x releases, a Query operator with Write-Update operation used in a hygienic module could emit unexpected data as output. This was fixed.
SB‑22318	EventFlow modules that use imported schemas or definitions could get flagged as needing to be saved despite having no changes in the module itself, in cases when an imported resource changed in its original location. This was corrected.
SB‑22317	In previous releases, if you copied a Module Reference and disconnected the copy, the original Module Reference could lose its table association in the Tables tab of its Properties view. This was corrected.
SB‑22315	In previous releases, using the Debug view's Terminate button would stop the debug session, then halt the running StreamBase Server instance without its usual shutdown procedures. This sequence of operations could fail to delete the disk Query Tables’ lock directory, which would then require deleting the lock directory manually before restarting the application. The Debug view's Terminate button was updated to perform the same clean shutdown of the Server as the Stop button in the top-level Studio toolbar.
SB‑22305	In previous 7.2.x releases, the server could throw a ClassCastException when a Query Table was connected through Module References to an inner module with at least two levels of capture fields with identical schemas. This was fixed.
SB‑22302	When using the StreamBase to StreamBase adapters with their Low Latency property disabled, duplicate data could be delivered in place of expected data. The cause was identified and corrected.
SB‑22300	The error messages "missing parameter table" and "missing parameter operation" were revised to more clearly describe the problem using EventFlow terminology. In general, typecheck error messages that can be thrown by the server runtime were reviewed and updated for clarity and EventFlow relevance.
SB‑22223	In previous 7.2.x releases, the indexof() function for lists of tuples became inadvertently sensitive to field order. The behavior of the function in 7.1.x was restored.
SB‑22133	A client application built with the .NET Client Library and the .NET 4 framework could result in multiple System.IndexOutOfRangeException errors. This was corrected.
SB‑22098, SB‑22099	In the Aggregate operator, the expression used for the opening policy is evaluated in a non-aggregate context and thereby must resolve to a simple function. In previous releases, no error or warning was issued if you used an aggregate function in the opening policy expression, and the module resulted in a NullPointerException at runtime. This case now has shows a typecheck error.
SB‑22092	When the Union operator detects a schema mismatch, Studio shows a SchemaMismatchException error. The (go to error) and (compare schemas) links were moved to the beginning of the tooltip message for this error so that they are always available even for very wide schemas.

Fixed in 7.2.3
Number	Resolution
Release 7.2.3 incorporates all fixes resolved in the release 7.1 series through 7.1.8, in the release 7.0 series through release 7.0.12, and in the release 6.6 series through release 6.6.19. See Limitations Resolved in 7.1.x, Limitations Resolved in 7.0.x, and Limitations Resolved in 6.6.x for details.
SB‑22259	The Wombat MAMA Publishing Output adapter was updated to clarify WARN log messages from the adapter that occur when the feed dictionary changes, but the application still expects a field with a type defined in the previous dictionary.
SB‑22253	In previous releases, when processing millions of tuples, if queues become very backed up, StreamBase Server begins to manage memory growth. After emitting WARN log messages about the queue backup, under certain rare conditions, some amount of queue data could be lost or inappropriately replayed. The cause was identified and corrected.
SB‑22234	In previous 7.2.x releases, a Query Table that used a table schema, which in turn was composed with a parent schema would show incorrect red X typecheck error icons in the table's Properties view. This was corrected.
SB‑22214	A typecheck error could occur on a Once adapter when the same module had a locally defined table schema that used a locally defined named schema. This was fixed.
SB‑22209	An IndexOutOfBoundsException error was generated when renaming a table schema without using Refactor → Rename. This was fixed.
SB‑22183, SB‑22178	In previous 7.2.x releases, the default setting for the Query operator's Operation tab was changed compared to release 7.1. As of 7.2.3, this tab's default for the If no rows are found selection is restored to match input with null values both for new Query operators and those upgraded to 7.2 from existing modules.
SB‑22176	In previous 7.2.x releases, the Sequence operator was missing its default values. This was corrected.
SB‑22134	In projects upgraded to 7.2, some Query operators associated with Module References were reporting an incorrect typecheck failure about undefined tables. This was fixed.
SB‑22091, SB‑21514	When using the EventFlow Debugger in previous releases, changing the value of a variable in the Variables view would fail, resulting in an error. A similar error could result from changing a dynamic variable in the Variables view. These conditions no longer generate an error.
SB‑22087	In projects upgraded to 7.2, Query operators could sometimes appear with no input grid in the Output tab; closing and reopening the module would restore the input grid, but in the wrong location in the tab. The cause was identified and corrected.
SB‑22017	Arc bend points on the EventFlow canvas were not correctly restored when reloading a module. This was fixed.
SB‑21890	In previous 7.2.x releases, when you specified a Query operator with Delete operation, and also specified Where: All rows, the Order control was incorrectly activated. This was fixed.
SB‑21805	When you enabled an error port on operators with no output ports, an error dialog would result, even though the error port was created correctly. The appearance of the error dialog was corrected.
SB‑20398	The Copy Schema From dialog was updated to include output streams as a source of schemas to copy.

Fixed in 7.2.2
Number	Resolution
Release 7.2.2 incorporates all fixes resolved in the release 7.1 series through 7.1.7, in the release 7.0 series through release 7.0.12, and in the release 6.6 series through release 6.6.18. See Limitations Resolved in 7.1.x, Limitations Resolved in 7.0.x, and Limitations Resolved in 6.6.x for details.
SB‑22090	In some cases, a Map operator created in recent 7.1.x releases would show empty settings in the Properties view's Output Settings tab after importing into release 7.2. This was corrected.
SB‑22027	In previous 7.2 releases, a Query operator performing a Write operation exhibited different output behavior depending on the Fallback option selected. This was fixed.

Fixed in 7.2.1
Number	Resolution
Release 7.2.1 incorporates all fixes resolved in the release 7.1 series through 7.1.7, in the release 7.0 series through release 7.0.12, and in the release 6.6 series through release 6.6.18. See Limitations Resolved in 7.1.x, Limitations Resolved in 7.0.x, and Limitations Resolved in 6.6.x for details.
SB‑22072	In previous releases, long-running, high-volume enqueuing clients could, in some circumstances, exhaust StreamBase Server's input queue buffer capacity, resulting in a disconnected client after the connection timed out. This was corrected.
SB‑21799	The error message caused by exceeding the maximum input packet size was clarified and improved.
SB‑21589	In previous releases, if you dragged the left side of an arc from an input stream and reconnected the arc to another component, the arc incorrectly gained a declared schema, using the schema of the input stream. This was corrected.
SB‑20656	The Wombat MAMA Output adapter was verified to work over the TIBCO Rendezvous (RV) transport. You must obtain a Wombat library version that supports RV and is at least version 5.0.4 or later.

Fixed in 7.2.0
Number	Resolution
Release 7.2.0 incorporates all fixes resolved in the release 7.1 series through 7.1.6, in the release 7.0 series through release 7.0.11, and in the release 6.6 series through release 6.6.17. See Limitations Resolved in 7.1.x, Limitations Resolved in 7.0.x, and Limitations Resolved in 6.6.x for details.
SB‑21768	The schema for the status port of the FXall Relationship Trading Provider adapter was optimized to use current StreamBase APIs.
SB‑21655	When using the optional StreamBaseFIX FIX engine, FIX tag values greater than about 33000 resulted in an error when loading the data dictionary. This was corrected.
SB‑20785	In previous releases, the Copy Schema From dialog included imported schemas when showing the available schemas from a particular module. The was corrected to show only locally defined schemas for each module.
SB‑19477	Removing a nested field from a null tuple in a Map operator now leaves the tuple as null, instead of changing it to a tuple filled with nulls. For example, if you send the tuple `(top(a,b,c))` to a Map operator that drops field `b`, the resulting tuple is `(top(a,c))`. If top is null before the Map, now it is null after the Map.
SB‑17246	The Trace Debugger would sometimes leave its color highlight in place after returning to the SB Authoring perspective. This was fixed.
SB‑13271	Previous releases of the .NET Client Library did not provide a way to construct a new DequeueResult, while the Java Client Library provided SimpleDequeueResult for this purpose. This situation was corrected in the October 2011 refresh of the .NET API with the addition of the DequeueResult constructors. See Migrating .NET Clients.
SB‑12662	In previous releases of the .NET Client Library, using `IsNull("wrong_field_name")` threw the generic SEHException instead of StreamBase.SB.NoSuchFieldException. This situation was corrected in the October 2011 refresh of the .NET API as described above.

Limitations Resolved in 7.1.x

Fixed in 7.1.13
Number	Resolution
Release 7.1.13 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.2x. See Limitations Resolved in 7.0.x and Limitations Resolved in 6.6.x for details.
SB‑24487	Previously, the QF/J options to use a JDBC message store could not be used in a FIX config file supplied to the SB FIX adapter. The message "quickfix.ConfigError: FileStorePath not defined" is symptomatic of this condition. This was corrected.
SB‑24485	The FXall provider adapter was upgraded to support FXall TCPI 4.0.0.1. In particular, An optional `MidRate` field was added to the price leg schema and `FixingDate`, `MidRate`, and `USILeg` fields were added to the leg schema.
SB‑23933	If the Java source folder for custom Java operators, adapters, or functions was anything other than `java-bin` under a Studio project root (as could happen when using Maven to manage the Java files), then Studio was unable to load that operator, adapter, or function during typechecking of the project. Studio would report that the class could not be found. This was corrected.
SB‑23912	In previous releases, the expression language's strptime() function incorrectly interpreted time strings that specified the noon hour as a timestamp 12 hours later. This was corrected.
SB‑23155	In previous releases, importing a 7.0.x project into 7.1.x that used JDBC query with the USE CALLABLE parameter set to FALSE, a migration step was required to force Studio to ignore the JDBC index. This step is not longer required.

Fixed in 7.1.12
Number	Resolution
Release 7.1.12 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.23. See Limitations Resolved in 7.0.x and Limitations Resolved in 6.6.x for details.
SB‑23726	On Linux systems, an unpredictability in classpath loading order was resulting in a NullPointerException for the Alpha Trading Systems adapters. The classpath loading order was updated to assure a predictable order.
SB‑23619	When using the Wombat MAMA Input adapter, subscriptions that failed with a NOT_FOUND error were correctly removed from the adapter, but the underlying Wombat subscription was not destroyed. This was fixed.
SB‑23252	In previous releases, under certain conditions, embedded adapters would incorrectly use the containing server's log level setting instead of the adapter's independent log level setting. The conditions were: the STREAMBASE_USE_CUSTOM_LOGGING environment variable was set to `true`, and the adapter was configured to log at the same or a less verbose level than the server. This was corrected.
SB‑23230	The Thomson Reuters TREP-RT Subscribing Input adapter was incurring an exception in processing a market price message for each field not present in the adapter's schema, leading to less than optimal performance. This issue occurred only when the adapter's Disable Market Price View Requests was enabled (not the default), or when processing messages from a Reuters server that does not support view requests. The adapter was updated to respond correctly to these situations.
SB‑22757	The .NET Client Library was updated to behave more like the Java Client Library in one respect. Previously, when a DequeueResult.Interceptor returned null, the null was returned to its caller, which interrupted dequeuing. Now a null case no longer interrupts dequeuing.

Fixed in 7.1.11
Number	Resolution
Release 7.1.11 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.22. See Limitations Resolved in 7.0.x and Limitations Resolved in 6.6.x for details.
SB‑23602	An unusual race condition when starting multiple containers with synchronous container connections was fixed.
SB‑23156, SB‑23157	When migrating a module written with release 7.0.x to 7.1, Query-JDBC operators that used explicitly set schemas in the Result Settings tab were not correctly migrated, and the Output Settings tab was incorrectly set to SQL Result Fields=None. The cause was identified and corrected.
SB‑23111	The IBM WebSphere MQ output adapter was updated to not attempt to read the depth of remote queues, which was causing the adapter to incorrectly report a connection-down state.
SB‑23106	The TREP-RT Publishing Output adapter could fail to service download requests for very large data dictionaries. This was fixed.
SB‑23030	On Windows, starting with release 7.1.9, StreamBase Server launched from the StreamBase Command Prompt could fail or hang under some circumstances if the server configuration file included XML comments. This was fixed.
SB‑22958	In the .NET Client Library, `DequeueResult.GetTupleCount()` was returning null instead of 0 when `Status==DequeueResult.TIMEOUT`. This was corrected.
SB‑22930	In 6.6.x releases, double-clicking an entry in the Problems view would both open the affected EventFlow module and select the operator with the problem. In previous 7.x releases, the same double-click would open the affected module but not select the affected operator. This was corrected such that the 6.6 behavior was restored.
SB‑22837	A leak of Path resource memory from the graphics rendering code that supports Studio was corrected.
SB‑22740	In previous 7.1.x releases, an error resulted when trying to store a null value of type list(tuple) into a disk-based Query Table. This was fixed.

Fixed in 7.1.10
Number	Resolution
Release 7.1.10 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.21. See Limitations Resolved in 7.0.x and Limitations Resolved in 6.6.x for details.
SB‑22785	On rare occasions, client applications authored in C++ and .NET could spontaneously disconnect from StreamBase Server. The cause was isolated and corrected.
SB‑22768	The FIX data dictionary for the 360T SuperSonic TEX adapter, although in compliance with 360T's specification, was sending the QuoteCondition field out of order. The data dictionary was corrected to match actual practice.
SB‑22729	The reference page for the sbargen command (and the corresponding man page on UNIX) were corrected to remove the `-d` and `-n` options.
SB‑22728	A minor issue with Group-By expressions in Query Table Read operations that access fields in the table was found and fixed.
SB‑22708	The wording of a queue updating message was changed to more accurately reflect the condition reported. This message previously reported "`Deadlock detected: queue-path, queue expanding by nn tuples.`" While a deadlock was very remotely possible under those conditions, the message was only meant to convey that the server had to expand this queue because the consumer side of the queue was consuming slower than the producer side was producing. The new wording for this message is: `WARN: FQ classname - Queue queue-path expanding by nnn tuples because the consumer is slower than the producer. Waited ttt milliseconds.`
SB‑22682	In previous releases, when a feed simulation encountered read errors as it attempted to read an input CSV file, the error message emitted did not provide adequate information. As of this release, the error message under these conditions now includes the failing stream name and the line number in the failing file, in addition to the message text.
SB‑22627	The Wombat Publishing adapter was inadvertently truncating integers to shorts in populating I32 message fields. This was corrected.
SB‑22578	In previous releases of StreamBase Studio, in the Manual Input view, when you used command completion to fill in the current date and time in a timestamp field, the timestamp entered did not update to match current time. This was fixed.
SB‑22553	StreamBase Server could throw a StringIndexOutOfBounds exception and halt under conditions related to an unexpectedly abbreviated month specification when using the strptime() function. This was corrected with a new, more informative error message, and an error condition that is handled by the error streams system normally.
SB‑22370	The Thomson Reuters TREP-RT Subscribing Input adapter was updated to move its one-time initialization code to a later state of the adapter's start-up sequence. This avoids "time out on state change" errors.
SB‑21756	In previous releases, StreamBase Studio could throw a Keybinding conflicts error. The cause was traced to an unclosed tooltip and corrected.

Fixed in 7.1.9
Number	Resolution
Release 7.1.9 incorporated 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.20. See Limitations Resolved in 7.0.x and Limitations Resolved in 6.6.x for details.
SB‑22540	The Thomson Reuters Enterprise Platform for Real-Time (TREP-RT) Subscribing Input adapter (formerly named the Thomson Reuters RMDS Subscribing adapter) was using a non-thread-safe OMM encoder and was thereby incurring random errors when initial and dynamic subscriptions were processed concurrently. This problem was corrected.
SB‑22538	The TREP-RT Subscribing Input adapter previously supported the "Include Marketfeed Field_List_No Header Field" property only for the Market Feed message model. This property is now supported for Market Price model as well. The property name, as seen in the Tuple Properties tab, is now Include Field List Number Field.
SB‑22534	The TREP-RT Subscribing Input adapter was inconsistent between Market Feed and Market Price with respect to the tuples it emitted when a non-existent item was subscribed to. Previously, the adapter emitted closed tuples on both the events and market data ports for Market Feed (RMDS 5) but only on the market data port for Market Price (RMDS 6). To be consistent with its Market Feed behavior, the adapter now emits closed tuples on both ports for Market Price.
SB‑22516	The TREP-RT Subscribing Input adapter was updated to emit at least one tuple per market by order or market by price refresh message.
SB‑22442	The data dictionary file for the Currenex adapter was inadvertently removed from recent releases, but is now restored.
SB‑22408, SB‑22364	In release 7.1.8, Studio could lock up when attempting to edit a server configuration file with one or more `<xi:include>` statements. This was corrected.
SB‑22375	A Quick Fix wizard to remove unused imports was added in release 7.1.8. However, in cases where there were multiple unused imports in the same file, the Quick Fix removed only the first instance. This was corrected.
SB‑22365	The C++ and .NET Client Libraries were updated with better queue management. Clients now pause high-rate dequeuing from the server if the internal queues back up, to prevent excessive memory consumption.
SB‑22317	In previous releases, if you copied a Module Reference and disconnected the copy, the original Module Reference could lose its table association in the Tables tab of its Properties view. This was corrected.
SB‑22302	When using the StreamBase to StreamBase adapters with their Low Latency property disabled, duplicate data could be delivered in place of expected data. The cause was identified and corrected.
SB‑22259	The Wombat MAMA Publishing Output adapter was updated to clarify WARN log messages from the adapter that occur when the feed dictionary changes, but the application still expects a field with a type defined in the previous dictionary.
SB‑22253	In previous releases, when processing millions of tuples, if queues become very backed up, StreamBase Server begins to manage memory growth. After emitting WARN log messages about the queue backup, under certain rare conditions, some amount of queue data could be lost or inappropriately replayed. The cause was identified and corrected.
SB‑22252, SB‑21433	When dragging an operator from the Palette view and dropping it onto an existing Group on the canvas, Studio would place the new icon outside the Group, and, for a large Group, sometimes offscreen. This was fixed.
SB‑21273	If an output arc is part of a loop in an inner module, and lacks an explicit schema declaration, previous StreamBase releases would emit an XmlParsingException error. The same conditions now produce an error message "No schema specified for stream `stream-path`".
SB‑22099	In the Aggregate operator, the expression used for the opening policy is evaluated in a non-aggregate context and thereby must resolve to a simple function. In previous releases, no error or warning was issued if you used an aggregate function in the opening policy expression, and the module resulted in a NullPointerException at runtime. This case now has shows a typecheck error.
SB‑22092	When the Union operator detects a schema mismatch, Studio shows a SchemaMismatchException error. The (go to error) and (compare schemas) links were moved to the beginning of the tooltip message for this error so that they are always available even for very wide schemas.
SB‑22017	Arc bend points on the EventFlow canvas were not correctly restored when reloading a module. This was fixed.
SB‑21805	When you enabled an error port on operators with no output ports, an error dialog would result, even though the error port was created correctly. The appearance of the error dialog was suppressed for these cases.
SB‑21849, SB‑21431	When you opened an EventFlow module by double-clicking its related `.sblayout` file, Studio did not draw the Rearrange Components and Reroute Arcs buttons in the toolbar. This was corrected.
SB‑21501	In previous releases, Notes attached to output streams were not preserved. This was fixed.
SB‑20398	The Copy Schema From dialog was updated to include output streams as a source of schemas to copy.

Fixed in 7.1.8
Number	Resolution
Release 7.1.8 incorporated 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‑22257	If all operator parameters are configured to be emitted at server startup, a null string array parameter could cause the server to not start. This was corrected.
SB‑22213	In previous releases, adding a field to a named schema could in some circumstances change the order of schema definitions in a module or interface such that a schema's dependencies were defined after the schema that required them. The cause was identified and corrected.
SB‑22231	When StreamBase Server starts, it keeps an internal copy of the PATH environment variable, which it uses only to locate processes requested to be run by the External Process operator. In previous releases, on 64-bit Windows, an error prevented `STREAMBASE_HOME/bin64` from appearing in this internal PATH, leaving `STREAMBASE_HOME/bin` as the first entry in the PATH. This was corrected.
SB‑22169, SB‑22173	The parse_time() function was interpreting time zone information in the supplied time string incorrectly. This was fixed.
SB‑22152	Consider a module that defines a named schema, X. A second module imports X, then creates its own named schema Y, that has X as one of its subfields. Now a third module wants to import and use schema Y. In previous releases, the third module would have to import both schemas X and Y so that Y.X was visible. The trail of imported schemas was corrected so that the third module now only needs to import schema Y.
SB‑22135	In previous releases, a Note attached to a Query Table could result in NullPointerException error when running Layout Application (Ctrl+L). This was corrected.
SB‑22130	In the Exegy Input adapter, the cached tuples used to emit level one equities and commodity messages are now properly synchronized.
SB‑22079	If you used Studio's text search feature to look for a string known to be in a Query operator's SQL statement, Studio would instead return the associated JDBC Table data source as containing that string. This was fixed.
SB‑22059	A complex feed simulation with multiple input streams that included lists would sometimes cause a Java NumberFormatException error. The cause was identified and fixed.
SB‑22036	The Exegy adapter was not setting cash position, delta, and halt prices correctly when creating baskets and setting halt prices on them. This was fixed.
SB‑22031	If you used the StreamBaseClient.subscribe(stream, logical_name, predicate) API to subscribe to a stream and specified a logical_name that included a period, the unsubscribe() method would fail to recognize that stream. This was fixed.
SB‑21417	The high availability sample in `sample/ha` was failing to run from its start scripts on Windows. This was corrected.

Fixed in 7.1.7
Number	Resolution
Release 7.1.7 incorporated 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‑22072	In previous releases, long-running, high-volume enqueuing clients could, in some circumstances, exhaust StreamBase Server's input queue buffer capacity, resulting in a disconnected client after the connection timed out. This was corrected.
SB‑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 incorporated 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‑21711	The JMS embedded adapters were updated to emit tuples over the error port system to report failures to connect to or reconnect with a JMS server.
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 incorporated 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 incorporated 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 pop-up 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 incorporated 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, TIBCO 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 incorporated 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 incorporated 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 incorporated 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 Refactor → Move 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.

Limitations Resolved in 7.0.x

Fixed in 7.0.12
Number	Resolution
Release 7.0.12 incorporates all fixes resolved in the release 6.6 series through release 6.6.18. See 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‑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‑21648	The error message from calling `sendOutput()` on the instance of a Java operator used for typechecking was improved.
SB‑21602	An exception that could occur during initial connection using the Deutsche AutobahnFX Trading System adapter was fixed.
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.0.11
Number	Resolution
Release 7.0.11 incorporates all fixes resolved in the release 6.6 series through release 6.6.17. See Limitations Resolved in 6.6.x for details.
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 same application as an embedded server as part of the StreamBase JUnit test framework. This was corrected.
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‑21161	When the Thomson Reuters RMDS Subscribing Input adapter was 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‑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.0.10
Number	Resolution
Release 7.0.10 incorporates all fixes resolved in the release 6.6 series through release 6.6.16. See 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‑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 StreamBase 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‑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‑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‑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 fail typechecking. This was corrected.
SB‑20859	There were certain cases of dragging a module from the Package Explorer view to the canvas to form a Module Reference that working in 6.6.x releases, but not in 7.x releases. The cause was identified and fixed.
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‑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‑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.0.9
Number	Resolution
Release 7.0.9 incorporates all fixes resolved in the release 6.6 series through release 6.6.15. See Limitations Resolved in 6.6.x for details.
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‑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‑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‑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.

Fixed in 7.0.8
Number	Resolution
Release 7.0.8 incorporates all fixes resolved in the release 6.6 series through release 6.6.14. See Limitations Resolved in 6.6.x for details.
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‑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‑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‑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‑20550	In the Thomson Reuters RMDS Subscribing Input adapter, OMMData values with attribute isBlank=true are now discarded.
SB‑20521	As before, TIBCO 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‑20469	Module-scope dynamic variables were not correctly recognized in operator expressions. This was 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.0.7
Number	Resolution
Release 7.0.7 incorporates all fixes resolved in the release 6.6 series through release 6.6.13. See Limitations Resolved in 6.6.x for details.
SB‑20495	Table schemas using named schemas were not being correctly added to applications when implementing an interface. 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‑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‑20325	An earlier fix, SB-19792, uncovered a conflict between Studio and certain adapters, including the TIBCO Subscribe 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‑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‑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‑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.0.6
Number	Resolution
Release 7.0.6 incorporates all fixes resolved in the release 6.6 series through release 6.6.13. See Limitations Resolved in 6.6.x for details.
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‑20136	The StreamBase Admin operator, when running with its asynchronous option enabled, sometimes caused a null pointer exception error. This was fixed.
SB‑20069	Errors in aggregate expressions that attempted to access nested tuple fields were not detected at typecheck time, and instead caused a runtime error in the server. 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‑19970	In previous 7.0.x releases, running the Reroute components and arcs for best layout function had the inadvertent effect of expanding any collapsed Groups. This was fixed to preserve Group status.
SB‑19931	In previous 7.0.x releases, the EBS adapter could fail to start. The cause was identified and corrected.
SB‑19917	In the Application Input and Output views, using the Copy as CSV function from the context menu always included values from the Time column, even when that column was configured to not appear. This was corrected such that Copy as CSV now copies only the visible columns.
SB‑19899	In previous 7.0.x releases, dragging an arc to the edge of the canvas did not automatically scroll the canvas in that direction. This was corrected and the pre-7.x behavior restored.
SB‑19853	Certain erroneous configurations involving a dynamic variable in the Group Options tab of a Query operator would incorrectly pass typechecking, but then cause a runtime error in the server. This was corrected.
SB‑19841	Studio would sometimes show a typechecking error message when in the Properties view when a field's expression definition began with a module parameter in the form `${param}`. Studio was corrected to allow this valid construction without showing an error.
SB‑19772	In previous 7.0.x releases, double-clicking an Input Stream or Output Stream component on the canvas failed to open and bring its Properties view to the foreground. This was corrected.
SB‑19739	When loading EventFlow modules created with an earlier release into Studio 7.x, on occasion, an arc could be rendered with a gap. The cause was found and corrected.
SB‑19653	Errors in custom resolver functions now take into account any function aliases in use when reporting the error.
SB‑19351	In previous 7.0.x releases, the X X keyboard shortcut with no operators selected acted as if all operators were selected. This was corrected to restore the documented behavior, the same as in the 6.6.x release series, that X X without a selection draws an arc on the last two items placed on the canvas.
SB‑19223	In previous 7.0.x releases, copy and paste of an entire EventFlow module failed to copy Groups or Group contents. This was corrected.
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‑19087	In previous releases, when dragging a new Query operator to the canvas, the Group Options tab in its Properties view was immediately available, but any options entered there were not saved once you connected a data construct to the operator. Starting with 7.0.6, a new Query operator's Properties view shows only the General tab until a data construct is connected.
SB‑18851	The High Availability Finite State Machine sample was updated to correct minor errors.
SB‑15779	On the EventFlow canvas, running the Reroute Arcs function on a selected arc inside a Group resulted in the arc being routed around the Group. This was fixed.

Fixed in 7.0.5
Number	Resolution
Release 7.0.5 incorporates all fixes resolved in the release 6.6 series through release 6.6.12, and in the release 6.5 series through release 6.5.13. See Limitations Resolved in 6.6.x for details.
SB‑19702	Typecheck error messages from the Query operator could sometimes appear twice for one error. This was fixed.
SB‑19582	A race condition dealing with adding many containers at the same time with the StreamBase Admin operator was fixed.
SB‑19557	The TIBCO Subscribing Input adapter was emitting a Notice informational log message that reported the adapter's current queue size on receipt of every Tibrv message. This was fixed.
SB‑19461	The `SettlDate` field was added to the data dictionary for the EBS adapter.
SB‑19454	The temporary workspace directory created by the StreamBase Manager utility was getting created in the wrong location. This was corrected.
SB‑19441	In previous 7.0.x releases, the visual debugger in Studio showed placeholders instead of field names for Query Tables. This was fixed.
SB‑19421	In previous 7.0.x releases, collapsing then moving a group on the EventFlow canvas prevented the group from being uncollapsed. This was corrected.
SB‑19398	Error messages from the sbargen command now include file names for each error line.
SB‑19293	The StreamBase `.bin` file installer for Solaris for Intel would sometimes fail to extract files. This was corrected.
SB‑19273	The Reuters RMDS Contribution Output adapter was reading its configuration file in a nonstandard way that prevented applications that included this adapter from being bundled. This was corrected.
SB‑19010	In previous releases on Windows, a space in a path set by the TMP environment variable was not recognized. This was fixed.
SB‑18749	In recent releases, the default value for the Java property `streambase.tmpdir` was used even when a customer specified a different value on the sbd command line. This was corrected, and user-specified values are once again honored.
SB‑13159	In previous releases, clicking the Home button in the standalone Help Viewer opened a generic page on using Eclipse Help. This was corrected to open the home page of StreamBase documentation.

Fixed in 7.0.4
Number	Resolution
Release 7.0.4 incorporates all fixes resolved in the release 6.6 series through release 6.6.11, and in the release 6.5 series through release 6.5.12. See Limitations Resolved in 6.6.x for details.
SB‑19437	Java code that implemented the FXall Trading Provider and Trading Customer adapters was assigning names to schema instances constructed by the adapters, which sometimes caused a typechecking conflict if customer code specified a named schema with the same name. These adapters were updated to not assign names in Schema() constructors.
SB‑19433	In previous releases, setting the Log Level to `-1` or `-2` was honored when using the `streambase.log-level` system property, but not when using the `STREAMBASE_LOG_LEVEL` environment variable. This was corrected.
SB‑19424	An internal redundancy in the Log adapter was corrected. Customers who use the Log adapter configured at DEBUG or TRACE level in performance-sensitive paths should experience a significant performance improvement.
SB‑19288	ERROR messages were enhanced to include the name of the operator in which the error occurred.
SB‑19284	In the 6.6.x release series, if a bundle file included a precompiled archive file (`.sbar` file), and the sbd version running the bundle did not match the sbd version that generated the `.sbar` file, then sbd automatically fell back to compiling the EventFlow and StreamSQL modules contained in the bundle. In releases 7.0.0 through 7.0.3, a version mismatch with a bundle's precompiled files did not automatically fall back to compiling the source files in the bundle, and instead stopped and reported the mismatch. As of release 7.0.4, this was corrected, and the 6.6 behavior was restored.
SB‑18792	In previous releases, in a custom Java operator or adapter, running the `typecheck()` method would sometimes remove the Description attribute for subtuple fields in a schema that included a list of tuples. This was corrected.
SB‑17915	In previous releases, when passing string values through the StreamBase .NET Client API, characters could be lost if the value contained non-Latin or other special characters. This was corrected, and now, if you configure both StreamBase Server and your .NET client environment for Unicode support as described on Unicode Support, there is no character loss when using the .NET API.

Fixed in 7.0.3
Number	Resolution
Release 7.0.3 incorporates all fixes resolved in the release 6.6 series through release 6.6.11, and in the release 6.5 series through release 6.5.12. See Limitations Resolved in 6.6.x for details.
SB‑19301	In previous releases, the RMDS Contribute adapter was responding with an error in response to certain ACK and NAK messages. The cause was determined and corrected.
SB‑19264	A problem was found with schemas in Java Operator tuples that had multiple instances of the same nested named schema. The problem caused incorrect values to be set in the duplicated nested named schema. The problem was corrected.
SB‑19260	The FXall Relationship Trading Provider was inadvertently discarding an order when a quote for the order was withdrawn. This was fixed.
SB‑19247	Since release 7.0.0, the sbargen command has been using excess memory during application compilation, with the result that applications that precompiled easily in release 6.6.x failed to precompile in 7.0.0 through 7.0.2. The cause was found and the problem corrected.
SB‑19181	The `getLeadershipStatus()` function in the StreamBase expression language was not correctly working when used as part of a filtered subscribe predicate in a client application. This was fixed.
SB‑19173	In previous releases, Error Streams were overwriting explicitly set `action` field settings in the error tuple when crossing module boundaries. This was corrected.
SB‑19024	In previous releases, invalid time and date format streams were causing hard-to-decipher error messages on startup of StreamBase Server. Such errors are now better caught at typecheck time, and if not detected during typecheck, a more informative error message is produced.
SB‑18918	In previous releases, some exceptions thrown during application startup were missing some information when the application was loaded by means of the sbadmin addContainer command. This was corrected.

Fixed in 7.0.2
Number	Resolution
Release 7.0.2 incorporates all fixes resolved in the release 6.6 series through release 6.6.11, and in the release 6.5 series through release 6.5.12. See Limitations Resolved in 6.6.x for details.
SB‑19118	In previous 7.0.x releases, using the pinned feature of the Palette view did not survive Studio restarts. This was corrected, and Palette view pinning was restored to the same functionality as in release 6.6, as described in Palette View Drawer Pinning.
SB‑18758	A race condition when using the get or set dynamic variable feature was corrected.

Fixed in 7.0.1

Number Resolution

Release 7.0.1 incorporates all fixes resolved in the release 6.6 series through release 6.6.10, and in the release 6.5 series through release 6.5.11. See Limitations Resolved in 6.6.x for details.

SB‑19013 Some parts of the C++ Client Library were ignoring the STREAMBASE_XMLRPC_TIMEOUT variable, leaving the XML RPC timeout at zero, meaning wait forever. This was corrected.

SB‑18981 Applications in 7.0.0 that used the Query Table replication feature could not be typechecked in Studio, but still typechecked and ran when running from the command line with sbd. This was fixed.

SB‑18901

In a rare configuration where the output port of one Query write operator was shared by two arcs, one leading to a second Query write operator updating the same Query Table, "old" table rows emitted to the third operator (such as the Map operator shown here) could contain incorrect values. The data in the Query Table itself was not corrupted. The condition was not triggered when the first Query operator was followed by any single operator, such as a Split connected to the second Query and third operators. The cause of the problem was identified and corrected.

SB‑18838 Applications that specified JDBC data sources could be bundled, but the bundle would sometimes not run, reporting an error message that the data source was modified since the application was compiled. This was corrected.

SB‑18566 In previous releases, when using the Query operator for Write-Insert or Write-Update operations, if you selected Assign these values to "new" table row for the behavior-on-failure control, the default value provided for tuple fields was tuple(null), which failed to validate. This was fixed, and the default value now provided for all data types is simply null.

SB‑18305 StreamBase bundle files created with the -c option were correctly generating a precompiled archive file, and the .sbar file was included in the bundle. However, when running such a bundle, StreamBase Server would sometimes not use the .sbar file, resulting in slower startup times than expected. This was corrected.

SB‑18807 In-memory Query Tables that use secondary indexes were optimized to reduce their memory overhead. Improvements on the order of 10 to 25% less overhead have been seen in real world applications.

SB‑18726 In previous releases, only selecting without changing a Module Reference that contained a placeholder table would incorrectly flag the EventFlow Editor session as needing to be saved. This was fixed.

SB‑18716 A version issue with the MarketFactory API JAR file included with StreamBase was corrected.

SB‑18713 File chooser dialogs in Studio were failing to show StreamBase interface files imported from other modules. This was fixed.

SB‑18672 In previous releases, the return type of custom Java functions was not checked for validity. This was corrected.

SB‑18669 A race condition was found and corrected that could cause a DLL crash in the Microsoft Excel external adapter when used with Excel 2010.

SB‑18661 In the EBS adapter, a Mina parsing error was corrected.

SB‑18658 The Currenex and EBS output adapters were reporting a null pointer exception when tuples were sent before the adapter's FIX connection was established. Now tuples sent to these output adapters before the connection is established are dropped and reported on the console.

SB‑18481 StreamBase JUnit tests with an external data source configured in the server configuration file could fail with the erroneous error data source is already defined. This was corrected.

SB‑18425 The Load StreamBase Component Exchange dialog could appear to be empty if you scrolled to the bottom of the dialog and then used the search feature. This was fixed.

SB‑18120 The JSONTupleMaker class in the StreamBase unit test API was enhanced to report errors on unexpected or mismatched fields in JSON strings used in test classes.

SB‑17822 In release 7.0.0, memory-based Query Tables could not be safely expanded and viewed when using the Visual Debugger in StreamBase Studio. This was corrected.

SB‑17726 In some cases, an operator parameter specified in the server configuration file was not correctly expanded when referenced with ${param} in a module parameter. This cause was identified and corrected.

SB‑17714 When using the Visual Debugger in StreamBase Studio, Studio now automatically opens the Editor tab of the associated EventFlow Editor for the active module when you click a stack frame line in the Debug view.

Fixed in 7.0.0
Number	Resolution
Release 7.0.0 incorporates all fixes resolved in the release 6.6 series through release 6.6.6, and the release 6.5 series through release 6.5.10. See Limitations Resolved in 6.6.x for details.
SB‑16936, SB‑16975	In previous releases, running Project → Clean on a StreamBase project while EventFlow or StreamSQL Editor sessions are open could leave those editors unable to complete typechecking under some circumstances. The cause was identified and corrected.
SB‑15596	Using Refactor → Rename on a Studio project folder was failing to adjust the project's module search path and resource search path properties. This was corrected.
SB‑14436	Starting with release 7.0.0, output streams that use a declared schema now pass typechecking without a stream connected to their input port. This allows output streams with declared schemas to be used in StreamBase interfaces.
SB‑12993	The Union operator no longer requires the order of sub-fields in tuple fields to match when using the default Loose union setting. However, sub-field order must still match when using the Strict union or Declared schema options, as described in the Known Issues section.

Limitations Resolved in 6.6.x

Fixed in 6.6.25
Number	Resolution
SB‑24353	The DeutscheBank Autobahn FX Adapter sometimes processed custom NDF subscriptions as custom forwards. This was fixed.

Fixed in 6.6.24
Number	Resolution
SB‑23853	For 64-bit platforms, the .NET and C++ clients would sometimes not release Windows handles after a connection was terminated, so subsequent connection attempts would increase the handle counts. This was fixed.
SB‑23851	The Trading Systems Framework sometimes incorrectly returned a NULL date. This was fixed.

Fixed in 6.6.23
Number	Resolution
SB‑23619	When using the Wombat MAMA Input adapter, subscriptions that failed with a NOT_FOUND error were correctly removed from the adapter, but the underlying Wombat subscription was not destroyed. This was fixed.

Fixed in 6.6.22
Number	Resolution
SB‑22783	On rare occasions, client applications authored in C++ and .NET could spontaneously disconnect from StreamBase Server. The cause was isolated and corrected.

Fixed in 6.6.21
Number	Resolution
SB‑22728	A minor issue with Group-By expressions in Query Table Read operations that access fields in the table was found and fixed.
SB‑22708	The wording of a queue updating message was changed to more accurately reflect the condition reported. This message previously reported "`Deadlock detected: queue-path, queue expanding by nn tuples.`" While a deadlock was very remotely possible under those conditions, the message was only meant to convey that the server had to expand this queue because the consumer side of the queue was consuming slower than the producer side was producing. The new wording for this message is: `WARN: FQ classname - Queue queue-path expanding by nnn tuples because the consumer is slower than the producer. Waited ttt milliseconds.`
SB‑22627	The Wombat Publishing adapter was inadvertently truncating integers to shorts in populating I32 message fields. This was corrected.

Fixed in 6.6.20
Number	Resolution
Release 6.6.20 incorporates all fixes resolved through 6.6.19.

Fixed in 6.6.19
Number	Resolution
Release 6.6.19 incorporates all fixes resolved in the release 6.5 series through release 6.5.13.
SB‑22259	The Wombat MAMA Publishing Output adapter was updated to clarify WARN log messages from the adapter that occur when the feed dictionary changes, but the application still expects a field with a type defined in the previous dictionary.
SB‑22231	When StreamBase Server starts, it keeps an internal copy of the PATH environment variable, which it uses only to locate processes requested to be run by the External Process operator. In previous releases, on 64-bit Windows, an error prevented `STREAMBASE_HOME/bin64` from appearing in this internal PATH, leaving `STREAMBASE_HOME/bin` as the first entry in the PATH. This was corrected.
SB‑21848	In previous releases, multiple Update operations from Query operators in separate threads to an in-memory Query Table showed non-atomic behavior, whereas the same case for an on-disk Query Table did not. The cause was identified and corrected.
SB‑21417	The high availability sample in `sample/ha` was failing to run from its start scripts on Windows. This was corrected.

Fixed in 6.6.18
Number	Resolution
Release 6.6.18 incorporates all fixes resolved in the release 6.5 series through release 6.5.13.
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 6.6.17
Number	Resolution
Release 6.6.17 incorporates all fixes resolved in the release 6.5 series through release 6.5.13.
SB‑21438	In previous releases, a port specified in a server configuration file on which to run StreamBase Server was honored for standard uses but ignored when running same application as an embedded server as part of the StreamBase JUnit test framework. This was corrected.
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‑20273	In previous releases, certain StreamBase-provided and customer-written input adapters that emit tuples at high rates could incur timeouts when being shut down or suspended. This was corrected.
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 6.6.16
Number	Resolution
Release 6.6.16 incorporates all fixes resolved in the release 6.5 series through release 6.5.13.
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‑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‑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 6.6.15
Number	Resolution
Release 6.6.15 incorporates all fixes resolved in the release 6.5 series through release 6.5.13.
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‑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‑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‑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‑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‑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‑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‑20521	As before, TIBCO does not recommend overriding the `Operator.getName()` method. However, StreamBase internals are now protected from the consequences if your application requires doing so.
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.

Fixed in 6.6.14
Number	Resolution
Release 6.6.14 incorporates all fixes resolved in the release 6.5 series through release 6.5.13.
SB‑20550	In the Thomson Reuters RMDS Subscribing Input adapter, OMMData values with attribute isBlank=true are now discarded.
SB‑20499	The Wombat MAMA adapters were updated to allow configuration of their properties before the required third-party Wombat JAR file has been installed. This corrects the NoClassDefFoundError messages seen when starting Studio for Linux at the command prompt.
SB‑20469	Module-scope dynamic variables were not correctly recognized in operator expressions. This 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‑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‑20325	An earlier fix, SB-19792, uncovered a conflict between Studio and certain adapters, including the TIBCO Subscribe adapter, that were using older classloaders. The cause was identified and fixed.
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 supersede 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‑19883	Modules that implement an interface underwent unnecessary typechecking whenever any other module or interface file was saved. This was fixed.

Fixed in 6.6.13
Number	Resolution
Release 6.6.13 incorporates all fixes resolved in the release 6.5 series through release 6.5.13.
SB‑20220	The Thomson Reuters RMDS Subscribing Input adapter was updated to download its data dictionary only once per connection when using the RMDS 6 message model.
SB‑20216, SB‑18913	In interactive monitoring of a running application with StreamBase Manager or the sbmonitor command, queue size information was not being updated correctly, with the result that some queues that appeared to be empty were not. In addition, the batch processing time and batch latency values were sometimes reported as negative numbers. These issues were corrected.
SB‑20214	Using the HotspotFX adapter with a `getAllTrades` request resulted in an error message. The cause was identified and corrected.
SB‑20073, SB‑19776	When the Thomson Reuters RMDS adapter was used in a certain sequence of events (subscribe, duplicate subscribe, unsubscribe, subscribe), the duplicate subscribe would silently override the unsubscribe, resulting in two subscriptions. 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‑20041	The CSV File Writer Input adapter was emitting an incorrect filename for a Closed event. This was fixed.
SB‑20039	The CSV File Writer Input adapter was updated so that its File Name property is optional if the Start Control Port property is enabled. The adapter emits a warning if a write tuple is enqueued before an output file has been opened, which can happen if no File Name is specified and a start control tuple with a file name has not yet been enqueued.
SB-19959	The Thomson Reuters RMDS Contribution Output adapter was inadvertently dividing by 10,000 when publishing or contributing a Reuters Real32 field using a StreamBase int field. This was fixed.
SB-19928	The Currenex adapter had issues dealing with non-ASCII characters in schema definitions used in Java operators. This was resolved.
SB‑19792	A PermGen memory leak in Studio was resolved. This leak would affect users whose workspaces contained projects with large numbers of libraries on the Java Build Path. The leak would manifest with Studio eventually displaying an OutOfMemoryError referring to PermGen space.
SB‑19707	The Wombat MAMA Input adapter would occasionally fail to send an Init tuple when subscribing to a symbol. This was fixed.
SB‑19702	Typecheck error messages from the Query operator could sometimes appear twice for one error. This was fixed.
SB‑19673	The CSV File Writer Input adapter no longer shuts down if the configured file cannot be opened during startup and a Start Control Port is enabled.
SB‑18791	In previous releases, in a Schema tab of the Properties view for an operator, if the schema was defined by a named schema or table schema, the entire grid was disabled including its scroll bars, which prevented read-only inspection of the full grid. Starting with this release, under the same circumstances, the scroll bars for schema grids remain enabled, which allows you to browse the read-only fields.
SB‑18790	In previous releases, when using the EventFlow Debugger, breakpoints in modules that had multiplicity enabled were never hit. This was corrected.
SB‑16223	In previous releases, a custom Java function that returns a list would cause a null pointer exception if the function returned a list(null). This was fixed, and a list(null) is now correctly returned.
SB‑13159	In previous releases, clicking the Home button in the standalone Help Viewer opened a generic page on using Eclipse Help. This was corrected to open the home page of StreamBase documentation.

Fixed in 6.6.12
Number	Resolution
Release 6.6.12 incorporates all fixes resolved in the release 6.5 series through release 6.5.12.
SB‑19557	The TIBCO Subscribing Input adapter was emitting a Notice informational log message that reported the adapter's current queue size on receipt of every Tibrv message. This was fixed.
SB‑19560	A race condition in memory Query Table pooling was found and fixed. This issue could only be triggered when updating a memory Query Table from two or more different parallel regions simultaneously.
SB‑19461	The SettlDate field was added to the data dictionary for the EBS adapter.
SB‑19437	Java code that implemented the FXall Trading Provider and Trading Customer adapters was assigning names to schema instances constructed by the adapters, which sometimes caused a typechecking conflict if customer code specified a named schema with the same name. These adapters were updated to not assign names in Schema() constructors.
SB‑19433	In previous releases, setting the Log Level to `-1` or `-2` was honored when using the `streambase.log-level` system property, but not when using the `STREAMBASE_LOG_LEVEL` environment variable. This was corrected.
SB‑19424	An internal redundancy in the Log adapter was corrected. Customers who use the Log adapter configured at DEBUG or TRACE level in performance-sensitive paths should experience a significant performance improvement.
SB‑19398	Error messages from the sbargen command now include file names for each error line.
SB‑19301	In previous releases, the RMDS Contribute adapter was responding with an error in response to certain ACK and NAK messages. The cause was determined and corrected.
SB‑19293	The StreamBase `.bin` file installer for Solaris for Intel would sometimes fail to extract files. This was corrected.
SB‑19288	ERROR messages were enhanced to include the name of the operator in which the error occurred.
SB‑19273	The Reuters RMDS Contribution Output adapter was reading its configuration file in a nonstandard way that prevented applications that included this adapter from being bundled. This was corrected.
SB‑19260	The FXall Relationship Trading Provider was inadvertently discarding an order when a quote for the order was withdrawn. This was fixed.
SB‑19181	The `getLeadershipStatus()` function in the StreamBase expression language was not correctly working when used as part of a filtered subscribe predicate in a client application. This was fixed.
SB‑19024	In previous releases, invalid time and date format streams were causing hard-to-decipher error messages on startup of StreamBase Server. Such errors are now better caught at typecheck time, and if not detected during typecheck, a more informative error message is produced.
SB‑19010	In previous releases on Windows, a space in a path set by the TMP environment variable was not recognized. This was fixed.
SB‑18918	In previous releases, some exceptions thrown during application startup were missing some information when the application was loaded by means of the sbadmin addContainer command. This was corrected.
SB‑18792	In previous releases, in a custom Java operator or adapter, running the `typecheck()` method would sometimes remove the Description attribute for subtuple fields in a schema that included a list of tuples. This was corrected.
SB‑18749	In recent releases, the default value for the Java property `streambase.tmpdir` was used even when a customer specified a different value on the sbd command line. This was corrected, and user-specified values are once again honored.

Fixed in 6.6.11
Number	Resolution
Release 6.6.11 incorporates all fixes resolved in the release 6.5 series through release 6.5.12.
SB‑19110	Expressions that combined a StreamBase constant with an asterisk to indicate all fields were incorrectly failing to typecheck. This was fixed.
SB‑19137	The 29West LBM Publishing output adapter was throwing a NullPointerException when run with `streambase.operator.parameters.log-level` set to 3. This was corrected.
SB‑19028	In previous releases, there were cases where Studio would show a typecheck error due only to field ordering differences between two schemas, but the same module would run as expected in StreamBase Server. Studio typechecking was corrected.
SB‑19022	In previous releases, when using a valid, defined parameter in ${PARAMETER} format in the Join operator's Tuple-based Settings tab, Studio failed to substitute parameter values, resulting in a typecheck error. This was fixed.
SB‑19013	Some parts of the C++ Client Library were ignoring the `STREAMBASE_XMLRPC_TIMEOUT` variable, leaving the XML RPC timeout at zero, meaning wait forever. This was corrected.
SB‑18929	The FIX data dictionary used by the Currenex adapter was corrected to use data type int for field tag 460 with name "Product".
SB‑18980	Modules with complex module importation patterns were generating spurious typecheck errors. For example, let's say file `A.sbint` defines named schema A; file `B.sbint` defines schema B which has a tuple field of type A (imported from `A.sbint`); then file `C.sbapp` imports from `B.sbint`. In previous releases, module `C.sbapp` would show a typecheck error, complaining that schema A could not be found. This was corrected.
SB‑18960	The Studio Visual Debugger would sometimes miss breakpoints in complex applications that use extension points, especially those set before a Once adapter or other functionality that occurred early. The debugger was corrected for those cases.
SB‑18905	A memory leak in list handling in the C++ and .NET versions of the StreamBaseClient API was fixed.
SB‑18864	When using the Extract as Module command from the context menu in Studio, layout information was being written to the `.sbapp` file, even when the preference was set to use `.sblayout` files. This was corrected.
SB‑18838	Applications that specified JDBC data sources could be bundled, but the bundle would sometimes not run, reporting an error message that the data source was modified since the application was compiled. This was corrected.
SB‑18809	The Reuters RMDS Publishing adapter was issuing a confusing error message that reported "no subscribers" after responding to an incoming subscribe request for a RIC. The expected usage is for the StreamBase application to always issue a REFRESH action in response to a subscribe request before issuing any updates. Accordingly, the adapter was updated to distinguish the true no-subscriber case from the case immediately after receiving a subscribe request. The WARN message for the latter case now reads "There are 0 pending snapshots and 1 pending subscriptions but no active subscriptions for item `RICname`. Consider publishing a REFRESH instead."

Fixed in 6.6.10

Number Resolution

Release 6.6.10 incorporates all fixes resolved in the release 6.5 series through release 6.5.11.

SB‑18901

SB‑18566 In previous releases, when using the Query operator for Write-Insert or Write-Update operations, if you selected Output these values instead for the behavior-on-failure control, the default value provided for tuple fields was tuple(null), which failed to validate. This was corrected, and the default value now provided for all data types is simply null.

Fixed in 6.6.9
Number	Resolution
Release 6.6.9 incorporates all fixes resolved in the release 6.5 series through release 6.5.11.
SB‑18869	Message throughput of the 29West LBM Publishing adapter was not at the expected level compared to a similar Java client. This was corrected.
SB‑18868	The 29West LBM adapters were failing to locate their configuration files on the resource search path, leading to a conflict between Studio typechecking and runtime typechecking. This was corrected.
SB‑18867	The 29West LBM Subscribing input adapter could fail to subscribe to a topic. This was fixed.
SB‑18847	The 29West LBM Publishing Output adapter was emitting the error `topic already associated with a source` because idle topics were inadvertently discarded after a short period of inactivity. The cause was identified and fixed.
SB‑18846	Shutting down a container that includes a FIX adapter before it has completely initialized no longer throws an exception.
SB‑18845	A custom aggregate function called by a defined alias was failing when reused with a different schema. The cause was identified and corrected.
SB‑18731	When running a feed simulation, using the rate slider control in the Feed Simulations view could sometimes cause the simulation to stop sending data and enter an infinite loop. This was fixed.
SB‑16212	Typechecking tests were added to the Field Serializer Operator so that it now reports when the Edit Schema tab in the Properties view is null or empty.

Fixed in 6.6.8
Number	Resolution
Release 6.6.8 incorporates all fixes resolved in the release 6.5 series through release 6.5.10.
SB‑18807	In-memory Query Tables that use secondary indexes were optimized to reduce their memory overhead. Improvements on the order of 10 to 25% less overhead have been seen in real world applications.
SB‑18305	StreamBase bundle files created with the `-c` option were correctly generating a precompiled archive file, and the `.sbar` file was included in the bundle. However, when running such a bundle, StreamBase Server would sometimes not use the `.sbar` file, resulting in slower startup times than expected. This was corrected.
SB‑18726	In previous releases, only selecting without changing a Module Reference that contained a placeholder table would incorrectly flag the EventFlow Editor session as needing to be saved. This was fixed.
SB‑18716	A version issue with the MarketFactory API JAR file included with StreamBase was corrected.
SB‑18713	File chooser dialogs in Studio were failing to show StreamBase interface files imported from other modules. This was fixed.
SB‑18672	In previous releases, the return type of custom Java functions was not checked for validity. This was corrected.
SB‑18669	A race condition was found and corrected that could cause a DLL crash in the Microsoft Excel external adapter when used with Excel 2010.
SB‑18661	In the EBS adapter, a Mina parsing error was corrected.
SB‑18658	The Currenex and EBS output adapters were reporting a null pointer exception when tuples were sent before the adapter's FIX connection was established. Now tuples sent to these output adapters before the connection is established are dropped and reported on the console.
SB‑18582	In previous releases, if you began a Property view edit, then switched to a non-EventFlow Editor session, then back, your edits were not preserved. This was corrected.
SB‑18481	StreamBase JUnit tests with an external data source configured in the server configuration file could fail with the erroneous error `data source is already defined`. This was corrected.
SB‑18425	The Load StreamBase Component Exchange dialog could appear to be empty if you scrolled to the bottom of the dialog and then used the search feature. This was fixed.
SB‑17726	In some cases, an operator parameter specified in the server configuration file was not correctly expanded when referenced with `${param}` in a module parameter. This cause was identified and corrected.

Fixed in 6.6.7
Number	Resolution
Release 6.6.7 incorporates all fixes resolved in the release 6.5 series through release 6.5.10.
SB‑18627	The EBS adapter was updated to not require the Username, Password, or NewPassword properties in its configuration file when the adapter runs as an acceptor.
SB‑18593	The FIX adapter, and adapters based on it, including the EBS adapter, could fail to read FIX 5.0 data dictionary files when running with the QuickFIX/J FIX engine. This was corrected.
SB‑18529	The Reuters RMDS Publishing Output adapter was publishing ASCII and UTF-8 strings incorrectly, and in a way that could not be consumed by Microsoft Excel clients. This was fixed.
SB‑18526	The Reuters D3000 adapter honored the resource search path during typechecking, but failed to honor it at runtime. This caused the adapter to fail to locate its instrument price format file if placed in a different directory that the StreamBase application file. This was corrected.
SB‑18461	The CSV File Writer adapter was failing to recover from a disk full event, and did not continue writing output when disk space was cleared. This was fixed.

Fixed in 6.6.6
Number	Resolution
Release 6.6.6 incorporates all fixes resolved in the release 6.5 series through release 6.5.10.
SB‑18337	An issue involving Query read operations that used complex group-by expressions was identified and fixed.
SB‑18259	In previous releases, Studio was incorrectly flagging as a duplicate action error certain expressions that used an asterisk in both Field Name and Expressions columns. This was corrected.
SB‑18165	When using multiple TIBCO Rendezvous embedded input adapters in the same StreamBase application, a race condition could result in spurious warnings and null pointer exceptions when under heavy message loads. This was fixed.
SB‑18160	The TIBCO Rendezvous embedded input adapter now allows a specific field ID to be present at multiple levels in a Tibrv message.
SB‑18045	In previous releases, if the IBM WebSphere MQ output adapter was configured to not generate XML from tuple fields, and the adapter's input schema contained both a payload (string) field and a metadata (tuple) field, then the adapter could generate an erroneous typecheck error: "Error(s) in schema of input port (1): Exactly one field (of type string) must be present when not generating XML from tuple fields". This was corrected.
SB‑17968	In previous releases, if a Query-Read operator used an imported table schema and specified match input with null values if now rows were found, the Query operator would fail typechecking after modifying the table schema; but the typechecking state was cleared just by selecting the Query operator and re-saving the module. This cause for this condition was identified and corrected.
SB‑17869	In previous releases, StreamBase JUnit tests did not set the library path for the StreamBase Server that the test invoked to run the test, which prevented any module that used disk-based Query Tables to fail to run. As of release 6.6.6, JUnit tests set the library path to `STREAMBASE_HOME/lib` or `/lib64`, as appropriate for the server version you are testing with.
SB‑17821	In previous Studio releases, for EventFlow applications with very long description text for any component, running View Source from the context menu of the canvas would create a non-resizable window the full width of the monitor. This was fixed, and the source view window is now always resizable.
SB‑17799	Threading and performance issues in the CSV Socket Writer adapter were identified and corrected.
SB‑17551	StreamBase Admin operators that specified the correct URI syntax were still not correctly connecting to remote servers. This was fixed.
SB‑17294	In StreamBase Manager, the field that reports the CPU usage of a process was not correctly showing large percentage numbers. This was corrected.

Fixed in 6.6.5
Number	Resolution
Release 6.6.5 incorporates all fixes resolved in the release 6.5 series through release 6.5.9.
SB‑17662	A rare deadlock situation involving parallel access to memory-based Query Tables was fixed.
SB‑17661	The ActivFeed Input adapter was updated to use the originating exchange's time zone when processing timestamp fields, as specified by Activ.
SB‑17649	In previous releases on Linux, the `stop` subcommand of the `/etc/init.d/streambase` script failed to stop a running instance of StreamBase Server. This was corrected.
SB‑17633	The Reuters RMDS Publishing Output adapter was not setting an expected flag to indicate completion in non-hierarchical refresh messages. This was corrected.
SB‑17619	Running sbd –b at the StreamBase Command Prompt was producing a crash report. The cause was identified and corrected.
SB‑17600	The Reuters RMDS Publishing Output adapter could lose track of subscriptions to a RIC when two clients subscribed and the second client unsubscribed. This was fixed.
SB‑17573	The Extension Point operator was failing to enforce unique reference names for modules. This was corrected.
SB‑17550	Some StreamBase adapters, including the FIX adapter and adapters that inherit from it, allow you to set a logging level independently of the hosting StreamBase Server's logging level. In previous releases, this feature worked for the Logback logging mechanism that is used by Studio and when sbd is run interactively. However, the adapter log levels did not work with the log4j logging mechanism that is used when running sbd –b or when running StreamBase Server as a Windows service. As of releases 6.5.9 and 6.6.5, adapter log level settings are honored in all contexts.
SB‑17545	When the Copy Schema From dialog prompted to save the application, and you did save, the Copy Schema dialog failed to reappear. This was corrected.
SB‑17499	A schema-bearing operator followed by a downstream operator with a declared schema was causing an EvalPluginException if the declared schema specified a different field order. This was fixed.
SB‑17443	The StreamBase Server configuration file validator failed to support custom functions that took a list of tuples as an argument. This was fixed.

Fixed in 6.6.4
Number	Resolution
Release 6.6.4 incorporates all fixes resolved in the release 6.5 series through release 6.5.8.
SB‑17427	A rounding error was affecting the feed simulator when using a CSV data file as input and the Timestamp from column feature, with the result that timestamps with millisecond components were batched into one second groups. This was corrected.
SB‑17425	Calling `Schema.getName()` in the `typecheck()` method for a Java operator or adapter once again returns any schema name set in the properties for that operator or adapter. This capability was present in early 6.5.x releases, was inadvertently removed, and is now restored in releases 6.5.9 and 6.6.4.
SB‑17497	In the StreamBase .NET API, running `Tuple.SetList()` for a list of longs was throwing an exception. This was fixed.
SB‑17417	The Studio typecheck cache was not correctly flushed when an imported table schema was modified with a new field. This was corrected.
SB‑17392	The installer for 64-bit Windows now creates the placeholder registry key `sbd64.n.m` for the authentication keys that can be configured for the 64-bit version of StreamBase Server, as described on StreamBase Registry Keys on Windows.
SB‑17366	Typecheck errors could be seen in a newly created EventFlow application that was created with File → New with the Implement interfaces option selected and the selected interface used schemas that imported schema definitions. This was corrected.
SB‑17335	The combination of a Java operator with a schema and an immediately downstream operator with an explicitly declared schema could fail with an internal error if the explicit schema defined fields in a different order. The internal error condition was eliminated.
SB‑16827	The Edit Table Schema dialog was failing to draw scrollbars for very large schemas, which prevented the Add, Edit, and Remove buttons from showing. This was fixed.

Fixed in 6.6.3
Number	Resolution
Release 6.6.3 incorporates all fixes resolved in the release 6.5 series through release 6.5.8.
SB‑16999	If the text of a Note component on the EventFlow canvas contained a string such as `${text}` that could be interpreted as a reference to a variable or parameter, the containing module gave a typecheck error. This was corrected by URL encoding such strings in the EventFlow XML.
SB‑17267, SB‑17237	In previous releases, there were issues with table references, where a Query Table in module A referenced a placeholder table in a Module Reference to module B, and module B in turn imported table schemas from module C. Symptoms included an inability to access the Query Table in module A, and the secondary index failing to appear as an index option for Query Read operations. The cause of these issues was identified and corrected.
SB‑17158	In the QuickFIX/J library used by the FIX adapter, the FIX message field `OrigSendingTime`, optionally included in the adapter output schema, now checks the QuickFIX/J configuration setting `MillisecondsinTimeStamp`, also used by the `SendingTime` field, to determine whether to include milliseconds. This setting is set to `Y` by default.

Fixed in 6.6.2
Number	Resolution
Release 6.6.2 incorporates all fixes resolved in the release 6.5 series through release 6.5.7.
SB‑17170	In release 6.6.1 only, an inadvertent error prevented using the mouse to connect the second and subsequent arcs from an operator or module reference with two or more output ports to the next downstream component. In 6.6.1, keyboard shortcuts and context menu actions were unaffected and still worked normally to make the same arc connections. The mouse arc connection issue was fixed in release 6.6.2.
SB‑17124	When using the Alpha Trading Systems EMAPI Order Entry adapter, the Passive Only field was inadvertently set to null for update messages. This was corrected.
SB‑17189	A cache used in conjunction with Query Tables was causing excessive object creation during Query Table writes, which in turned caused excessive garbage collection activity. This was fixed.
SB‑17185	StreamBase Server collects statistics as it runs and emits those as tuples from the `system` container's `stat` stream. The collection of statistics for the stat stream was optimized to improve caching and to prevent allocating excessive objects. The default size of the stat stream's tuple cache was changed to dynamically grow as needed by the application. You can control the stat stream's cache size by means of the system property `streambase.max-stat-tuples-cache`. The default value is –1.
SB‑17165	An error with Query Table replication was fixed for cases of two tables with the same name but different schemas in the same application.

Fixed in 6.6.1
Number	Resolution
Release 6.6.1 incorporates all fixes resolved in the release 6.5 series through release 6.5.6.
SB‑17080	In release 6.6.0, there were cases where the Properties view for a Module Reference could lose its connection to the underlying EventFlow Editor, which forced re-entering property settings. In release 6.6.1, the cause was identified and corrected.
SB‑17066	StreamBase client applications written with the C++ Client Library could enter a loop that consumed 100% of CPU resources, if the client application called `dequeue()` with a 0 timeout, and no tuples were enqueued to any stream that client subscribed to. The cause was identified and corrected.
SB‑16968	The StreamBase IBM WebSphere MQ Adapter was not emitting an Event Port tuple when it was unable to process a message. This was fixed.
SB‑16950	The Interface tab of the Interface Editor could draw with its buttons inaccessible under the right window edge if an interface or component had a very long description. Starting with 6.6.1, a horizontal scroll bar appears in these cases.
SB‑16898, SB‑17031	The Extension Point operator, introduced in release 6.6.0, was not initially compatible with the Trace Debugger. This was corrected, and you can now step through tuple traces for applications that include both Extension Points and Module References.
SB‑16766, SB‑16767	In previous releases, if you renamed a table schema, locally defined tables that used that table schema failed to be updated. Similarly, if you renamed a named schema used by a table schema, locally defined table schemas were not updated. These issues were fixed.

Fixed in 6.6.0
Number	Resolution
Release 6.6.0 incorporates all fixes resolved in the release 6.5 series through release 6.5.5.
SB‑16777	In previous releases, StreamBase erroneously provided schema, schema field descriptions, and schema names at runtime. These properties are only maintained during application development and have no meaning during application runtime.
SB‑16706	The performance of paste operations in an EventFlow application when the clipboard contains many items was dramatically improved.
SB‑16004	In previous releases, typechecking in StreamBase Studio sometimes failed to ignore references to file resources in the file system outside of the Studio workspace. This applied both to EventFlow module files and resource files (such as CSV input files) on the module search path. As of release 6.6.0, Studio strictly requires referenced files to be in the Studio workspace.
SB‑11376	Previously, when intermediate stream dequeuing was enabled, it was also possible to enqueue into intermediate input streams. This was corrected so that non-public inner module streams remain private, even with ISD enabled.

StreamBase Release Note Archives

Limitations Resolved in 7.4.x

Important

Limitations Resolved in 7.3.x

Limitations Resolved in 7.2.x

Limitations Resolved in 7.1.x

Limitations Resolved in 7.0.x

Limitations Resolved in 6.6.x