TIBCO Rendezvous Release Notes · TIBCO Rendezvous Release Notes 2 | Release Notes New Features This section lists features and the release they were added to this product. Reference

Two-Second Adv

TIBCO Rendezvous®

Release NotesSoftware Release 8.4.2March 2014

antage®

Important 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, The Power of Now, TIB, Information Bus, Rendezvous, TIBCO Rendezvous and Messaging Appliance are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.Enterprise Java Beans (EJB), 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 © 1997–2014 TIBCO Software Inc. ALL RIGHTS RESERVED.

TIBCO Software Inc. Confidential Information

| iii

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixHow to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixHow to Access All TIBCO Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixHow to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Deprecated Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Release 8.4.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Release 8.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Release 8.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Release 8.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Release 8.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Release 8.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Release 7.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Retraction of Deprecation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Operating System Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Migration and Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Release 8.3.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Release 8.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Release 8.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Release 8.x. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Release 6.x. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Release 5.x. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Special Note for IBM i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

TIBCO Rendezvous Release Notes

iv | Contents


| v

Preface

TIBCO Rendezvous® is a messaging infrastructure product.

TIBCO is proud to announce the latest release of TIBCO Rendezvous®. This release is the latest in a long history of TIBCO products that leverage the power of the Information Bus® to enable truly event-driven IT environments. To find out more about how TIBCO Rendezvous and other TIBCO products are powered by TIB® technology, please visit us at www.tibco.com.

Topics

• Typographical Conventions, page vi

• Connecting with TIBCO Resources, page ix


vi | Typographical Conventions

Typographical Conventions

The following typographical conventions are used in this manual.

Table 1 General Typographical Conventions

Convention Use

TIBCO_HOME

ENV_HOME

TIBRV_HOME

Many TIBCO products must be installed within the same home directory. This directory is referenced in documentation as TIBCO_HOME. The value of TIBCO_HOME depends on the operating system. For example, on Windows systems, the default value is C:\tibco.

Other TIBCO products are installed into an installation environment. Incompatible products and multiple instances of the same product are installed into different installation environments. An environment home directory is referenced in documentation as ENV_HOME. The default value of ENV_HOME depends on the operating system. For example, on Windows systems the default value is C:\tibco.

TIBCO Rendezvous installs into a version-specific directory inside TIBCO_HOME. This directory is referenced in documentation as TIBRV_HOME. The value of TIBRV_HOME depends on the operating system. For example on Windows systems, the default value is C:\tibco\rv\8.4.

code font Code font identifies commands, code examples, filenames, pathnames, and output displayed in a command window. For example:

Use MyCommand to start the foo process.

bold code

font Bold code font is used in the following ways:

• In procedures, to indicate what a user types. For example: Type admin.

• In large code samples, to indicate the parts of the sample that are of particular interest.

• In command syntax, to indicate the default parameter for a command. For example, if no parameter is specified, MyCommand is enabled: MyCommand [enable | disable]


Preface | vii

italic font Italic font is used in the following ways:

• To indicate a document title. For example: See TIBCO FTL Concepts.

• To introduce new terms For example: A portal page may contain several portlets. Portlets are mini-applications that run in a portal.

• To indicate a variable in a command or code syntax that you must replace. For example: MyCommand PathName

Key combinations

Key name separated by a plus sign indicate keys pressed simultaneously. For example: Ctrl+C.

Key names separated by a comma and space indicate keys pressed one after the other. For example: Esc, Ctrl+Q.

The note icon indicates information that is of special interest or importance, for example, an additional action required only in certain circumstances.

The tip icon indicates an idea that could be useful, for example, a way to apply the information provided in the current section to achieve a specific result.

The warning icon indicates the potential for a damaging situation, for example, data loss or corruption if certain steps are taken or not taken.

Table 1 General Typographical Conventions (Cont’d)

Convention Use

Table 2 Syntax Typographical Conventions

Convention Use

[ ] An optional item in a command or code syntax.

For example:

MyCommand [optional_parameter] required_parameter

| A logical OR that separates multiple items of which only one may be chosen.

For example, you can select only one of the following parameters:

MyCommand para1 | param2 | param3


viii | Typographical Conventions

{ } A logical group of items in a command. Other syntax notations may appear within each logical group.

For example, the following command requires two parameters, which can be either the pair param1 and param2, or the pair param3 and param4.

MyCommand {param1 param2} | {param3 param4}

In the next example, the command requires two parameters. The first parameter can be either param1 or param2 and the second can be either param3 or param4:

MyCommand {param1 | param2} {param3 | param4}

In the next example, the command can accept either two or three parameters. The first parameter must be param1. You can optionally include param2 as the second parameter. And the last parameter is either param3 or param4.

MyCommand param1 [param2] {param3 | param4}

Table 2 Syntax Typographical Conventions

Convention Use


Preface | ix

Connecting with TIBCO Resources

How to Join TIBCOmmunityTIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts, 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 http://www.tibcommunity.com.

How to Access All TIBCO DocumentationAfter you join TIBCOmmunity, you can access the documentation for all supported product versions here:

http://docs.tibco.com

How to Contact TIBCO SupportFor comments or problems with this manual or the software it addresses, please contact TIBCO Support as follows.

• For an overview of TIBCO Support, and information about getting started with TIBCO Support, visit this site:

http://www.tibco.com/services/support

• 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.


http://www.tibcommunity.com

http://docs.tibco.com

http://www.tibco.com/services/support


x | Connecting with TIBCO Resources


| 1

Release Notes

This document contains release notes for TIBCO Rendezvous®, Software Release 8.4.2.

Check the TIBCO Product Support web site at https://support.tibco.com for product information that was not available at release time. Entry to this site requires a username and password. If you do not have a username, you can request one. You must have a valid maintenance or support contract to use this site.

Topics

• New Features, page 2

• Changes in Functionality, page 10

• Deprecated Features, page 14

• Migration and Compatibility, page 18

• Closed Issues, page 22

• Known Issues, page 42

• Special Note for IBM i, page 47



2 | Release Notes

New Features

This section lists features and the release they were added to this product.

Reference #and Release Feature

New Features in Release 8.4.2

RV-3232

8.4.2

Documentation is now separate from the product installer.

TIBCO Rendezvous documentation is no longer bundled with the installer. You can obtain the documentation from https://docs.tibco.com/products/tibco-rendezvous.

For the complete documentation set, click the 8.4.0 version tab. For the most recent documentation updates, click the most recent version tab.

New Features in Release 8.4

RV-1582

8.4

Client Count in HOST.STATUS

HOST.STATUS advisory messages now carry a new field (cc) indicating the number of clients connected on a service.

RV-2102

8.4

DATALOSS.MSG_TOO_LARGE

A new advisory message indicates that a program sent a message that exceed TRDP size limits (64MB).

RV-2830

8.4

UDP TTL

TRDP daemons now accept a new command line parameter -udp-ttl, which lets you set the number of hops for UDP packets.

RV-2979

8.4

Task Capacity Zero

Enhanced distributed queues to permit zero as the task capacity (worker tasks), which results in a dedicated scheduler.


https://docs.tibco.com/products/tibco-rendezvous

New Features | 3


1-AF3HAA

8.3

POSIX Local IPC Sockets

For communication between a client and a daemon running on the same host computer, IPC sockets yield faster performance than TCP/IP sockets. All other TIBCO Rendezvous behavior is transparent to this choice of socket protocol.

IPC sockets are available only on UNIX platforms that support AF_UNIX or AF_LOCAL socket types.

1-AHDIFN

8.3

IPM

IPM is a linkable library that puts the core functionality of a TIBCO Rendezvous daemon (rvd) inside an application program process. By eliminating inter-process communication between the daemon and the application program, IPM can improve application data latency performance.

IPM is available only for applications coded in C, Java or .NET, running under Linux 2.6 (with glibc 2.3), Solaris x86 or Windows operating systems.

1-AIKG37

8.3

UDP Buffer Size

A new command line parameter for daemons overrides the default UDP buffer size for outbound multicast communication.

1-81KCMS

8.3

TCP Keepalive

The connection from a Rendezvous client application to a remote Rendezvous daemon now utilizes TCP keepalive (SO_KEEPALIVE). This enhancement rapidly alerts the client when the daemon disconnects.

TCP keepalive is enabled only at the client's socket (not at the daemon's accept socket).

TCP keepalive is an advanced TCP feature. Under ordinary circumstances, TIBCO does not recommend adjusting TCP keepalive parameters.

1-AHHMSS1-A94PF3

8.3

Improved Java performance

1-9ZYKSF

8.3

RVDM Purge Statistics

An RVDM enhancement lets you delete statistics records for a host and service.



4 | Release Notes

1-76PF3W

8.3

Self-Signed Certificates without Passwords

Secure daemons now let you omit the password when supplying a self-signed certificate that does not use a password.

1-AMJAF7

8.3

Daemons Report OpenSSL Library Version

1-AWNIVR

8.3

RPG sample programs and usage notes on IBM i platform.

