Release Notes
Software Release 4.2.0 July 2015Important Information
SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.
USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE
SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.
This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written
authorization of TIBCO Software Inc.
TIBCO, Two-Second Advantage, TIB, Information Bus, eFTL and Rendezvous are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries. Enterprise Java Beans (EJB), Java Platform Enterprise Edition (Java EE), Java 2 Platform Enterprise Edition (J2EE), and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle Corporation in the U.S. and other countries.
All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only.
THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM.
THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.
THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE,
INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES. Copyright © 2010–2015 TIBCO Software Inc. ALL RIGHTS RESERVED.
Contents
TIBCO Documentation and Support Services. . . .4
New Features. . . .6
Changes in Functionality. . . . 8
Deprecated and Removed Features. . . .9
Migration and Compatibility. . . .10
Closed Issues. . . .11
Known Issues. . . .14
TIBCO Documentation and Support Services
Documentation for this and other TIBCO products is available on the TIBCO Documentation site:
https://docs.tibco.com
Documentation on the TIBCO Documentation site is updated more frequently than any documentation that might be included with the product. To ensure that you are accessing the latest available help topics, please visit us at https://docs.tibco.com.
Product-Specific Documentation
Documentation for TIBCO products is not bundled with the software. Instead, it is available on the TIBCO Documentation site. To access the documentation web page for this product from a local software installation, open the following file:
TIBCO_HOME/release_notes/TIB_ftl_4.2.0_docinfo.html
TIBCO_HOME is the top-level directory in which TIBCO products are installed.
● On Windows platforms, the default TIBCO_HOME is C:\tibco. ● On UNIX platforms, the default TIBCO_HOME is /opt/tibco.
The following documents for this product can be found on the TIBCO Documentation site.
TIBCO FTL®
Documentation Set
● TIBCO FTL Concepts Everyone reads this booklet first, for an intuitive introduction to the
fundamental concepts of FTL software.
● TIBCO FTL Development Application developers and architects read this manual to understand
concepts relevant in any supported programming language.
● TIBCO FTL API Reference Application developers use this HTML documentation to learn the details
of the FTL API in specific programming languages.
● TIBCO FTL Administration Administrators read this manual to learn how to use the realm server
and its interfaces, and how to define a realm. Developers can also benefit from understanding FTL software from an administrator’s perspective.
● TIBCO FTL Installation Read this manual before installing or uninstalling the product.
● TIBCO FTL Glossary The glossary contains brief definitions of key terms used in all other parts of
the documentation set.
● TIBCO FTL Release Notes Read the release notes for a list of new and changed features. This
document also contains lists of known issues and closed issues for this release.
TIBCO eFTL™ Documentation Set
TIBCO eFTL software is documented separately. Administrators use the FTL realm server GUI to configure and monitor the eFTL service. For information about these GUI pages, see the documentation set for TIBCO eFTL software.
How to Contact TIBCO Support
For comments or problems with this manual or the software it addresses, contact TIBCO Support:
● For an overview of TIBCO Support, and information about getting started with TIBCO Support,
visit this site:
● If you already have a valid maintenance or support contract, visit this site: https://support.tibco.com
Entry to this site requires a user name and password. If you do not have a user name, you can request one.
How to Join TIBCOmmunity
TIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts. It is a place to share and access the collective experience of the TIBCO community. TIBCOmmunity offers forums, blogs, and access to a variety of resources. To register, go to:
https://www.tibcommunity.com
New Features
The following new features have been added to Release 4.2.0 of TIBCO FTL software.
TLS Security
● Realm servers can now use TLS cryptography protocols to secure its communications with clients,
with other realm servers, and with GUI browsers.
● TCP-based transports can now use TLS to secure client-to-client communications. ● A new realm server command line parameter can specify the JCE provider. Group API Enhancements
● A new group status advisory presents information about the group and its members.
● When joining a group, each member can supply a unique member descriptor to identify itself to
other members.
● A program can join a group as an observer. Observers do not participate in the functional roles of
the group, but can monitor group status advisories.
Durable Types
Previous releases distinguished only two types of durables: non-shared and shared. Release 4.2.0 introduces last-value durables and key/value maps. Along with this enhancement, non-shared durables are now called standard durables, although their functionality has not changed.
Key/Value Map API
Client programs can use a persistence store as a key/value map, which emulates a simple database table, storing one value for each key. Programs can iterate over all key/value pairs in the map. Programs can use locks for exclusive access to a map.
Dynamic Durables
Client programs can now create durables dynamically using the create subscriber call. Administrators must define a template to enable this functionality.
Direct Publishers and Subscribers
A new C API yields faster performance and lower latency by communicating directly through shared memory. Direct publishers and subscribers are appropriate only in very specialized use cases in which a few nanoseconds of latency can make a critical difference.
A new transport type, direct shared memory, supports this API.
Multicast Retransmission Advisories
A new advisory provides visibility into the retransmission behavior of multicast transports.
Multicast Statistics
New statistics provide visibility into the retransmission behavior of multicast transports.
IPv6
The realm server supports IPv6, as do TCP transports and RUDP transports.
Maximum Payload for Built-In Opaque Formats
Previous releases limited the payload size of messages with built-in format opaque or keyed opaque. Release 4.2.0 eases this restriction: message payload can exceed the constant
BUILTIN_MSG_FMT_OPAQUE_MAXSIZE. This constant now represents a performance threshold: a message with payload larger than this constant is less efficient than a message with smaller payload.
When defining a multicast transport, administrators can specify a range of open ports to use. This feature simplifies cooperation with firewalls.
Multicast MTU Size
When defining a multicast transport, administrators can specify a larger MTU size.
API Enhancements
● Access opaque fields in .NET without copying data.
● Set array fields in .NET and Java by copying only part of a source array. ● Event queue get count.
● Event queue destroy call in C now accepts a closure argument. Persistence Server Logging
Persistence servers support logging to a rotating set of log files.
Changes in Functionality
The following are changes in functionality in Release 4.2.0 of TIBCO FTL software.
Maximum Payload for Built-In Opaque Formats
Previous releases limited the payload size of messages with built-in format opaque or keyed opaque. Release 4.2.0 eases this restriction: message payload can exceed the constant
BUILTIN_MSG_FMT_OPAQUE_MAXSIZE. This constant now represents a performance threshold: a message with payload larger than this constant is less efficient than a message with smaller payload.
Durable Types
Deprecated and Removed Features
The following tables list any features that have been deprecated or removed as of Release 4.2.0 of TIBCO FTL software.
For deprecated features, if relevant, useful alternatives to the deprecated features are listed. Any use of a deprecated feature should be discontinued as it may be removed in a future release. You should avoid becoming dependent on deprecated features and become familiar with the suggested alternative features.
Platforms
Affected Platform Description
Affected Release
Novell SUSE Linux Enterprise Server 11.0 64-bit, x86-64 Migrate to 11.3. 4.2.0 Deprecated Features Affected Component Description Deprecated Release
Adapter The adapter converts and forwards messages between TIBCO FTL and TIBCO Rendezvous. This component is deprecated, and will be removed in a future release. This functionality will become part of the TIBCO Rendezvous product family.
4.2.0 Removed Features Affected Component Description Deprecated Release Removed Release
API API calls that facilitated request/reply interactions between TIBCO FTL and TIBCO eFTL are obsolete.
4.2.0 4.2.0
Migration and Compatibility
The table lists compatibility issues among releases of TIBCO FTL software. Instructions on how to migrate from a previous release to version 4.2.0 of TIBCO FTL software are included in the product documentation set.
See “Upgrade Migration to a New Release” in TIBCO FTL Administration.
Incompatibility with Earlier Releases
Key Summary
FTL-5119 Persistence Server Incompatibility: Release 4.0 to 4.1
Persistence servers from Release 4.0 and earlier are incompatible with persistence servers from Release 4.1.
Persistence servers from opposite sides of this gap cannot establish a quorum. A persistence server and a realm server from opposite sides of this gap cannot operate together.
Rolling upgrade of persistence servers is not supported across this gap. Instead, upgrade requires complete shutdown of the persistence store feature.
This incompatibility is fixed in release 4.2. That is, persistence servers from Release 4.0 and earlier are compatible with persistence servers from Release 4.2.
FTL-5111 Persistence Incompatibility: Release 3.1 to 4.0 and 4.1
Client durable subscribers from Release 3.1 and earlier cannot connect to persistence servers from Release 4.0 and 4.1.
This incompatibility is fixed in release 4.2. That is, client durable subscribers from Release 3.1 and earlier can connect to persistence servers from Release 4.2.
Incompatibility with Releases of Other TIBCO Products
Closed Issues
The table lists closed issues in version 4.2.0 of TIBCO FTL software.
Key Summary
FTL-5121 Fixed tibstore memory leaks that could occur after a subscriber on a shared durable reconnected to the persistence server.
FTL-5111 Fixed a tibstore defect in which client durable subscribers from Release 3.1 and earlier could not connect to persistence servers from Release 4.0 and 4.1.
This incompatibility is fixed in release 4.2. That is, client durable subscribers from Release 3.1 and earlier can connect to persistence servers from Release 4.2.
FTL-5104 Fixed a defect in which the client library could call a subscriber completion callback more than once after removing a subscriber from an event queue.
FTL-5091 Fixed a defect in which a subscriber object could miss the first inbound messages from a publisher object.
FTL-5082 Fixed a defect in which the sample realm server start script, samples\scripts \ftlstart.bat, did not automatically load the sample realm definition.
This defect was limited to Windows platforms only.
FTL-5078 Fixed a defect in which tibstore and tibbridge executables could exit abruptly
upon receiving unrecognizable command line parameters.
FTL-5051 Fixed a defect in which the .NET method IMessage.IsFieldSet could return true
even when the field was not set in the message.
FTL-5025 Fixed a defect in which create subscriber calls could use the subscriber name mapping form the default application instance definition rather than from the named application instance.
FTL-5023 Improved performance of event queue dispatch with no wait.
FTL-5016 Fixed a defect in which a subscribing application could exit abruptly. This symptom could occur on a multicast transport with high reliability time, in situations of heavy network packet loss.
FTL-5011 Fixed a defect in which threads contending to connect to a tibstore server could deadlock.
FTL-4966 Fixed a defect in which memory could grow without bound in a subscriber to a standard durable. This defect could occur when the publisher sent built-in opaque messages and overflowed its transport's backlog buffer.
FTL-4920 Improved logging for multicast transports on Windows platforms.
FTL-4877 Fixed a defect in which the persistence server did not reassign messages left unacknowledged by a subscriber to a shared durable.
Key Summary
FTL-4846 Fixed a defect in which utilities and scripts accepted only lower case web protocol names in arguments.
FTL-4820 Fixed a defect in which an application process with durable subscribers could exit abruptly after the persistence server overflowed its client transport's backlog buffer.
FTL-4653 Fixed a defect in which a subscriber on a multicast tranport with more than one listen group could erroneously send retransmission requests to the wrong publisher.
FTL-4634 Fixed a defect in which the realm server displayed excessive monitoring data for event queues, which could cause browsers to exit abruptly.
FTL-4591 Eliminated a potential deadlock that could occur when the application attempted to close the realm object while reconnecting to the realm server.
FTL-4582 Fixed a defect in which a subscriber on a standard durable could receive messages out of order. This symptom could occur either if a transport's backlog buffer overflowed at a publisher, or if a temporary network disconnect interrupted a direct path transport.
FTL-4579 Fixed a defect in which the client library did not generate a upstream data loss advisory after a transport bridge restarted.
FTL-4578 Fixed a memory leak that occurred when closing a durable subscriber.
FTL-4560 Fixed the error description string indicating that a field is not found in a message. FTL-4545 Fixed a defect in which clients could not connect to a realm server. This symptom could occur when the value of the host portion of the --ftl realm sever command
line parameter was either * or omitted.
FTL-4538 Fixed a defect in the usage text of the realm server command line interface. FTL-4415 Fixed tibstore memory leaks that could occur after a subscriber on a standard
durable reconnected to the persistence server.
FTL-4463 Improved configuration validation for process transport definitions.
FTL-4396 Fixed a defect in durable monitoring reported interaction times for durables without any clients.
Key Summary
FTL-4289 Fixed a defect in which client processes could leak file descriptors. These actions were associated with this leak:
● Client programs opening and closing the realm object
● Administrators dynamically adding and removing transports
This defect was limited to Mac OS X platforms only.
FTL-4219 Fixed a defect in which the client library did not reclaim transport resources until the application closed the realm object.
Known Issues
The table lists known issues in version 4.2.0 of TIBCO FTL software.
Key Summary
FTL-5184 Summary: Applications that publish through a multicast transport could exhibit
unbounded memory growth under the following conditions:
● The publisher runs on a Windows platform.
● The Reliability Time parameter of the multicast transport is greater than
zero.
● The Reliability Memory parameter of the multicast transport is not
configured.
Workaround: Configure the Reliability Memory parameter to limit memory
growth.
FTL-5177 Summary: A secure affiliated realm server with a long host name cannot connect to
its primary secure realm server.
The affiliated realm server continues to output a Java exception with description
string too long until you explicitly stop the process.
Workaround: Supply a shorter name when starting the affiliated realm server,
using the --server.label command line parameter.
FTL-5176 Summary: On Mac OS X platforms, TIBCO FTL Python scripts cannot connect to a
secure realm server.
The reason is an incompatibility between OpenSSL versions. The default Python installation on Mac OS X platforms uses OpenSSL 0.9.8. TIBCO FTL software requires OpenSSL 1.0.1.
Workaround: Install Python using either the MacPorts package manager or the
Homebrew package manager. Ensure that the Python installation uses OpenSSL 1.0.1.
FTL-5128 Summary: Inbox Communication through a Transport Bridge
If two application processes communicate through a transport bridge, and one application uses a Release 3.x library while the other uses a Release 4.x library, then they cannot exchange messages using inbox communications.
Workaround: Upgrade the applications and the transport bridge to the latest
release.
FTL-4976 Summary: IPv4 Overrides IPv6, or Vice Versa
If the realm server command line specifies --http hostname:port, and hostname
resolves to both IPv4 and IPv6 addresses, then the realm server binds to only the computer's preferred address. For example, if the preferred address is IPv4, then clients cannot connect to the IPv6 address. If the preferred address is IPv6, then clients cannot connect to the IPv4 address.
Key Summary
FTL-4386 Summary: Chrome and Safari browsers can no longer access TIBCO HTML
documentation from a file system, that is, using the file:// protocol. Workaround: Access using a different browser, or access the HTML
documentation through the web, that is, using the http:// protocol.