New Features in Release 8.2.1

8.2 Windows 7

New platform support.


1-9NWKHL

8.2

Vector Listeners

Programs can now receive vectors of inbound messages. When used properly, vector listeners can improve throughput and latency performance by reducing message dispatch overhead.

New entry points in C, C++, Java. .NET and COBOL implement this feature.

1-93TW71

8.2

Send Message Vectors

Send methods in Java and .NET now support sending an array of messages with a single method call. This method is more efficient than a separate call for each message.

1-8YMTN0

8.2

Dispose—Release Native Messages

A new entry point, called dispose, in Java and .NET, gives programmers more control over message resources in the native C environment. You can release these resources independently of the Java or .NET message object, and without waiting for the garbage collector.

The benefits of managing memory resources properly can include more consistent latency, more consistent throughput, and lower consistent memory footprint.



New Features | 5

1-70URII

8.2

Java Message View

A new Java class, TibrvMsgView, enables more efficient read-only access to message fields.

1-9C11P3

8.2

Reliability Window

You can set the daemon’s reliability window for a specific service. API calls in C, C++, .NET, Java and COBOL let you request the reliability.

1-9HERRR

8.2

Latency Assessment Tool

rvlat measures latency statistics and produces reports to help you understand the latency characteristics of your network.

1-8YMTP0

8.2

Port Reuse

A new daemon parameter, -reuse-port, enables daemons and Rendezvous in-process modules on the same host computer to reuse service ports.

This feature is not available on HP Tru64 UNIX.

1-9FHNQB

8.2

Direct Communication

Transports that connect to TIBCO Messaging Appliance™ P-7500 (release 8.3 and later) are now eligible for direct communication. That is, connecting to a remote TIBCO Messaging Appliance P-7500 no longer disqualifies a transport—assuming that all other eligibility requirements are satisfied.

1-8LH3VN

8.2

RVDM JMX Interface

JMX MBeans let you configure RVDM using Java method calls, JConsole, or any other JMX-compliant console.

1-8LH3V2

8.2

RVDM Idle Mode

A new RVDM command line parameter lets you start RVDM in idle mode, so you can configure RVDM, yet RVDM does not communicate with managed daemons.

1-8K3ACZ

8.2

RVDM browser administration interface (control center) supports Safari browser.

1-8K3WPD

8.2

RVDM browser interface can now logout inactive users.



6 | Release Notes

1-8YMTKY

8.2

New methods in the Java configuration API let you examine RVDM settings.

1-9SDGTB

8.2

rvperf Uses Vectors

rvperfs automatically receives messages using vector listeners. The -non-vectored parameter forces it to use ordinary listeners.

rvperfm automatically sends messages using vector send calls. The -non-vectored parameter forces it to use individual send calls. (This parameter replaces the obsolete -vectored parameter with opposite behavior; see Changes in Functionality on page 10.)

1-9HL5XV

8.2

Routing Daemon Performance Improvements

Improved message routing performance of rvrd and rvsrd.

1-9VNAD1

8.2

Reconnection to a daemon that has a different IP address (than the original connection) now results in partial functionality. Previously, such connections were completely inoperable. Now, only point-to-point communication is inoperable, while multicast communication functions properly.

The error advisory message RVD.RECONNECT_FAILED is obsolete.

The new error advisory message CLIENT.IP_MISMATCH replaces it.

1-94WWDW

8.2

Enhanced RVCM performance.

1-9TLG65

8.2

Installation packages for Mac OS X on Intel hardware now include 64-bit executables.


1-1A8J5Z

8.1

Rendezvous Java libraries are now available for IBM z/OS and i5/OS operating system platforms. For details, see TIBCO Rendezvous Java Reference.

1-8MHDFF

8.1

Enhancements to the browser administration interface of managed daemons:

• Added a link from the Services page to the Subject Map page.

• Improved information on the Subject Map page regarding clients and subscribers.



New Features | 7

1-8LH3WZ

8.1

Improved RVDM control center interface:

• Improved feedback when updating the port map or service maps.

• Added a statistics page.

1-8MEQN0

8.1

Enhanced audit logging of authentication events in rvsd.

1-8LNZB7

8.1

Clarified documentation of CA-signed certificates and trust chains.

1-1YQZJ6

1-19CDLP

8.1

Secure daemons (rvsd and rvsrd) are now available on the z/OS platform.

New entry points in COBOL to access secure daemons.

1-8IQNVX

8.1

New entry points in COBOL to add, get and update string arrays and message arrays (as message field values).

1-8LNVNA

8.1

.NET publisher policy is now available on 64-bit Windows.

1-8UHO7I

8.1

SNMP for rvtrace has two new configuration parameters, and both are required for proper operation of the rvtrace SNMP agent. If you use this agent, you must update the configuration file. For details, see the documentation about rocommunity and rwcommunity in TIBCO Rendezvous Administration.

1-8V569Z

8.1

When installing on UNIX platforms, you can (serially) install several instances of Rendezvous software in different directories on the same file system.


1-84TCYN

8.0

Support for Windows Vista.

1-81K255

8.0

Rendezvous daemon manager (RVDM) lets administrators coordinate and manage the behavior of Rendezvous daemons throughout an enterprise.



8 | Release Notes

1-73T86H

8.0

Enhanced retransmission control operates at receivers (previously it operated only at senders). An additional daemon parameter configures the new feature, and an additional advisory message reports on its operation.

1-MV64I

8.0

rvcache now supports both deep and shallow merging of nested messages. For backward compatibility, the default behavior is shallow merging.

1-6QQMFW

8.0

rvcache now offers memory-only mode, which sacrifices persistence of cached values to gain speed by eliminating disk I/O. For backward compatiiblity, the default behavior is to write cached values to the store file.

1-7BE2X9

8.0

TibrvCmTransport.destroyEx is now available in the Java API JNI full-message implementation. (Previously it was available only in the JNI thin-message implementation.) This method blocks until the a distributed queue completes its assigned tasks, then destroys the transport and returns.

1-6XY075

8.0

A new entry point (C, C++, Java and .NET) gets the number of unassigned task messages in a distributed queue. (A task is unassigned if the scheduler has not yet assigned it to any worker.)

1-6XM8YR

8.0

A new Java entry point resets a message object, clearing its fields and address information.

1-75RIVK

8.0

A new .NET entry point, getXmlAsStringByIndex(), gets the value of an XML field from a message by index, and converts it to a string.

1-791699

8.0

The .NET Dispatcher constructor now accepts a thread name as an argument. When absent, it supplies a default name.

1-785FO8

8.0

Enhanced .NET DLL versioning so programmers no longer need to recompile .NET projects with each new release of Rendezvous.

1-6SSLQ2

8.0

New entry points in C, Java and .NET support arrays of messages and arrays of strings as message field types.

1-7CCTTK

8.0

Improved implementation of client detail reporting in the rvd browser administration interface. The report now displays the client's TCP port number. The report also displays the IP address, even for clients older than release 7.5.0.



New Features | 9

1-82OJN9

8.0

Extended the entry point for setting a CM transport’s publisher inactivity discard interval to the .NET and C++ APIs (it already existed in C and Java).

1-75JDV6

8.0

Improved sizing of UDP socket buffers.

1-7XU4CP

8.0

Enhanced rvd to output command line parameters in its start banner.

1-6R2N0B

8.0

Enhanced rvd browser administration interface. When the Information Alerts field of the Service Detail page displays alerts about inbound data loss, it now includes a list of IP addresses from which retransmissions were not available.

1-71UVYN

8.0

Enhanced the rvcache browser administration interface to show field IDs within cached messages.

1-1ZYOYV

8.0

Improved rvrd fault tolerance behavior to eliminate unnecessary failover switching.

1-6JQWQK

8.0

A new advisory message, _RV.ERROR.SYSTEM.RVD.RECONNECT_FAILED, indicates that after becoming disconnected from its daemon, the transport cannot reconnect at the same IP address.



10 | Release Notes

Changes in Functionality

This section lists changes to product functionality and the release when the change was introduced.

Reference #and Release Functionality

Release 8.4.2

8.4.2 Rendezvous Java language interface and RVDM now support only JRE 1.7.

Hardware and operating systems that do not support JRE 1.7 no longer support the Rendezvous Java interface nor other Java-based components.

The exception to this change is HPUX 11 on HP-PA RISC hardware, for which TIBCO Rendezvous supports only JRE 1.6. (Note that this platform is deprecated.)

Release 8.3

8.3 Rendezvous Java language interface now supports only JRE 1.6.

Hardware and operating systems that do not support JRE 1.6 no longer support the Rendezvous Java interface.

8.3 The Rendezvous documentation set no longer includes NDoc pages for .NET classes and methods. (NDoc does not support .NET 2.0.)

Release 8.2

8.2 TIBCO Rendezvous no longer adds new features to the Microsoft COM interface.

This release does include a COM interface for VC8 and VC9 (32-bit only). Legacy COM applications should migrate smoothly to VC8 and VC9.

Furthermore, legacy COM applications running with earlier releases of Rendezvous (for example, under VC7) interoperate correctly with Rendezvous 8.2 daemons.

8.2 TIBCO Rendezvous no longer supports VC7 (Visual C++). Support carries forward to VC8 and VC9.


Changes in Functionality | 11

8.2 We now use different names to refer to the Java JNI implementations—however, we have not changed the names of the archive files, nor removed any previously supported functionality from either implementation.

• JNI Preferred implementations: tibrvnative.jar and tibrvnativesd.jar (formerly known as native thin-message implementations).

• JNI Backward Compatibility implementations: tibrvj.jar and tibrvjsd.jar (formerly known as native full-message implementations).

8.2 The rvperfm parameter -vectored is obsolete. The behavior it previously specified—to send messages using vector send calls—is now the default behavior for rvperfm. A new parameter, -non-vectored, specifies the opposite behavior—namely, send messages using individual calls (see New Features on page 2).

The rvperfm parameter -batch has changed. The previous default behavior was 1 message per batch. The new default behavior 128 messages per batch.

1-9VNAD1

8.2

Reconnection to a daemon that has a different IP address (than the original connection) now results in partial functionality. Previously, such connections were completely inoperable. Now, only point-to-point communication is inoperable, while multicast communication functions properly.

The error advisory message RVD.RECONNECT_FAILED is obsolete.

The new error advisory message CLIENT.IP_MISMATCH replaces it.

Release 8.1

8.1

1-8SVGYY

The protocol subjects for RVDM have changed in release 8.1, with the following compatibility consequences:

• Release 8.1 RVDM communicates with managed daemons from both 8.1 and 8.0.

• Release 8.0 RVDM cannot communicate with managed daemons from release 8.1.

8.1

1-8V2F0H

The utility rvntsreg.exe has a new required command line parameter. You must supply an additional argument when you use this utility to register Rendezvous daemons as Windows services. For details, see TIBCO Rendezvous Administration.



12 | Release Notes

8.0

1-8FHUJA

COBOL call names have changed in release 8.1. All calls now begin with the prefix tibrv instead of trvOS. Old call names are deprecated, and will become obsolete in release 9.

New calls added in release 8.1 exist only with prefix tibrv.

8.0

1-8IQNNN

COBOL call tibrv_CurrentDate is obsolete, and is replaced by tibrvMsg_GetCurrentTime and tibrvMsg_GetCurrentTimeString.

8.0

1-8IQNR2

The following COBOL calls have been renamed:

Old tibrvCCEvent_CreateListener

New tibrvcmEvent_CreateListener_Cobol

Old tibrvCBEvent_CreateListener

New tibrvEvent_CreateListener_Cobol

Old tibrvCBQueue_TimedDispatch

New tibrvQueue_TimedDispatch_Cobol

Old tibrvCBEvent_Destroy and tibrvCCEvent_DestroyNew tibrvEvent_Destroy

Release 8.0

8.0

1-8D9X5B

The Rendezvous Java client API requires JDK 1.4 or later.

Features such as RVDM and the TIBCO Universal Installer require JDK 1.5 or later.

8.0

1-8JP9VT

The new TIBCO Universal Installer installs Rendezvous 8 to a different destination root directory than old-style installers (which overwrote previously installed versions of Rendezvous).

In particular, installing Rendezvous 8 after an existing TRA leaves two versions of Rendezvous in separate locations—the old version (installed with TRA) and the new version. Other TIBCO products that depend on TRA use Rendezvous daemons from the new version, but continue to use Rendezvous libraries from the old version.

8.0

1-8LK0WX

A default ticket file (tibrv.tkt) is no longer provided; however, the daemon behavior is unchanged (operation without a ticket file and with the old default ticket file is the same).



Changes in Functionality | 13

8.0 TIBCO Rendezvous no longer supports the UnixWare operating system platform.



14 | Release Notes

Deprecated Features

This section describes deprecated features and lists equivalent features that accomplish the same result, if relevant. 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 equivalent feature.

This section also lists features that are removed (if any).

Release 8.4.2

Web JAR The TIBCO Rendezvous web JAR is deprecated. TIBCO plans to withdraw support in a future release.

Platforms Please note the following changes in platform support.

Release 8.4

COM The Rendezvous COM API is deprecated. TIBCO plans to withdraw support for Microsoft COM in a future release.

VMSSingle-Thread

Applications

Support for single-thread application programs is deprecated on VMS platforms. In a future release TIBCO will no longer support this usage on VMS.

Silent Uninstall Silent uninstallation is not available (TIBCO Universal Installer 2.9).

Visual Studio2005

Microsoft Visual Studio 2005 is deprecated. TIBCO plans to withdraw support for this version in a future release, and instead support a more recent version.

Table 3 Platform Support Changes

Platform Status Description

HPUX 11 on HP-PA RISC hardware

Deprecated TIBCO plans to withdraw support in a future release.

Solaris 8 and 9 on SPARC hardware


Windows XP on x86 and x86-64 hardware



Deprecated Features | 15

Platforms Please note the following changes in platform support.

Release 8.3Please note the following changes in platform support.



AIX 5.2 Obsolete TIBCO no longer supports this platform.

FreeBSD Obsolete TIBCO no longer supports this platform.

Linux Itanium Obsolete TIBCO no longer supports this platform.

Mac OS X 10.4 PowerPC Obsolete TIBCO no longer supports this platform.

OpenVMS Alpha v.7.3-2 Obsolete TIBCO no longer supports this platform.

Solaris 9 x86 32-bit Obsolete TIBCO no longer supports this platform.

Tru64 Obsolete TIBCO no longer supports this platform.



AIX 5.2 Deprecated TIBCO plans to withdraw support in a future release.

FreeBSD Deprecated TIBCO plans to withdraw support in a future release.

Tru64 Deprecated TIBCO plans to withdraw support in a future release.

Linux Itanium Deprecated TIBCO plans to withdraw support in a future release.

Linux (2.4 kernel) Obsolete TIBCO Rendezvous now supports only the Linux 2.6 kernel.

Mac OS X 10.4 Deprecated TIBCO Rendezvous plans to withdraw support in a future release.


16 | Release Notes

Release 8.2

COM TIBCO Rendezvous no longer adds new features to the Microsoft COM interface.

Rendezvous 8.2 does include a COM interface for VC8 and VC9 (32-bit only). Legacy COM applications should migrate smoothly to Rendezvous 8.2 with VC8 and VC9.

Furthermore, legacy COM applications running with earlier releases of Rendezvous (for example, under VC7) interoperate correctly with Rendezvous 8.2 daemons.

VC7 TIBCO Rendezvous no longer supports VC7.

MacintoshPowerPC

Support for Apple Macintosh PowerPC hardware is deprecated. In a future release TIBCO will no longer this platform (that is, Rendezvous will support OS X on Intel processors only.)

Release 8.1

COBOL COBOL call names have changed in release 8.1. All calls now begin with the prefix tibrv instead of trvOS. Old call names are deprecated, and will become obsolete in release 9.

Release 8.0

UnixWare TIBCO Rendezvous no longer supports the UnixWare operating system platform.

Release 7.5

-log-rotate rvd, rvrd, rvsd, rvsrd, rva, rvtrace share a command line parameter governing log file rotation. This command line parameter, -log-rotate n, is deprecated in release 7.5, and will become obsolete in a subsequent release. We recommend migrating to the new log rotation parameters (-log-max-size and -log-max-rotations) at your earliest convenience.

Mac OS X 10.5 PowerPC Obsolete OS X 10.5 does not support PowerPC hardware.




Deprecated Features | 17

In the meantime, we preserve backward compatibility by converting the value of this deprecated parameter to corresponding values of the new parameters

-w-rotate rvtrace had a parallel command line parameter governing data capture file rotation. This command line parameter, -w-rotate n, is deprecated in release 7.5, and will become obsolete in a subsequent release. We recommend migrating to the new data capture file rotation parameters (-w-max-size and -w-max-rotations) at your earliest convenience.

In the meantime, we preserve backward compatibility by converting the value of this deprecated parameter to corresponding values of the new parameters.

Retraction of DeprecationIn release 7.3 we announced deprecation of two Java JNI libraries. Full support for these libraries (now called the full-message implementations) has now been restored; they are no longer deprecated.

Operating System SupportIn general, we do not support TIBCO software on operating system releases that are no longer supported by their vendors.


18 | Release Notes

Migration and Compatibility

This section explains how to migrate from a previous release to this release.

Release 8.3.2

Installation Batch Scripts (Windows)

Installation batch scripts (*.bat) on Windows platforms must now invoke the TIBCO Universal Installer using the CALL command. Existing scripts that invoke the installer directly must be changed to use the CALL command, for example:

CALL .\TIBCOUniversalInstaller -silent

Release 8.2

Reusing Service Ports

This new feature requires a potentially extensive upgrade throughout the enterprise. For details, see Reusing Service Ports in TIBCO Rendezvous Administration.

Java Minimum Version

Rendezvous Java API requires Java 1.5 (or later).

RVDM JMX interface requires Java 1.6 (or later).

Rendezvous configuration tools and API require Java 1.4 (or later).

Release 8.1

RVDM Compatibility with Rendezvous 8.0


• Release 8.1 RVDM communicates with managed daemons from both 8.1 and 8.0. For details on configuring routing daemons to forward protocol subjects, see Forward RVDM Protocol Messages across Network Boundaries in TIBCO Rendezvous Administration.


Migration and Compatibility | 19


SNMP and rvtrace

SNMP for rvtrace has two new configuration parameters, and both are required for proper operation of the rvtrace SNMP agent. If you use this agent, you must update its configuration file. For details, see the documentation about rocommunity and rwcommunity in TIBCO Rendezvous Administration.

Release 8.x

Compatibility with TRA 5.5.x and Hawk 4.7

Table 6 describes the effect of installing Rendezvous 8.x over one of these existing products.

Table 7 on page 20 describes the effect of installing one of these products over existing Rendezvous 8.x.

Rendezvous 8.x compatibility with either TIBCO Runtime Agent (TRA) 5.5.x or TIBCO Hawk 4.7 depends on the exact combination, the order of installation, and the operating system platform. If your organization uses either of these TIBCO products, read this section carefully.

Table 6 Compatibility: Installing Rendezvous 8.x over Existing Products that Include Rendezvous 7.5.x

Existing Support and Effect

TRA 5.5.x The installer for TRA 5.5.x has already installed Rendezvous 7.5.4.

We support installing Rendezvous 8.x.

While both versions can exist simultaneously on one host computer, TRA starts Rendezvous 7.5.4 daemons.

Hawk 4.7 The installer for Hawk 4.7 has already installed Rendezvous 7.5.2. (You might have subsequently upgraded to a later release of Rendezvous 7.5.x.)

We do not support installing Rendezvous 8.x over standalone Hawk 4.7 (without TRA 5.5.x).


20 | Release Notes

Migrating to Release 8.x on OpenVMS Platforms

Forward Migration

In general, applications linked with shareable images migrate forward to new versions of TIBCO Rendezvous without any need to relink; they usually operate smoothly with newer shareable images.

Table 7 Compatibility: Installing Products that Include Rendezvous 7.5.x over Existing Rendezvous 8.x

Existing WindowsSupport and Effect

UNIXSupport and Effect

TRA 5.5.x We support installing TRA 5.5.x over Rendezvous 8.x.

The installer for TRA 5.5.x installs Rendezvous 7.5.4.

While both versions can exist simultaneously on one host computer, TRA starts Rendezvous 7.5.4 daemons.

We support installing TRA 5.5.x over Rendezvous 8.x.

The installer for TRA 5.5.x installs Rendezvous 7.5.4. Both Rendezvous releases can exist simultaneously on one host computer

When installing TRA 5.5.x, the installer prompts you to select the effective Rendezvous release; TRA starts Rendezvous daemons from the release that you select.

Hawk 4.7 We support installing Hawk 4.7 over Rendezvous 8.x.

The Hawk installer overwrites any existing 7.5.x installation with Rendezvous 7.5.2.

While both versions can exist simultaneously on one host computer, Hawk starts Rendezvous 7.5.2 daemons.

We support installing Hawk 4.7 over Rendezvous 8.x.

The Hawk installer overwrites any existing 7.5.x installation with Rendezvous 7.5.2.

When installing Hawk 4.7, the installer prompts you to select the effective Rendezvous release. Nonetheless, we do not support selecting Rendezvous 8.x in this combination—you must select Rendezvous 7.5.2.

For additional information about compatibility of Rendezvous 8.x, TIBCO Hawk® 4.7 (or older), TIBCO Designer™ and TIBCO BusinessWorks ™, see the known issue note 1-8KWJMP on page 46.


Migration and Compatibility | 21

Exception: In Rendezvous release 8.0, we reorganized the Rendezvous shareable image libraries on OpenVMS platforms, in order to resolve issues with third-party libraries. As a result, you must relink applications linked with shareable image libraries when you upgrade across this division (from 7.5.4 or earlier, to 8.0 or later, on OpenVMS).

Older Shareable Libraries

Applications that link with sharable images usually cannot run with older shareable libraries (from earlier Rendezvous releases). The reason is that new releases can introduce new entry points, which are absent from older shareable libraries.

This incompatibility can cause problems if you link an application against a current shareable library, and then distribute it to other host computers where it runs with older shareable libraries.

Release 6.x• When started via the command line, rvd will no longer exit when there are no

connected clients. Daemons which are started with the -no-permanent flag will exit 2 minutes after the last client disconnects.

• The RV 7 API includes a mechanism which allows the application developer to turn on timer-based batching at the individual transport level for use in those situations where reduced context switching and/or reducing the number of small packets delivered to the network is more important than data latency.

• RV 7 now requires use of WINSOCK2 on Microsoft platforms. Applications which are statically linked on Microsoft platforms must explicitly link in ws2_32.lib.

Release 5.x• Rendezvous 7 (and later) applications will not be able to autostart daemons

earlier than release 6.

• The Rendezvous 5.3 compatibility libraries are not included in the Rendezvous 7 (and later) distribution.


22 | Release Notes

Closed Issues

This section lists issues that were closed in the named releases.

Reference #and Release Description

Issues Closed in Release 8.4.2

RV-3270RV-2782

8.4.2

Fixed a packaging defect in which the Mac OS X installer did not include the correct 64bit libz dependency for the 64bit SSL libraries.

This issue arose only for Mac OS X 10.7 (or later) on x86 hardware when using 64-bit JVM. It affected only Java clients of the 64-bit secure daemons (rvsd or rvsrd).

RV-3218

8.4.2

Updated OpenSSL to version 0.9.8y (prevously used 0.9.8o).

RV-3257

8.4.2

Fixed a Java defect in which using tibrvj.jar within an application server could cause the JVM to exit abruptly.

RV-3213

8.4.2

Fixed a defect in which a routing daemon could stop routing messages after recovering from loss of network connectivity with neighboring routers. This symptom could occur in large routing topologies with large numbers of subscriptions.

RV-3209

8.4.2

Fixed a defect in which a heavily loaded daemon could prematurely present a CLIENT.SLOWCONSUMER advisory to clients.

RV-3202

8.4.2

Fixed a installation defect that affected Windows 32- and 64-bit packages. This release updates the Microsoft Visual C redistributable runtime library.

RV-3201

8.4.2

Improved routing daemon processing of release 5.x client shutdowns when a routing daemon is tracking many subscriptions.

RV-3115

8.4.2

Fixed a defect in which the Java library could ignore the worker complete time set by a distributed queue member. (This symptom affected only the tibrvnative.jar library.)

RV-3105

8.4.2

Fixed a defect in which a Java application could abruptly exit while processing a CM or DQ messages outside of the dispatch thread. (This symptom affected only the tibrvnative.jar library.)


Closed Issues | 23

RV-2906

8.4.2

Fixed a Java library defect in which programs could abruptly exit when the constructor TibrvRvdTransport received null as the license ticket.


RV-3170

8.4.1

Fixed a daemon defect in which the daemon process could abruptly exit when the last client on a service disconnected.

RV-3161RV-3164

8.4.1

Fixed a defect in which distributed queue listeners could not receive certified messages after restart of their remote daemon.

RV-3160

8.4.1

Moved rvlat.jar to the bin directory (formerly in the lib directory).

RV-3157

8.4.1

Improved memory allocation performance.

RV-3154

8.4.1

Fixed a routing daemon defect in which routers serving the same local network could fail to synchronize their subscriptions.

RV-3146

8.4.1

Fixed a defect in which the routing daemon could abruptly exit.

RV-3141

8.4.1

Fixed a certified delivery library defect in which a CM correspondent did not receive messages. This symptom could occur after destroying a CM listener and then recreating the listener for the same correspondent.

RV-3140

8.4.1

Fixed a Java API library defect in which a new TibrvMsg object could erroneously have values set for its send and reply subjects.

RV-3137

8.4.1

Fixed a defect in which rvtrace did not rotate its log files at the correct file size (Windows platforms only).

RV-3131

8.4.1

Fixed a daemon defect in which reusing service ports (-reuse-port option) could cause dataloss. This defect affected only Linux platforms.



24 | Release Notes

RV-3130

8.4.1

Fixed a Java API defect in which TibrvMsg.add could not add an opaque field with zero length.

RV-3128

8.4.1

Fixed a defect affecting virtual circuits, in which send calls could deadlock in situations involving high message rates.

RV-3117

8.4.1

Fixed a defect in which daemons did not rotate their log files at the correct file size (Windows platforms only).

RV-3111

8.4.1

Fixed a routing daemon defect in which RV 8 routers did not forward subscription interest to neighbors after upgrading from RV 7.

RV-3108

8.4.1

Fixed an API library defect in which clients could automatically start a daemon process even though they specify a daemon host.

RV-3102

8.4.1

Addressed known issue RV-2730 (previously RV-2884). This fix addresses the issue only for Linux kernels 2.6.31 and higher (for example, RHEL6).

RV-3091

8.4.1

Fixed a defect in which a managed daemon could exit abruptly while processing network statistics.

RV-3086

8.4.1

Fixed a library defect on Solaris platforms that required application programs to relink with the -lrt flag.

RV-3085

8.4.1

Fixed a defect in which clients could not initialize a transport using the loopback interface (as the network parameter) when connecting to a daemon that enabled -reuse-port.

RV-3082

8.4.1

Fixed a defect in which a border router did not forward message data among its own local networks.

RV-3080

8.4.1

Fixed a defect in which a daemon could exit abruptly if did not have write permissions for its log file directory (UNIX only).

RV-3076

8.4.1

Fixed a Java API defect in which Tibrv.open could overwrite the string encoding value.



Closed Issues | 25

RV-3060

8.4.1

Fixed a defect in which the daemon could close a service, but its UDP receive socket could erroneously remain open. Subsequent attempts to start clients on that service would fail.

RV-3054

8.4.1

Fixed a daemon defect in which using the HTTP interface while a client was connecting could cause the daemon to deadlock.

RV-3036

8.4.1

Fixed a Java API defect in which convenience methods could return a negative value from an unsigned message field.

When the value does not fit into the specified Java type, these methods now cast the value to a larger type. For example, TibrvMsg.getShort extracting 65535 returns a 32-bit int rather than a 16-bit short, which Java would interpret as -1.

RV-3013

8.4.1

Fixed a defect (Solaris only) in which daemons were limited to approximately 1000 clients.

RV-3008

8.4.1

Fixed a Java API defect in which extracting the value 65535 from an unsigned short message field would yield -1 instead.

RV-2951

8.4.1

Fixed an rvrd defect in which release 8.3.2 introduced an incompatibility in the format of the routing daemon XML configuration file. Later releases could not read files that had been dumped by earlier releases.

RV-2922

8.4.1

Fixed a tibrvcfg defect in which RvdProxy.getServices could throw an exception.

RV-2907

8.4.1

Fixed a tibrvcfg defect in which ComponentInformation.getProcessID could throw an exception.

RV-2885

8.4.1

Fixed a daemon defect in which the browser interface could report an incorrect subscription count.


RV-3015

8.4.0

Fixed a defect in the distributed queue library, and reduced the cost of storage and accounting for processing reliable messages sent to distributed queues.

RV-2985

8.4.0

Fixed a defect in which the subscription list of a fault-tolerant routing daemon could become inaccurate (unsynchronized).



26 | Release Notes

RV-2979

8.4.0

Enhanced distributed queues to permit zero as the task capacity (worker tasks), which results in a dedicated scheduler.

RV-2967

8.4.0

Fixed a routing daemon defect that could cause excessive memory utilization at peak throughput.

RV-2943

8.4.0

Fixed a daemon defect on Windows XP platforms in which accumulation of handles during peak throughput bursts could affect overall host performance.

RV-2928

8.4.0

Fixed a daemon defect that resulted in lower throughput when the daemon delivered messages to clients. (This defect was introduced in release 8.3.0.)

RV-2939

8.4.0

Fixed a defect in which publishing to a wildcard subject could cause receiving distributed queue worker processes to exit abruptly.

RV-2946

8.4.0

Fixed a daemon defect in which the -listen parameter could not include TCP addresses within IPC specifications.

RV-2947

8.4.0

Fixed a daemon defect in which a managed routing daemon could exit abruptly at startup.

RV-2971

8.4.0

Fixed a daemon defect in which a managed daemon could exit abruptly during runtime.

RV-2920

8.4.0

Fixed a memory leak in the client library associated with queue limit policies discard first and discard last.

RV-2132

8.4.0

Routing daemons now exit immediately upon detecting store file corruption during OpenSSL initialization.

RVI-25

8.4.0

Fixed a daemon defect in which rvd would exit immediately when started without any command line parameters. This issue affected only IBM i platforms.


RV-2058

8.3.2

Fixed a defect on Mac OS X platforms in which 64-bit daemons did not receive messages when the -reuse-port feature was enabled.



Closed Issues | 27

RV-2204

8.3.2

Fixed a daemon defect in which the daemon would erroneously output a warning when the attempting to bound to a UDP that was already bound. (This operation is legal, so the warning is incorrect.) The warning had this form:

Unable to create transport on UDP port 9000. Current transport by specifying network as ';224.3.4.10' requests daemon to join multicast group 224.3.4.10, while transport previously created on this port by specifying network as ';224.3.4.10' did not express an interest in receiving data from that multicast group. You cannot associate the same service parameter with two different network parameters.

RV-2225

8.3.2

Fixed a defect in which the router’s browser interface and the tibrvcfg utility used different XML templates for dumping routing information.

RV-2723

8.3.2

Fixed a Java defect in which tibrvweb.jar erroneously attempted to load the RVCM library (which it does not support).

RV-2778

8.3.2

Fixed a daemon defect in which retransmission control (RXC) did not operate correctly when the sending daemon’s -reliability value was 1.

RV-2793

8.3.2

Fixed a Java defect in which the prepare-to-activate callback was inconsistent.

This issue affected only the Java native implementation library tibrvnative.jar.

RV-2806

8.3.2

Daemons now output log information when trdp packet sequence numbers roll past their maximum value.

RV-2808

8.3.2

Addressed a defect in which a daemon could exit abruptly when the daemon reported an advisory during the reliability window after its last client transport disconnected.

RV-2816

8.3.2

Fixed a Java defect in which calling TibrvMsg.dispose() more than once on the same message object could cause message corruption.

RV-2835

8.3.2

Fixed a library defect in which routing daemons erroneously reported Memory allocation failed errors, instead of the correct error string.

RV-2841

8.3.2

Improved memory utilization in daemons when clients disconnect.



28 | Release Notes

RV-2855

8.3.2

Fixed a defect in which a daemon could become unresponsive when a client or neighbor disconnected.

RV-2858

8.3.2

Fixed a defect in which managed daemons could report incorrect outbound statistics.

RV-2859

8.3.2

Fixed a defect in which the fault-tolerance library (RVFT) did not discriminate between inbox ports when several daemons on the same host computer enabled service port reuse.

In one symptom of this defect, fault-tolerant clients could erroneously activate.

RV-2833

8.3.2

Fixed a defect in which rvrd did not always discriminate between inbox ports when communicating with daemons that enabled service port reuse.

In one symptom of this defect, rvrd did not import or export subscriptions to other daemons.

RV-2868

8.3.2

Fixed a memory management defect in tibrvFtMonitor.

RV-2870

8.3.2

Fixed an RVDM defect in which log warning output was mislabeled as error output. The log output is “Reliability Interval not found.” It indicates that the reliability interval is set to zero. To eliminate the warnings, the administrator can change the daemon’s -reliability parameter.

RV-2873

8.3.2

Fixed a defect in which daemons or client applications could exit unexpectedly.

RV-2877

8.3.2

Fixed a defect in which a managed daemon could become unresponsive during a service map update.

RV-2888

8.3.2

Fixed a memory leak in which the daemon would leak memory every time a client connected.


RV-1681

8.3.1

Fixed a configuration API defect in which the dumpXML command for rvcache instances erroneously added fault tolerance values to its XML output (when fault tolerance was not enabled).



Closed Issues | 29

RV-2722

8.3.1

Fixed a daemon defect which could result in DATALOSS after a receiving daemon missed both the original TRDP data packet and a retransmission repair packet. In this situation, a subsequent NAK could trigger a race condition in which the sending daemon indefinitely deferred retransmitting additional repair packets.

RV-2731

8.3.1

Fixed a Java distributed queue (CMQ) defect in which the scheduler could assign additional tasks to a worker before the worker had finished its current task.

RV-2739

8.3.1

Fixed a daemon defect in which daemons spun one extraneous thread per client.

RV-2743

8.3.1

Fixed a configuration API defect in which methods could throw an exception indicating “unexpected error” when interacting with a daemon that uses local IPC sockets.

RV-2745

8.3.1

Fixed a fault tolerance API defect in which the library did not consistently issue the PREPARE_TO_ACTIVATE hint.

RV-2746

8.3.1

Fixed a defect in tibrvnative.jar in which adding (or updating) a string array field (in a message) could cause the JVM to exit abruptly. This symptom could occur when one of the strings in the array was a null string.

Instead of exiting, the method now throws an exception.

RV-2753

8.3.1

Fixed a routing daemon defect (introduced in release 8.0) in which routing daemons could erroneously disconnect from their neighbors. This symptom could occur when routers imported and exported the subject >, and a client also subscribed to the subject >.

RV-2756

8.3.1

Fixed a Java defect in which applets could fail to start because the pure Java implementation (tibrvjweb.jar) erroneously attempted to load a native library.

RV-2757

8.3.1

TIBCO Universal Installer can now install Rendezvous 8.3.1 and Hawk 4.9 in a single-pass installation.

RV-2762

8.3.1

Fixed a defect in which a daemon could become unresponsive when a client or neighbor disconnected.



30 | Release Notes

RV-2800

8.3.1

Fixed a daemon defect in which undefined behavior could result when packet sequence numbers rolled past the maximum integer (approximately 4.3 billion message packets). Possible symptoms could include unreported dataloss and missed protocol messages. This issue affected only TRDP daemons (not PGM) from release 8.2.0 and later.

RVI-7

8.3.1

Fixed a defect on IBM i platforms in which Java applications would not start.


1-ARE4X8

8.3.0

Fixed a daemon defect related to the order of multicast listen groups in client connection requests. The daemon would accept the first request, then erroneously reject subsequent requests that presented the multicast groups in a different order.

1-8TQ63Y

8.3.0

Fixed a defect in which clients erroneously received the advisory RVD.DISCONNECTED instead of CLIENT.NOMEMORY.

1-94LDB8

8.3.0

Fixed a defect in the C++ library which caused compiler warnings.

1-ACMRU2

8.3.0

Fixed a library defect which affected distributed queue (DQ) callback functions. If the callback function destroyed the CM listener and then created a new CM listener in its place, then the new listener did not receive any message data.

1-ALFHY9

8.3.0

Windows installation packages contain Microsoft’s C runtime library from VC8 (rather than VC9). This library operates correctly on both VC8 and VC9.

1-ANCH07

8.3.0

Migrated to OpenSSL 0.9.8o (previously 0.9.8l).

1-AP6IRJ

8.3.0

Fixed a Java library defect which could cause a race condition between dispatcher thread start and dispatcher thread destroy.

1-AU6YFE

8.3.0

Fixed a zOS library defect. On zOS systems without multicast support, if a daemon did not explicitly specify -no-multicast, then client transports could not connect to the daemon. Clients reported this error:

Failed to initialize transport: OS error



Closed Issues | 31


1-AJ01U1

8.2.2

Fixed a defect in which daemons from release 8.2.x would not retransmit data when requested by daemons from release 8.1.x and earlier.


1-ACJJ3N

8.2.1

Upgraded to OpenSSL 0.9.8l to address a security flaw in OpenSSL 0.9.8k.

1-ABYIRB

8.2.1

Daemons now use dynamic loading for OpenSSL (previously they used static loading).

1-AAI33H

8.2.1

Fixed a defect in which timed dispatch calls could time-out prematurely (in rare situations).

1-AAHU13

8.2.1

Fixed a memory leak in the .NET library. When application programs relied on the .NET garbage collector free message storage, the library did not free the native message (in the C environment). (In contrast, the Message.Dispose method correctly freed both the .NET message and the native message.)

1-A4POXZ

8.2.1

Fixed a defect in the fault tolerance libraries (RVFT) in which the SetWeight call resulted in abnormally high CPU utilization.


1-9H02E9

8.2

Improved performance of message and event dispatch by reducing lock contention.

1-9JC3L9

8.2

Fixed a defect in which release 8.0 and 8.1 routing daemons were incompatible with clients that use the release 5.4 (and earlier) Rendezvous library. Release 8.2 routing daemons are compatible with those clients.

1-972639

8.2

Fixed a defect affecting the reply phase of request/reply interactions over virtual circuit transports. Routing daemons did not correctly route reply messages.

1-9FLHFT

8.2

Fixed a defect in which a daemon could exit abruptly when its last client transport disconnected.



32 | Release Notes

1-9DL675

8.2

Fixed a defect in which a daemon could erroneously re-use the network parameter from the previous client connection request. As a result, transport creation could fail, repeatedly reporting an illegal attempt to use the same service on two different networks.

1-9CY3OA

8.2

Fixed a defect in which rvd could deadlock when the last client on a service disconnected.

1-9NCR0Q

8.2

Fixed an defect in which a 64-bit daemon with more than 60 clients could fail with this error message: select error: 10038 (The descriptor is not a socket). This symptom was platform-specific to Windows 2008.

1-933YGL

8.2

Fixed a defect in which routing daemon performance could degrade as a result of forwarding extraneous data. This symptom could occur in situations where listeners in the local network subscribed to subjects that were broader than the subject gating specified in the router. Restarting the router could trigger this symptom.

1-9WP2HV

8.2

Fixed a routing daemon defect involving border routing and fault tolerance. In some configurations the daemon could exit abruptly

1-8UPWVN

8.2

Fixed an rvrd configuration defect. The error log message that reported duplicate local network records did not contain sufficient information to resolve the issue.

1-993SFH

8.2

Fixed a defect in which routing daemons could overflow thread stacks on VMS platforms.

1-9DVJUJ

8.2

Fixed a defect in which simple sending applications caused the daemon to exit abruptly. (A simple sender is one that has only INBOX listeners—that is, no multicast subject listeners.)

1-8W20O8

8.2

Fixed a defect in the browser administration interface of non-managed communications daemons, in which the client subscription list erroneously omitted unicast (_INBOX) subscriptions.

1-9E5CD9

8.2

Fixed a daemon browser administration interface defect in which the subscription display could be incomplete.

1-9WSH7D

8.2

Fixed a defect in the daemon’s browser administration interface in which all hostnames displayed as [unresolved]. This symptom affected only 64-bit executables.



Closed Issues | 33

1-8YMJUT

8.2

Fixed a defect in which daemon and RVDM browser interfaces did not adequately protect against incorrectly structured URLs.

1-A275D9

8.2

Fixed an RVDM defect in which the browser administration interface of a managed daemon could erroneous report the port map feature as disabled.

1-8VAOS5

8.2

Fixed an RVDM defect in which subject mapping did not properly validate configuration values for multicast groups.

1-8VQZQF

8.2

Fixed an RVDM defect in which the subject map view did not display the settings related to wildcard publishing.

1-94QYWJ

8.2

Fixed an RVDM defect in which the parameter -rvdm-home did not support spaces in the string. The command line now supports spaces; enclose the entire value string in double-quote characters.

1-9DR9H1

8.2

Fixed a fault tolerance API defect in which changing weights dynamically could erroneously result in all group members becoming inactive.

1-9X8ZF5

8.2

Fixed a distributed queue scheduler defect. After a scheduler overflowed its backlog limit, the scheduler would not resume.

1-9FB63J

8.2

Fixed a Java API defect in which CMQ methods incorrectly interpreted a zero backlog limit.

1-91LMWP

8.2

Fixed a Java API defect in which exception logging did not report the root cause when Tibrv.open() failed to load the JNI library.

1-A3AG1V

8.2

Fixed a Java API defect in which TibrvTransport.setDescription() did not validate its arguments.

1-9IS22R

8.2

Fixed a Java library defect in which programs that send or receive XML messages could signal spurious java.lang.OutOfMemoryError exceptions.

1-9E38GR

8.2

Fixed a configuration API defect in which Service.getSubscriptions() could erroneously return an empty list of subscriptions.



34 | Release Notes

1-86NF0V

8.2

Fixed an XML configuration defect in which attempting to modify a routing daemon local network interface erroneously removed that interface.

1-9MN9UD

8.2

Fixed an XML configuration defect related to the routing daemon and the Rendezvous DTD.

1-9OEQV7

8.2

Fixed a defect in tibrvcfg which the parser did not correctly ignore whitespace surrounding numeric values.

1-9PZBAV

8.2

Fixed a defect in which non-secure daemons erroneously included hsaddr and hsport fields with zero values (these fields pertain only to secure daemons).

1-9WHFT1

8.2

Fixed a documentation defect in which the API reference books incorrectly described the behavior of transport destroy calls, event isValid calls, and listener getTransport calls.

1-6T6KT5

8.2

Enhanced documentation for tibrvQueueHook.

1-9L7PDX

8.2.0

Fixed a defect in which PGM daemons could not communicate with one another.

1-9GB3KB

8.2.0

Fixed a defect in which daemons did not recover from situations in which other daemons became unreachable. For example, after a temporary hardware failure of the NIC on daemon A, daemon B would not re-establish communication with daemon A. This defect occurred only on Windows XP SP3 platforms.


1-9725WI

8.1.2

Fixed an rvrd defect in which routers with more than 32 neighbors could develop memory corruption and exit abruptly.

1-9B49IZ

8.1.2

Fixed a daemon memory leak, associated with listeners disconnecting from the daemon.

1-8WWTIH

8.1.2

Fixed a defect in which RvdProxy.getClientTransports() did not properly parse user names containing dot (period) characters.



Closed Issues | 35

1-980Y1M

8.1.2

Fixed a daemon defect on Windows platforms in which thread deadlock prevented daemons from starting properly.

1-98538V

8.1.2

Fixed a defect in the virtual circuit feature, in which a terminal that sends a messages in a tight loop could enter a deadlock state.

1-987ZTX

8.1.2

Fixed a PGM defect affecting advisories that reported DATALOSS of point-to-point data:

• Sending daemons erroneously reported the DATALOSS incident with redundant advisories; local clients received two advisories for each incident.

• One of those two advisories contained an incorrect host IP address.

1-8WWY9H

8.1.2

Fixed an omission in the C example program tibrvftmon.c, so it now includes <string.h>.

1-97MJOR

8.1.2

Fixed a COBOL defect in which calls were not available in the library. For each call that has an extended (*Ex) variant (for example, tibrvMsg_GetStringEx), the base call (for example, tibrvMsg_GetString) was absent from the COBOL library.

1-8ZJPF8

1-8WM8B8

8.1.2

Fixed a defect in which secure daemons on z/OS platforms displayed the user name strings of applications without translating from EBCDIC to ASCII.

1-98LZBE

8.1.2

Fixed a COBOL defect in which listeners in a distributed queue could receive duplicate messages.


1-8YKCPR

8.1.1

Fixed a defect (introduced in release 8.1.0) in which Rendezvous libraries and daemons could erroneously reject messages as corrupt when the reply subject is longer than 120 characters. As a result, client applications could miss inbound messages. Note that rvrd routing—especially second-tier routing (border routing)—involves long reply subjects, and could trigger this symptom.

Issues Closed in Release 8.1

1-8M7IVF

8.1

Fixed a defect in formatting packet statistics in the rvrd browser administration interface.



36 | Release Notes

1-8U9F2J

8.1

Fixed an rvrd defect in which fault-tolerant routing daemons could not determine which daemon would import messages for local subscribers.

1-8B868Z

8.1

Fixed an rvrd defect in which specifying the -log-config parameter caused the daemon to abruptly exit.

1-8LNZH7

8.1

Fixed a defect in managed daemons in which listeners to > did not receive system messages (such as advisories).

1-8QKCFP

8.1

Fixed a defect in which the RVDM control center was susceptible to cross-site scripting.

1-8LNZHQ

8.1

Fixed a defect in which HOST.STATUS messages from managed daemons omitted the service and network fields.

1-8LK8PY

8.1

Fixed a defect in which release 8.0 did not support using PGM daemons in managed mode (with RVDM).

1-8KOL5O

8.1

Improved time to gather supplementary information in RVDM daemon table after fault-tolerant failover.

1-8RUEOD

8.1

Fixed a defect in which rvcache abruptly exited while reading store files larger than 4 GB.

1-8P5O3P

8.1

Fixed a defect in which rvcache in memory-only mode erroneously stored records for unique subjects matching a wildcard.

1-8KCX8M

8.1

Fixed a defect in which rvtrace with SNMP enabled would abruptly exit during its start sequence (on Solaris 10 Intel platforms only).

1-8UHW6P

8.1

Fixed a defect in the C client library that caused high CPU usage if a program accidentally closed one of the library's internal sockets.

1-8MP2VV

8.1

Improved C++ API source code to avoid warnings from stricter compilers.



Closed Issues | 37

1-8JDNAM

1-86CZXL

8.1

Fixed a memory growth defect associated with accessing message contents using the Java and .NET APIs.

1-8V5UUH

8.1

Fixed a memory growth defect in the .NET API.

1-8N8H7N

8.1

Fixed a Java API defect in which TibrvDispatchable.dispatch() stopped dispatching events after encountering a corrupt data message.

1-8EL2PA

8.1

Fixed a configuration API defect in which rvaProxy.getComponentInformation().getAsMap() indicated an incorrect value for httpTunnel.

1-8DYF23

8.1

Fixed a documentation defect at the description of configuration API method Router.addLocalNetworkInterface(). The document prescribed an incorrect default value for the networkSpecification parameter.

1-8DCXDN

8.1

Fixed a configuration API defect in which RvrdProxy.remove.Router() did not prevent removing a border router (which is illegal).

1-8DRX4U

8.1

Fixed a configuration API defect in which network interfaces based on default service and network values caused router.getLocalNetworkInterfaces to return null (instead of a valid network interface object).

1-8E076V

8.1

Fixed a configuration API defect related to borderRouter.getPolicyRules and the command tibrvcfg dumpXML.

1-7ZCKOZ (a)

8.1

Fixed a configuration API defect in which the command tibrvcfg dumpXML omitted from its output the routing daemon parameters section of the rvsrd configuration.

1-7ZCKOZ (b)

8.1

Fixed a configuration API defect which prevented two routers in the same rvrd process from specifying an identical neighbor.

Issues Closed in Release 8.0

1-6R2N1W

8.0

Fixed a daemon defect that prevented clients from receiving advisory messages when the transport configuration specified multicast groups.



38 | Release Notes

1-8DZDCP1-80HUME

8.0

Fixed a daemon defect in which daemons would exit abruptly during the shutdown sequence.

1-81Q8IH

8.0

Fixed a daemon defect in which rvd would exit abruptly if it could not write to its log file.

1-7Z3LEV

8.0

Fixed a defect that could cause rvd memory growth when the daemon stopped using a service that other daemons continued to use. (Setting the -reliability parameter to zero could trigger this issue.)

1-80V9JT

8.0

Fixed a routing daemon defect in which rvrd routes with different path costs did not route _INBOX messages over the correct path.

1-7471D9

8.0

Fixed a defect in which daemons and API calls erroneously allowed service port numbers greater than 65535.

1-85L3ES

8.0

Fixed an rvrd defect in which thread deadlock resulted in unforwarded data and rapid memory growth.

1-74715M

8.0

Improved value checking for the routing daemon’s maximum backlog parameter.

1-83OJL2

8.0

Fixed a defect on 64-bit platforms in which an error configuring rvrd could cause abrupt exit while printing the error message.

1-8GOU1R

8.0

Fixed a defect in which messages with wildcard subjects erroneously matched inbox listeners.

1-8DZ6KX

8.0

Fixed a memory leak related to application processes automatically starting rvd.

1-8FNS9N

8.0

Fixed a memory growth defect related to distributed queues.

1-84MR37

8.0

Fixed a daemon memory growth defect associated with messages of length zero.



Closed Issues | 39

1-81R42F

8.0

Improved handling of illegal arguments when creating fault tolerance members in the tibrvj.jar and tibrvjsd.jar implementations of the Java API.

1-811JCQ

8.0

Fixed a Java defect in the tibrvnative.jar and tibrvnativesd.jar implementations. TibrvTransport.sendRequest() and TibrvCmTransport.sendRequest() threw an exception when the timeout expired without receiving a reply. They now correctly return null.

1-86NEKH

8.0

Fixed a Java defect in which the class TibrvIPPort did not support port values greater than 32767.

1-7Z3HG5

8.0

Fixed a defect in rvntsreg (on Windows platforms) in which the autostart (/a) flag had no effect for newly created services. (It did work properly for existing services.)

1-7AO9OU

8.0

Fixed a defect in which rvntscfg (on Windows platforms) did not exit properly.

1-86TFXC

8.0

Added safeguards to the C call tibrvQueue_TimedDispatch() so that UNIX signals that interrupt it cause bounded wait rather than indefinite wait (Solaris only).

1-838ZZH

8.0

Added safeguards to the C call tibrvTransport_Sendv() to avoid fast producer behavior.

1-7MY4DV

8.0

Fixed a numeric conversion defect in the C and C++ API libraries, in which converting a string value to a U64 (unsigned integer) incorrectly parsed the string as I64 (signed integer).

1-80RXLL

8.0

Fixed a C++ defect associated with the gcc 4.1.1 compiler.

1-7BBF61

8.0

Fixed a Java defect in the tibrvnative.jar and tibrvnativesd.jar implementations, in which TibrvMsg.add() and addField() did not throw exceptions upon detecting unrecognized data types.

1-8BSL8R

8.0

Fixed a defect in the Java fault tolerance API in which the callback TibrvFtMemberCallback.onFtAction() executed in an incorrect thread.



40 | Release Notes

1-86QYWA

8.0

Fixed a .NET library defect in which a listener callback method could run before the listener was completely initialized, resulting in an Invalid Event exception in the dispatcher thread.

1-7UYVFC

8.0

Fixed a .NET library defect associated with the method Queue.TimedDispatch(). When this method threw an exception, the stack trace contained incomplete information.

1-8EHV01

8.0

Fixed a .NET defect in which applications with many listeners could miss inbound messages.

1-8AAPP3

8.0

Fixed a .NET defect associated with reviewing the ledger of certified messages.

1-2YLJK1

8.0

Fixed a certified delivery defect in which the API did not set the sender field of DELIVERY.UNAVAILABLE advisory messages.

1-8BWSG1

8.0

Fixed a defect in the RVCMQ (distributed queue) library in which the scheduler would stop assigning tasks to itself. This symptom occurred only when the scheduler’s task capacity was greater than 1, and it assigned itself a long-running task (one that took 20–30 seconds or more to complete).

1-88CTJP

8.0

Fixed a defect in which distributed queue listeners incorrectly handled messages with subject > (wildcard).

1-8DP2YW

8.0

Fixed a defect in which the fault tolerance advisory message _RV.WARNING.RVFT.PARAM_MISMATCH reported erroneously as an ERROR advisory.

1-8CYQI8

8.0

Fixed a Java configuration API defect in which RvcacheInformation.getFaultToleranceState() erroneously returned 0 in all cases (whether the fault tolerance feature was enabled or disabled).

1-7T5ZGB

8.0

Fixed a defect in which the Java configuration API reported incorrect IP addresses for remote hosts when the daemon could not resolve the remote host name.

1-77D0KQ

8.0

Added safeguards to the Java configuration API to prevent adding strings (via XML) that are too long for the browser administration interface.



Closed Issues | 41

1-778KP3

8.0

Added safeguards to the Java configuration API to prevent setting numeric values that exceed maximum values.

1-72GRBQ

8.0

Fixed a defect in rva error reporting in the browser administration interface.

1-6YYHW1

8.0

Improved rvcache browser administration interface reporting behavior. Queries that would return more than 1000 messages now report an error instead.

1-89MTJK

8.0

Fixed an rvcache defect in which the browser administration interface displayed message fields incorrectly when the field name was the empty string.

1-6QHS3X

8.0

Fixed a defect in the rvrd browser administration interface in which routing daemons in idle mode could abruptly exit when users attempted to view the Local Networks page.

1-8J16E8

8.0

Fixed a security defect in rvrd and rvsrd browser administration interfaces in which subject names could be interpreted as HTTP strings.

1-777VGQ

8.0

Fixed a defect in the rva browser administration interface, associated with HTTP tunnel configuration.



42 | Release Notes

Known Issues

This section lists issues that are open in the named releases and provides workarounds where known.

Identified in Release Description

Known Issues as of Release 8.4.1

RV-3275 Building Samples

On Mac OS X, the supplied makefiles for Perl, C and C++ samples do not work.

Workaround

Edit the makefiles.

RV-3274 Uninstallation

On some platforms uninstalling the product does not remove the SSL libraries installed under TIBCO_HOME.

Workaround

You may remove those files manually.


8.4.1

RV-3163

Uninstallation

When several releases of Rendezvous software are installed in the same TIBCO_HOME directory, uninstalling one of them could delete files from the other installed versions.

Affects release 8.0 and later.

Workaround

Uninstall the damaged release, and reinstall it.


8.4.0

RV-3039

rvcache Browser Interface

Some browsers cannot toggle the state of rvcache.

Workaround

Connect to rvcache using another supported browser, such as Internet Explorer 9.


Known Issues | 43


8.3.2

RV-2730(previously RV-2884)

Linux Delivers Multicast Data to All UDP Ports

Consider two receivers, R1 and R2, which run on the same Linux host computer. R1 binds UDP service U1, and joins multicast listen group M1. Similarly, R2 binds UDP service U2, and joins multicast listen group M2.

A sending program, S, runs on any other host computer across a network. S sends messages over UDP service U1 to multicast send address M2. Receiver R2 receives these messages, even though one would expect its service (U2) to preclude this behavior.

The behavior is specific to Linux, and not specific to Rendezvous. Simple multicast socket programs produce the same behavior on Linux. For more information, see https://bugzilla.redhat.com/show_bug.cgi?id=231899.

Workaround

RV-3102 fixes this issue for for Linux kernels 2.6.31 and higher (for example, RHEL6).

For earlier Linux kernels, use this workaround: Use distinct multicast addresses to separate message streams (do not rely on UDP services to separate message streams). Do not reuse a same multicast group address on different UDP services.

Known Issues as of Release 8.3

8.3

RV-2131

(1-AKCFVD)

rvtrace Support

rvtrace requires a library that does not support the Windows 64-bit platform.

Workaround

To use rvtrace, install the Windows 32-bit package (which operates correctly on 64-bit platforms).

8.3

1-9XXRW9

Message Access after Java Dispose

After calling TibrvMsg.dispose to release a message, the Java methods TibrvMsg.getSendSubject() and TibrvMsg.getReplySubject() retrieve null rather than throwing an exception.

Workaround

None.



44 | Release Notes

8.3

1-AADQH3

AIX 6.1 rvd Does Not Receive Broadcast Data

This symptom results from an operating system defect in AIX 6.1. Disabling the socket option IP_MULTICAST_LOOP disables receipt of broadcast data.

Workaround

Use multicast instead of broadcast.

8.3

1-AWENF7

AIX 5.3 Setting LIBPATH is Incompatible with JVM

On AIX platforms (version 5.3 and later) setting the environment variable LIBPATH causes the Java Virtual Machine (JVM) to exit abruptly.

Workaround

Set the environment variable LD_LIBRARY_PATH instead. Do not set LIBPATH at all—not even to a null value.


8.2

1-A3OWRP

Secure Java Clients on HP-UX Itanium

On HP-UX IA64 platforms, Java secure clients can abruptly exit when attempting to connect to a secure daemon.

Workaround

None.


8.1

1-8SVGYY


• Release 8.1 RVDM communicates with managed daemons from both 8.1 and 8.0.




Known Issues | 45


8.0

1-8KAG2Z

1-8KW0FV

64-bit Secure Java Clients on HP-UX HPPA & HP-UX Itanium

Release 8.0 does not support 64-bit secure JNI clients on HP-UX HPPA and HP-UX Itanium platforms. (A secure Java client is a Rendezvous program that loads either of these two libraries tibrvnativesd.jar or libtibrvjsd.jar.) This issue does not affect other platforms, except as listed in this section.

Workaround

Run secure clients on HP-UX using the 32-bit JVM.

7.5, 8.0 64-bit Secure Java Clients on AIX

Releases 8.0 and 7.5 do not support 64-bit secure JNI clients on AIX platforms. (A secure Java client is a Rendezvous program that loads either of these two libraries tibrvnativesd.jar or libtibrvjsd.jar.) This issue does not affect other platforms, except as listed in this section.

Workaround

Run secure clients on AIX using the 32-bit JVM.

8.0

1-8IQTH3

Old rvtrace Lists Managed Daemon Packets as Bad

rvtrace from releases earlier than 8.0.0 cannot interpret packet headers from managed daemons on services that use subject maps. It tallies such packets as bad packets.

Workaround

Switch to a current version of rvtrace.

8.0

1-8LNZHQ

Host Status Messages From Managed RVDs

For managed RVDs, host status messages do not show the service or network fields except for the control channel service.

Workaround

None.

8.0

1-8LNZH7

RV Advisory Messages From Managed RVDs

Using “>” does not capture RV advisory messages from managed RVDs.

Workaround

Explicitly request the RV advisory messages with “_RV.>” or a subset of the subject name.



46 | Release Notes

8.0

1-8KWJMP

Compatibility with BusinessWorks, Designer, Hawk 4.7 and TRA 5.5.x

When Rendezvous 8.x, TIBCO Hawk® 4.7 (or older), TIBCO Designer™ and TIBCO BusinessWorks ™ coexist on the same host computer, an OpenSSL version mismatch prevents correct operation of Rendezvous activities within BusinessWorks processes running in the Designer debugger.

Rendezvous 8.x transports require a newer version of OpenSSL, while Hawk 4.7 supplies an older version. Installing BusinessWorks modifies a directory path in designer.tra, causing Rendezvous transports to use the wrong version of OpenSSL.

Workaround

In the file designer.tra, modify the variable tibco.env.CUSTOM_PATH. Add the directory rv_8x_home/bin to the value of this path variable, ensuring that it precedes the directory tibco_home/hawk/bin.

Issues Known from Earlier Releases (which still apply to the current release)

7.3 Multicast Issue in Linux Kernel on x86-64 Hardware

This issue affects Linux kernels earlier than 2.4.26, running on x86-64 hardware. These kernels exhibit a defect calculating checksums, which prevents the Rendezvous daemon from properly joining multicast groups. (Network broadcast is not affected.)

Workaround

Request the appropriate defect correction from your Linux vendor.

7.2 Daemon Autostart

On Solaris 2.8 platforms, in some situations, rvd does not start automatically. This behavior results from a bug in the Solaris implementation of the system call recv().

Workaround

Update Solaris 2.8 with the latest patches.

7.2 COM Library

The version of librvcom.dll included with release 7.2 does not work with IIS version 5.0 or version 5.1; though it is known to work with versions 4 and 6 of IIS. This effects OS versions on which these IIS versions run.

Workaround

Enable script debugging for the ASP.



Special Note for IBM i | 47

Special Note for IBM i

TIBCO Rendezvous does not support the following features on IBM i (formerly i5 and AS/400) platforms:

• PGM variants

• Secure daemons (rvsd and rvsrd)

• Secure daemon API calls

• RVDM


48 | Release Notes


Documents

TIBCO Rendezvous Release Notes · TIBCO Rendezvous Release Notes 2 | Release Notes New Features This section lists features and the release they were added to this product. Reference