TIBCO Web Messaging for TIBCO Enterprise Message … · |4 Release Notes TIBCO Web Messaging for...

1

TIBCO Web Messaging for TIBCO Enterprise Message Service™ Release Notes

TIBCO Web Messaging for TIBCO Enterprise Message Service™

Release Notes Software Release 3.5.13 January 2014

Important Information SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUN-DLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNC-TIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LI-CENSED 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 DIS-PLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN LI-CENSE.PDF) 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 DOCU-MENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE AC-CEPTANCE 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.

TIB, TIBCO, TIBCO Adapter, Predictive Business, Information Bus, The Power of Now, TIBCO ActiveMatrix Business-Works, TIBCO Web Messaging for TIBCO Enterprise Message Service, and TIBCO Enterprise Message Service are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries. EJB, Java EE, J2EE, and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsys-tems, Inc. 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 RE-ADME.TXT 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 PAR-TICULAR 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 CHANG-ES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.

2 | Release Notes


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 (C) 2014 - TIBCO Software Inc., ALL RIGHTS RESERVED.

TIBCO Software Inc. Confidential Information

Release Notes | 3


Release Notes

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

• Changes in Functionality

• Deprecated Features

• Migration and Compatibility

• Closed Issues

• Known Issues

4 | Release Notes


New Features

This section lists features in this product.

Release 3.5.13 There are no new features in this release.







Release Notes | 5


Release 3.5.0 The following are new features in this release.

• Reverse Connectivity. You can configure TIBCO Web Messaging for TIBCO Enterprise Message Service™ to initiate connectivity from inside the trusted enterprise network to the DMZ. This ability lets you close all inbound ports of your enterprise firewall for maximum security, while still allowing your clients to connect.

• Client libraries for building Objective-C clients. You can now use client libraries to connect iOS native Objective-C applications with TIBCO Web Messaging for TIBCO Enterprise Message Service™.

• Support for hybrid mobile clients. You can connect hybrid mobile applications using Apache Cordova with TIBCO Web Messaging for TIBCO Enterprise Message Service™. You can write applications using HTML5 and JavaScript, then deploy these applications natively to mobile devices such as iOS and Android.

• Offline notifications for Objective-C clients with Apple Push Notification Service (APNS). Your Objective-C clients can receive messages even when the application is not in the foreground on your iOS device.

• Support for durable subscriptions. TIBCO Web Messaging for TIBCO Enterprise Message Service™ clients can now receive messages sent while the subscriber is not connected. Durable subscriptions provide the flexibility and reliability of queues while allowing clients to send messages to many recipients.

• Support for JMS MapMessage. TIBCO Web Messaging for TIBCO Enterprise Message Service™ clients support JMS MapMessage, which can send a set of name-value pairs of different object types.

• Bandwidth Control. You can control the bandwidth rate of messages from TIBCO Enterprise Message Service™ to clients on a per-client basis for each service. You can also create tiered-level services with different maximum rates for traffic shaping or different service offerings to your users.


• Support for message selectors. TIBCO Web Messaging for TIBCO Enterprise Message Service™ clients can now filter the messages they wish to receive on a consumer.

• Embedded TIBCO Web Messaging for TIBCO Enterprise Message Service™. TIBCO Web Messaging for TIBCO Enterprise Message Service™ can now be embedded inside a Java process, allowing it to be shipped as part of another application. TIBCO Web Messaging for

6 | Release Notes


TIBCO Enterprise Message Service™ can be configured, started, and stopped via simple commands.

• Client and server performance enhancements. TIBCO Web Messaging for TIBCO Enterprise Message Service™ introduces improvements for optimized message processing, faster randomization, and lower memory usage, as well as client performance improvements for handling large messages.

• Single sign-on. This release incorporates a consistent server and client architecture for authenticating and authorizing user access to WebSocket. This feature builds on standard APIs such as JAAS, and provides a foundation for building login modules for services such as OAuth, Facebook, and more. It introduces new functionality for re-validating connections, and brings WebSocket to a level of enterprise support not available in the base technology.

• Support for RFC 6455. TIBCO Web Messaging for TIBCO Enterprise Message Service™ supports incoming and outgoing connections using the finalized WebSocket standard, RFC 6455.

• Support for OpenJDK. TIBCO Web Messaging for TIBCO Enterprise Message Service™ can now run on OpenJDK.




• Flash connectivity is improved. First time WebSocket connections for Adobe Flash Player clients are established more quickly. This feature also provides faster processing for secure connections and broadens support for self-signed certificates and client certificates (self-signed certificates that are imported into your browser).

• TIBCO Web Messaging for TIBCO Enterprise Message Service™ JMS Client Libraries for Microsoft .NET and Silverlight. You can build .NET and Silverlight JMS clients with TIBCO Web Messaging for TIBCO Enterprise Message Service™ client libraries. See How to Build Microsoft .NET and Silverlight Clients Using TIBCO Web Messaging for TIBCO Enterprise Message Service™ for more information.

Release Notes | 7


• Single DLL for .NET and Silverlight client development. You can build Microsoft .NET and Silverlight clients for TIBCO Web Messaging for TIBCO Enterprise Message Service™ using a single DLL, which is based on PCL (portable class libraries).

• Property substitution in the TIBCO Web Messaging for TIBCO Enterprise Message Service™ configuration file. You can specify default values for properties, which will be substituted when TIBCO Web Messaging for TIBCO Enterprise Message Service™ starts. You can replace any values in the TIBCO Web Messaging for TIBCO Enterprise Message Service™ configuration file with a property. Starting TIBCO Web Messaging for TIBCO Enterprise Message Service™ replaces all instances of property with the value you specify at the top of the TIBCO Web Messaging for TIBCO Enterprise Message Service™ configuration file. Additionally, you can supersede property default values by using an environment variable when starting TIBCO Web Messaging for TIBCO Enterprise Message Service™.

• New basic challenge handler for the TIBCO Web Messaging for TIBCO Enterprise Message Service™ Java and Flash JMS clients. When securing your Java and Flash clients, you can now use a basic challenge handler for the client login credentials. For more information see the How to Build Java Clients Using TIBCO Web Messaging for TIBCO Enterprise Message Service™ and How to Build Flash Clients Using TIBCO Web Messaging for TIBCO Enterprise Message Service™ documents.


• Integration with Java Message Service (JMS): Extend the reach of TIBCO EMS to the Web based on standard JMS APIs.

• Full-duplex, bidirectional communication: Since TIBCO Web Messaging for TIBCO Enterprise Message Service™ is based on WebSockets, both the server and client can send and receive data simultaneously. This behavior is in contrast to polling or long-polling solutions, which rely on the client to regularly poll the server for data.

• Clustering, high availability, and disaster recovery support: TIBCO Web Messaging for TIBCO Enterprise Message Service™ supports high availability in enterprise deployments through clustering and load balancing of TIBCO Web Messaging for TIBCO Enterprise Message Service™ servers.

• Connection and subscription offloading: Increase the scalability of your architecture by using a single connection from TIBCO Web Messaging for TIBCO Enterprise Message Service™, while allowing TIBCO Web Messaging for TIBCO Enterprise Message Service™ to handle a massive number of concurrent client connections.

• JMS authentication and authorization: Authenticate from a client with TIBCO Web Messaging for TIBCO Enterprise Message Service™ for secure access. Additionally, authorize each operation they can perform, such as the ability to subscribe to a topic.

8 | Release Notes


• Automatically reconnect dropped client connections: Clients automatically attempt to reconnect after being disconnected, and resume processing messages.

• TIBCO Web Messaging for TIBCO Enterprise Message Service™ failover: When TIBCO Web Messaging for TIBCO Enterprise Message Service™ restarts, clients automatically reconnect and resume message processing.

• Buffer slow consumer messages: Buffer messages for slow consumers so that other clients continue processing at full speed.

• Enterprise-level security and Single Sign-On over the Web: Use SPNEGO-based Kerberos authentication using WebSocket over the Web. You can integrate Kerberos and TIBCO Web Messaging for TIBCO Enterprise Message Service™ with your existing infrastructure to provide Single Sign-On capability.

• Suitable for the DMZ to protect trusted systems: You want to be able share the data from your back-end systems and applications over the Web without exposing them to everyone on the Internet. Place TIBCO Web Messaging for TIBCO Enterprise Message Service™ in the DMZ to act as a front-line access point for those back-end systems, which can reside safely in the trusted network.

• JMX management and monitoring: Manage and monitor TIBCO Web Messaging for TIBCO Enterprise Message Service™ connections and activity using JMX.

• Publish and subscribe messaging (topics): Enable clients to publish and subscribe to topics that broadcast messages to many consumers.

• Point-to-point messaging (queues): Enable clients to send and receive from queues.

• Send JMS text and binary messages: Send JMS text and binary messages over a WebSocket connection.

• Asynchronous message processing: By using message listeners, enable asynchronous message processing per destination or at the session level. Messages are delivered as they are received.

• Synchronous message processing: Queue messages until they are requested by the client by using receive().

• Multiple acknowledgement modes: Configure sessions for auto-acknowledgement or client-acknowledgement.

• Start and stop flow control: Stop and start the flow of messages for each client connection.

• Support for priority, expiration and delivery modes: Enable messages to be sent or received with options for priority, expiration, and delivery mode (persistent or non-persistent).

• Asynchronous request-response: Use asynchronous request-response processing with correlation IDs and reply-to headers.

Release Notes | 9


• Custom message properties: Send and receive messages with custom properties, such as for sending additional information or metadata with the message.

• Client-initiated transactions: Initiate transactions with JMS clients. Transactions help ensure all messages are processed atomically.

10 | Release Notes


Changes in Functionality

This section lists changes in functionality since the last major release of this product.

Release 3.5.13 There are no changes in functionality in this release.







Release Notes | 11


Release 3.5.0 • Reverse Connectivity. You can configure TIBCO Web Messaging for TIBCO Enterprise

Message Service™ to initiatiate connectivity from inside the trusted enterprise network to the DMZ. This ability lets you close all inbound ports of your enterprise firewall for maximum security, while still allowing your clients to connect.

• Client libraries for building Objective-C clients. You can now use client libraries to connect iOS native Objective-C applications with TIBCO Web Messaging for TIBCO Enterprise Message Service™.

• Support for hybrid mobile clients. You can connect hybrid mobile applications using Apache Cordova with TIBCO Web Messaging for TIBCO Enterprise Message Service™. You can write applications using HTML5 and JavaScript, then deploy these applications natively to mobile devices such as iOS and Android.

• Offline notifications for Objective-C clients with Apple Push Notification Service (APNS). Your Objective-C clients can receive messages even when the application is not in the foreground on your iOS device.

• Support for durable subscriptions. TIBCO Web Messaging for TIBCO Enterprise Message Service™ clients can now receive messages sent while the subscriber is not connected. Durable subscriptions provide the flexibility and reliability of queues while allowing clients to send messages to many recipients.

• Support for JMS MapMessage. TIBCO Web Messaging for TIBCO Enterprise Message Service™ clients support JMS MapMessage, which can send a set of name-value pairs of different object types.

• Bandwidth Control. You can control the bandwidth rate of messages from TIBCO Enterprise Message Service™ to clients on a per-client basis for each service. You can also create tiered-level services with different maximum rates for traffic shaping or different service offerings to your users.

Release 3.3.0 • Support for message selectors

Clients can now filter the messages they wish to receive on a consumer.

• Embedded TIBCO Web Messaging for TIBCO Enterprise Message Service™.

TIBCO Web Messaging for TIBCO Enterprise Message Service™ can now be embedded inside a Java process, allowing it to be shipped as part of another application. TIBCO Web Messaging for TIBCO Enterprise Message Service™ can be configured, started, and stopped via simple commands.

• Single sign-on support

12 | Release Notes


TIBCO Web Messaging for TIBCO Enterprise Message Service™ now has consistent server and client architecture for authenticating and authorizing user access to WebSocket. This feature builds on standard APIs such as JAAS, and provides a foundation for building login modules for services such as OAuth, Facebook, and more. It introduces new functionality for re-validating connections, and brings WebSocket to a level of enterprise support not available in the base technology.

• Support for RFC 6455

TIBCO Web Messaging for TIBCO Enterprise Message Service™ supports incoming and outgoing connections using the finalized WebSocket standard, RFC 6455.

• Support for OpenJDK

TIBCO Web Messaging for TIBCO Enterprise Message Service™ can now run on OpenJDK.

• Namespace Changes

The namespace declarations have changed in this release. Note the use of .com in xmlns.kaazing.com in the namespace declarations. If you used a previous version (3.2.x or earlier) of TIBCO Web Messaging for TIBCO Enterprise Message Service™, then starting a later version, such as 3.3.0, automatically generates a new configuration file called "gateway-config.xml.new" that uses the new namespace. TIBCO Web Messaging for TIBCO Enterprise Message Service™ automatically uses this new configuration file, unless you revert to using your old file. For more information on starting TIBCO Web Messaging for TIBCO Enterprise Message Service™ using a specific gateway-config.xml file, see the “For Administrators” documentation. The namespace is declared in the gateway-config.xml file as follows:

<gateway-config xmlns="http://xmlns.kaazing.com/2012/03/gateway">



Release 3.2.3 • Support for the htm and vtt MIME types

Updated the TIBCO Web Messaging for TIBCO Enterprise Message Service™ to support the htm and vtt MIME types.

Release Notes | 13


• Flash demo challenge handlers

Updated the TIBCO Web Messaging for TIBCO Enterprise Message Service™ Flash demonstration to use the new API for challenge handlers.

• Downstream data processed in bursts

Downstream data is now processed in bursts on WebKit and Chromium-based mobile browsers.

• Partitioned Flash client libraries

Partitioned the Flash client libraries (available in the GATEWAY_HOME/lib/client/flash directory) into three separate Flash client libraries, and decreasing the download size.

• com.kaazing.gateway.client.flash.core.swc is for general functionality such as WebSocket connectivity, Single Sign-On, Server-Sent Events, and so on.

• com.kaazing.gateway.client.flash.kerberos.swc adds Single Single-On specifically when using Kerberos.

• com.kaazing.gateway.client.flash.compat.swc is for backward compatibility and is used for environments that use Single Sign-On or Kerberos interfaces in previous releases.



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.

Release 3.5.13 No features are deprecated in this release.






Release Notes | 15




Release 3.3.0 The following features are deprecated in this release:

• Authorization Constraints: The auth-constraint element from the TIBCO Web Messaging for TIBCO Enterprise Message Service™ configuration has been deprecated in 3.3. Use authorization-constraint instead. See the "Error Using the auth-constraint Element" section in the For Administrators topics for more information.

• Network Address Mapping: The <network> and <address-mapping> elements are now deprecated. Use protocol.bind instead.

• session Element: The session element and its properties are now deprecated, including:

o service-domain

o authentication-scheme

o authentication-connect

o realm-name

o encryption-key-alias

o inactivity-timeout

See the session section in the Administrator's Guide for a description of these changes to the TIBCO Web Messaging for TIBCO Enterprise Message Service™ configuration.



16 | Release Notes





Release Notes | 17


Migration and Compatibility

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

Release 3.5.13 There are no migration procedures or compatibility issues in this release.







18 | Release Notes



Release 3.3.0 Namespace Changes

The namespace declarations have changed in this release. Note the use of .com in xmlns.kaazing.com in the namespace declarations. If you used a previous version (3.2.x or earlier) of TIBCO Web Messaging for TIBCO Enterprise Message Service™, then starting a later version, such as 3.3.0, automatically generates a new configuration file called "gateway-config.xml.new" that uses the new namespace. TIBCO Web Messaging for TIBCO Enterprise Message Service™ automatically uses this new configuration file, unless you revert to using your old file. For more information on starting TIBCO Web Messaging for TIBCO Enterprise Message Service™ using a specific gateway-config.xml file, see the For Administrators topics. The namespace is declared in gateway-config.xml file as follows:

<gateway-config xmlns="http://xmlns.kaazing.com/2012/03/gateway">






Release Notes | 19


Closed Issues

The table in this section lists issues that were closed in the named releases.

Closed in Release

Key Summary

3.5.13 KG-10178 Fixed an issue where clients would always balance to the same clus-ter member after failover, potentially causing unbalanced loads.

3.5.13 KG-10144 Fixed an issue where, under certain conditions, not all pending queue messages were re-delivered.

3.5.13 KG-10067 Fixed an issue where Objective-C (iOS) clients may error when changing the underlying network, such as transitioning from WiFi to 3G.

3.5.13 KG-10043 Fixed an issue where authentication sometimes failed on Objective-C (iOS) clients.

3.5.12 KG-9786 Fixed an issue where an exception was not properly logged while creating a APNS notifying-consumer

3.5.12 KG-9942, KG-9898

Fixed an issue in the JavaScript JMS client that, when running in Mi-crosoft Internet Explorer 8, failed to connect when running with cer-tain more restrictive security settings.

20 | Release Notes


3.5.12 KG-9710 Fixed an issue where running the JavaScript JMS client within a Google Web Toolkit application could not start when running in De-velopment Mode.

3.5.12 KG-9856 Fixed an issue with the JavaScript JMS demo running in Microsoft Internet Explorer 11.

3.5.12 KG-9803, KG-9805

Fixed an issue in the Flash JMS client while sending messages where to TIBCO Web Messaging for TIBCO Enterprise Message Service™ deferred or failed to deliver "Message sent from client may not have been delivered" exceptions.

3.5.12 KG-9669 Fixed an issue where the Internal Gateway and client would some-times fail to reconnect to the DMZ Gateway under repeated intermit-tent connectivity conditions.

3.5.12 KG-9457 Improved memory usage with certain Enterprise Shield™ configura-tions using SOCKS over SSL connections.

3.5.12 KG-9430, KG-9429, KG-9428, KG-9427

Fixed an issue where some clients sent an incorrect value for JMS Message time-to-live.

3.5.12 KG-9711, KG-9409, KG-9429, KG-9428, KG-9427

Fixed issues with durable subscriptions where server reported the error "Failed to create durable subscriber" due to lost network con-nection. Contact TIBCO Support for details on configuration in this release.

3.5.12 KG-9370 Updated the Objective-C (iOS) demo to make it easier to include APNs integration.

Release Notes | 21


3.5.12 KG-9332 Fixed an issue where .NET/Silverlight clients did not detect a lost connection to TIBCO Web Messaging for TIBCO Enterprise Message Service™. Contact TIBCO Support for details on configuration.

3.5.12 KG-8940 Clarified the descriptions of prepared.connection count and connec-tion.count in the documentation. See the STOMP services topic for more information.

3.5.12 KG-8841 Fixed an issue where the JMSAuthorizationFactory policy canReceiveFromQueue() prevented a rejected message from be-ing delivered to other queues.

3.5.12 KG-8748 Objective-C (iOS) clients no longer accept self-signed certificates. Self-signed certificates must be signed by a trusted Certificate Au-thority in the keychain.

3.5.12 KG-8699 TIBCO Web Messaging for TIBCO Enterprise Message Service™ gracefully closes the connection when TIBCO EMS throws an abnor-mal exception after the client fails to acknowledge a message.

3.5.12 KG-8473 Fixed an issue for Objective-C (iOS) clients where JMSTimeStamp values were incorrect.

3.5.11 KG-8670 Fixed an issue where clients using secure non-native WebSocket con-nectivity with authentication or load balancing enabled may fail to connect.

3.5.10 KG-8608 Fixed an issue where Session.Recover did not redeliver unacknowl-edged messages.

3.5.10 KG-8443, KG-8518, KG-8519, KG-8520, and KG-8527

Fixed an issue where fatal errors reported by TIBCO Web Messaging for TIBCO Enterprise Message Service™ did not completely close connections in clients (JavaScript, Java, .NET/Silverlight, Objective-C (iOS) and Flash).

22 | Release Notes


3.5.10 KG-8436 Fixed an issue in the TIBCO Web Messaging for TIBCO Enterprise Message Service (TM) gateway.start script so that the correct EMS 8.0 client library JAR file is included on the start up classpath.

3.5.10 KG-8144 Fixed an issue where the Flash client did not detect a lost connection to TIBCO Web Messaging for TIBCO Enterprise Message Service™. Contact TIBCO Support for details on configuration.

3.5.8 KG-7656 Fixed an issue in the Objective-C (iOS) clients where client certificates were not honored when using ssl.verify-client.

3.5.8 KG-7725 Fixed an issue where a cluster member could time out when a subin-terface for the instance was added.

3.5.8 KG-7235 Fixed an issue where the JavaScript client running in Internet Explor-er 9 could stop receiving messages after 10 minutes.

3.5.8 KG-7128 Fixed an issue in the Objective-C (iOS) client where subscribing or unsubscribing after a disconnect from TIBCO Web Messaging for TIBCO Enterprise Message Service™ threw the error "Unrecognized subscription id" upon reconnect

3.5.6 KG-7450 Eliminated duplicate reverse connection retries from the internal TIBCO Web Messaging for TIBCO Enterprise Message Service™ when the DMZ TIBCO Web Messaging for TIBCO Enterprise Mes-sage Service™ goes down.

3.5.6 KG-7440 Fixed an issue where the Internal TIBCO Web Messaging for TIBCO Enterprise Message Service™ created reverse connections to the DMZ TIBCO Web Messaging for TIBCO Enterprise Message Ser-vice™ when restarted.

3.5.6 KG-7436 Improved logging for SOCKS exceptions for reverse connections.

Release Notes | 23


3.5.6 KG-7434 Fixed an issue where each reverse connection from the internal in-stance of TIBCO Web Messaging for TIBCO Enterprise Message Ser-vice™ established more TCP connections to the DMZ instance than expected when using RFC 6455 between instances of TIBCO Web Messaging for TIBCO Enterprise Message Service™.

3.5.6 KG-7393 Added a new socks.timeout connect option for forward and re-verse connections. If the SOCKS connection does not succeed within the period specified by this option, the failed attempt is propagated properly back to the client. To set the SOCKS timeout period, config-ure socks.timeout on the DMZ TIBCO Web Messaging for TIBCO Enterprise Message Service™ (recommended value: 5 seconds). In addition to setting the new connect option, ensure that you set the maximum.recovery.interval, prepared.connection.count, and socks.retry.maximum.interval properties to positive val-ues; the recommended value for socks.retry.maximum.interval is 1-5 seconds. See the socks.timeout description in the Service Reference documentation topic for more information. Also fixed an issue where reverse connec-tions failed due to TIBCO Web Messaging for TIBCO Enterprise Mes-sage Service™ unbinding the reverse connection port.

3.5.6 KG-7400 Fixed an issue where client did not reconnect properly in all cases when an internal instance of TIBCO Web Messaging for TIBCO En-terprise Message Service™ in a distributed DMZ architecture went offline.

3.5.6 KG-7391 Added the ability to detect a half-closed connection over WebSocket, which allows the detection of silent network failure over WebSocket between instances of TIBCO Web Messaging for TIBCO Enterprise Message Service™. WebSocket can be used as a protocol over SOCKS for forward and reverse connectivity to detect a network failure be-tween the DMZ instance and inner instance of TIBCO Web Messag-ing for TIBCO Enterprise Message Service™. To detect a half-closed connection over WebSocket, set the system property com.kaazing.gateway.transport.ws.INACTIVITY_TIMEOUT to a time value (in seconds) such as 30 to enable pings and pongs over the WebSocket connection.

3.5.6 KG-7318 Improved performance by cleaning up background threads from re-verse connections.

24 | Release Notes


3.5.6 KG-7116, KG-7109, KG-7098

Fixed an issue in the TIBCO Web Messaging for TIBCO Enterprise Message Service™ Javascript, Flash, and .NET clients where sub-scribing to a destination or unsubscribing from a destination after the connection was dropped caused TIBCO Web Messaging for TIBCO Enterprise Message Service™ to throw an error upon reconnect.

3.5.6 KG-6552 Fixed an issue in the TIBCO Web Messaging for TIBCO Enterprise Message Service™ Java, JavaScript, .NET, Flash, and iOS clients where the client replayed subscriptions on temporary destinations when a dropped connection was restored.

3.5.6 KG-7196 Fixed an issue with the TIBCO Web Messaging for TIBCO Enterprise Message Service™ Flash client library was incompatible with earlier versions of the client when using Kerberos for authentication for ticket sizes 8K or larger.

3.5.6 KG-7003 and KG-7116

Fixed an issue in the TIBCO Web Messaging for TIBCO Enterprise Message Service™ JavaScript, Java, .NET, and Flash client where subscribing or unsubscribing after a disconnect from TIBCO Web Messaging for TIBCO Enterprise Message Service™ threw the error "Unrecognized subscription id" upon reconnect.

3.5.6 KG-6994 Fixed an issue with the TIBCO Web Messaging for TIBCO Enterprise Message Service™ Java client where subscribing after a disconnect from TIBCO Web Messaging for TIBCO Enterprise Message Ser-vice™ threw the error "StompException: Gateway Reported Error: Duplicate subscription id" upon reconnect.

3.5.6 KG-6187, KG-6075, KG-6074, KG-6073, and KG-6053

Fixed an issue where TIBCO Web Messaging for TIBCO Enterprise Message Service™ clients appeared to send messages to a closed message producer; instead, an exception now correctly displays when attempting to send a message to a closed producer.

3.5.6 KG-7083 Fixed an issue where a Java applet failed to establish a secure Web-Socket connection.

3.5.6 KG-6176 Fixed an issue where the Java client would sometimes disconnect when using emulated WebSocket with some buffering proxies.

Release Notes | 25


3.5.6 KG-6720 Fixed an issue where the startup script for a cluster member would fail on the hostname when started from Amazon EC2 Virtual Private Cloud (Amazon VPC).

3.5.6 KG-6745 Fixed an issue where an exception from the Microsoft Internet Ex-plorer 10 console on Windows 8 displayed when disconnecting.

3.5.3 KG-6761 Fixed an issue in the iOS (Objective-C) demo where loss of connectiv-ity during the sending of a message threw an uncaught exception, causing the application to crash.

3.5.3 KG-6552 Fixed an issue where an iOS (Objective-C) client attempted to resub-scribe to temporary destinations upon reconnect.

3.5.0 KG-5706 Fixed an issue where the wss.bind accept option in the configura-tion file prevented TIBCO Web Messaging for TIBCO Enterprise Message Service™ from starting when the hostname could not be resolved.

3.5.0 KG-1659 Fixed a known issue where closing and re-creating a consumer on a temporary destination, replies to that temporary destination could fail.

3.2.7 KG-3491 Fixed an issue where messages originating from external sources with empty string header values could cause the exception: Proto-colCodecException: Missing header value.

3.2.7 KG-3411 TIBCO Web Messaging for TIBCO Enterprise Message Service™ now allows text messages containing null byte characters in the message body. However, due to a known issue with Adobe Flash/Actionscript, Flash clients do not currently support messages containing null characters. See http://help.adobe.com/en_US/AS2LCR/Flash_10.0/help.html?content=00000334.htm for more information.

26 | Release Notes


3.2.7 KG-3191 Prevented a Duplicate subscription id error in clients when subscribing to a temporary topic immediately after a client discon-nect.

3.2.7 KG-3266 Added a description for maximum.pending.bytes to the Adminis-trator's Guide.

3.2.7 KG-3028 Prevented a GenericException when messages are sent to a tem-porary topic with a consumer already closed.

3.2.7 KG-2296 Added documentation for a Security-Ticket Protected Gateway to the Administrator's Guide.

3.2.7 KG-2409 Improved the document How to Build Java Clients Using TIBCO Web Messaging for TIBCO Enterprise Message Service™ for sending messag-es.

3.2.7 KG-2410 Added a note to the document How to Build Java Clients Using TIBCO Web Messaging for TIBCO Enterprise Message Service™ to note the re-quirement of a JMS API JAR.

3.2.7 KG-1929 Prevented an ArrayIndexOutOfBounds exception in the server log when a client remains connected to a TIBCO Web Messaging for TIBCO Enterprise Message Service™ that has lost connection to its message broker.

3.2.7 KG-2374 Fixed a known issue to ensure the ability for the Flash client to con-nect to TIBCO Web Messaging for TIBCO Enterprise Message Ser-vice™ when using WebSocket Secure (WSS) on Google Chrome on Sun/Oracle Java 6 Update 29 or higher.

3.2.7 KG-2443 Fixed an issue that could prevent a Flash client from connecting with a Kerberos-protected service.

Release Notes | 27


3.2.7 KG-1714 Fixed an issue that could prevent cross-origin communications from file-based pages, likely to be seen in mobile embedded runtimes.

3.2.7 KG-3514 Adjusted cross-origin constraint handling based on new origin head-er behaviors sent from the Flash runtime.

3.2.7 KG-3159 Fixed an issue where a "ja-va.lang.IllegalArgumentException: message is empty. Forgot to call flip()?" error could occur in the server when using Flash clients.

3.2.7 KG-3160 Fixed an issue where a ClassCastException "SimpleBuffer cannot be cast to com.kaazing.gateway.server.transport.wsr.RtmpMessage" could occur during heavy load of Flash clients.

3.2.7 KG-3161 Fixed an issue where a NullPointerException in com.kaazing.gateway.server.transport.wsr.WsrAcceptor$1.doMessageReceived could occur during heavy load of Flash clients.

3.2.7 KG-2648 Fixed an issue where a java.nio.BufferUnderflowException could cause unwanted client logouts.

3.2.7 KG-2671 Improved the reliability of emulated WebSocket connections under heavy load.

3.2.7 KG-2651 Fixed an issue where a WebSocket connection could be closed by the server when sending high-volume, high speed data stream over emu-lated connections.

3.2.7 KG-3183 Reduced excessive amounts of logging on the server, which could occur when connecting with Flash clients.

28 | Release Notes


3.2.7 KG-2638 Improved the memory usage of emulated WebSockets on Google Chrome during heavy load.

3.2.7 KG-2649 Enabled the JDK version check to be bypassed by using the -DbypassPlatformCheck system property.

3.2.7 KG-2929 Updated the TIBCO Web Messaging for TIBCO Enterprise Message Service™ start batch files and scripts to dump the heap memory au-tomatically during an OutOfMemoryError.

3.2.7 KG-3151 Improved the description of JMX configuration in the document How to Manage TIBCO Web Messaging for TIBCO Enterprise Message Ser-vice™.

3.2.7 KG-2511 Fixed an issue where some WebSocket connections received slower downstream data delivery after reconnects.

3.2.7 KG-2554 Improved the consistency of downstream throughput in emulated JavaScript WebSocket connections.

3.2.7 KG-2296 Updated usage information for the authentication-connect property in the Security Guide and Administrator's Guide.

3.2.5 KG-2012 Fixed an issue where the Flash JMS demo occasionally caused an ex-ception.

3.2.5 KG-1965 Exceptions during TIBCO Web Messaging for TIBCO Enterprise Message Service™ startup are now written to the TIBCO Web Mes-saging for TIBCO Enterprise Message Service™ log instead of sys-tem.err.

Release Notes | 29


3.2.5 KG-1944 Fixed a race condition that might occasionally result in failure to send a reply message to the TemporaryQueue or TemporaryTopic named in the JMSReplyTo property of a received message.

3.2.5 KG-1939 Fixed a resource and memory leak that may occur when using mes-sages with the JMSReplyTo property set to a TemporaryQueue or TemporaryTopic.

3.2.5 (KG-1935, KG-1949, and KG-1831)

Fixed connectivity issues with the Flash client when used with Mi-crosoft Internet Explorer.

3.2.5 KG-1880 Fixed an issue in the JavaScript JMS client where if the client sub-scribed to a queue with more than 40 outstanding messages, the server returned multiple exceptions.

3.2.5 KG-1868 Fixed an issue where messages exceeding the number defined by the optional maximum.pending.acknowledgements property on the stomp.jms service were neither delivered to the client nor acknowl-edged, and resulted in a terminated connection between the client and TIBCO Web Messaging for TIBCO Enterprise Message Service™.

3.2.5 KG-1805 Fixed an issue where unacknowledged queue messages were not be-ing redelivered and caused TIBCO EMS to redeliver messages only when the JMS session on which the messages were received was closed.

3.2.5 KG-1739 Removed references to PasswordAuthentication from the ActionScript API documentation as this is no longer necessary. See the "Securing Flash JMS Clients" section in How to Build Flash Clients Using TIBCO Web Messaging for TIBCO Enterprise Message Service™ for information on using a login handler with Flash JMS clients.

3.2.3 KG-1842 Fixed an issue where Adobe Flash clients displayed the Unhandled AsyncErrorEvent: Argument count mismatch when TIBCO Web Messaging for TIBCO Enterprise Message Service™ abruptly disconnected while processing in-flight messages.

30 | Release Notes


3.2.3 KG-1833 Fixed an issue that caused the error StompConnectionFactory is undefined in Microsoft Internet Explorer 8. Similar errors may have appeared in other browsers. The issue was caused when the required JMS library scripts were not fully loaded before the application code was executed.

3.2.3 KG-1803 Fixed an issue where sending a reply to a temporary queue (or topic) that was specified in the JMSReplyTo header of a received message would fail in a configuration with TIBCO Web Messaging for TIBCO Enterprise Message Service™ and TIBCO EMS.

3.2.3 KG-1785 Fixed an issue where the Java minimum version detection prevented TIBCO Web Messaging for TIBCO Enterprise Message Service™ from running on Java 7.

3.2.3 KG-1758 Fixed a connection leak that occurred only when using Microsoft Internet Explorer 6 and 7 to ensure the TIBCO Web Messaging for TIBCO Enterprise Message Service™ proxy service closes down the back-end connection when the client disconnects.

3.2.3 KG-1730 Fixed an issue in which the Java Echo Demo could not connect properly if Application Basic was used for authentication.

3.2.3 KG-1738 Fixed an issue that occurred where TIBCO Web Messaging for TIBCO Enterprise Message Service™ did not allow Microsoft Silverlight clients to establish an Authorization header even when the client was configured as Authorized with cross-site constraints.

3.2.3 KG-1724

KG-1723

Fixed issues that occurred only with Microsoft Internet Explorer 8 and 9 to ensure the onClose method is called when TIBCO Web Messaging for TIBCO Enterprise Message Service™ goes down.

Release Notes | 31


3.2.3 KG-1719 Fixed inaccuracies in the documentation of the stomp.proxy service.

3.2.3 KG-1704 Fixed an issue where the WebSocket connection for Flash JMS clients would close if the user authentication dialog was not completed within five seconds.

3.2.3 KG-1694 Fixed an issue where the "Subscription not found for ID" GenericException was returned due to incorrectly processing ACK receipts.

3.2.3 KG-1693 Fixed an issue in the TIBCO Web Messaging for TIBCO Enterprise Message Service™ startup so that it now returns an exception and ceases the startup when configured with an unresolvable hostname.

3.2.3 KG-1685 Fixed an issue where NullPointerExceptions could occur in TIBCO Web Messaging for TIBCO Enterprise Message Service™ if ssl.encryption was disabled.

3.2.3 KG-1666 Fixed a problem that prevented connections to TIBCO Web Messaging for TIBCO Enterprise Message Service™ after redirection.

3.2.3 KG-1653 Fixed an issue where multiple argument_addingduplicate exceptions are returned when Microsoft .NET clients try to reconnect to TIBCO Web Messaging for TIBCO Enterprise Message Service™.

32 | Release Notes


3.2.3 KG-1647 Fixed an issue in the Java JMS client where calling the javax.jms.TextMessage.setText() method returned the message "Subscription not found for ID."

3.2.3 KG-1547 Fixed an issue when a single Java client made multiple attempts to simultaneously connect to TIBCO Web Messaging for TIBCO Enterprise Message Service™.

3.2.3 KG-1486 Changed the ErrorEventArgs parameter to the Exception type to fix an issue with Microsoft Silverlight cross-origin failures.

3.2.3 KG-1338 Fixed an issue so that the WebSocket readyState attribute correctly indicates that a connection cannot be established when it is passed an invalid URL.

3.1.2 KG-1469 Fixed an HTTP transport issue when resolving URIs.

Release Notes | 33


Known Issues

The table in this section lists known issues in this release.

Key Summary/Workaround

KG-8662 Summary In accordance with the W3C WebSocket API standard at http://www.w3.org/TR/websockets/, applications may not connect from secure source origin to insecure target origin.

Workaround Per the specification, do not configure clients to connect from a secure source origin to an insecure target origin.

KG-7114 Summary When using the TIBCO Web Messaging for TIBCO Enterprise Message Service™ Silverlight client libraries on Safari for Microsoft Windows, the client may not work properly due to system incompatibility issues.

Workaround Check the Microsoft Silverlight compatibility chart at http://www.microsoft.com/getsilverlight/Get-Started/Install/Default.aspx for more information.

KG-7001 Summary Self-signed certificates are not currently supported on all client platforms and browsers, and thus may cause secure WebSocket connections to fail.

Workaround Use a trusted certificate. See the documentation topic “Secure TIBCO Web Messaging for TIBCO Enterprise Message Service™ Using Trusted Certificates” for more information.

KG-5846 Summary The iOS client application may crash after a period of time due to memory limitations when running multiple connections at high message rates.

Workaround Use a single connection for the iOS client application.

KG-4049 Summary When using JRE 7 in a browser on Windows, Java applets secured by HTTPS may fail to load with an "invalid JAR file" error message, and connections to WebSocket services secured by WebSocket secure may not

34 | Release Notes


succeed. This issue is caused by a bug in Java (see Oracle bug 7176846 for more information).

Workaround To ensure that secured Java applets running JRE 7 in a browser can load via HTTPS and connect to secured services over WebSocket secure (wss), open your Java Control panel, navigate to the Security/General section, then click the Advanced tab. On the Advanced tab, enable the "Use TLS 1.0," "Use TLS 1.1," and "Use TLS 1.2" options.

KG-1851 Summary For any .NET application that uses more than one connection at a time, the .NET 4.0 Framework has a maximum connection limit of two per domain, similar to the browser limitation.

Workaround Because .NET client may use multiple connections simultaneously, you must either ensure that any connection is closed before opening another connection, or increase the connection limit on the application by updating the maxconnection attribute in the app.exe.config file.

See MSDN for more information about the application configuration file and its attributes and elements: http://msdn.microsoft.com/en-us/library/ms229689.aspx and http://msdn.microsoft.com/en-us/library/fb6y0fyc.aspx.

KG-1850 Summary The .NET Client initial WebSocket connection request may be delayed by several seconds due to automatic proxy detection in Microsoft Windows.

Workaround To address this, if using Internet Explorer, choose Options > Connections tab > LAN Settings. Clear the Automatically Detect Settings checkbox and, if necessary, specify the proxy settings. In .NET applications, you can bypass the proxy settings by including the line System.Net.WebRequest.DefaultWebProxy = null; before the client initiates the WebSocket connection. If your application requires a proxy, change the null value in this line to the default proxy or follow the instructions located here: http://msdn.microsoft.com/en-us/library/dkwyc043.aspx.

KG-1849 Summary The TIBCO Web Messaging for TIBCO Enterprise Message Service™ client libraries fire events on multiple threads for better performance. Therefore, events are delivered on a thread other than the UI thread. This requires you to explicitly transfer execution to the UI thread when updating the UI from dispatched events. This technique varies slightly between Silverlight and .NET Framework applications, as described in How to Build Microsoft Silverlight and .NET Clients Using TIBCO Web Messaging for TIBCO Enterprise Message Service™.

Release Notes | 35


Workaround In TIBCO Web Messaging for TIBCO Enterprise Message Service™ clients for Microsoft Silverlight, you must call StompConnectionFactory() on the Application UI thread, and call the createConnection() method on a separate thread. See the file GATEWAY_HOME/demo/silverlight/src/jms/Page.xaml.cs for an example.

KG-1840 Summary Messages delivered to sessions in the TIBCO Web Messaging for TIBCO Enterprise Message Service™ client library for Microsoft .NET and Silverlight are delivered using threads from the application ThreadPool, and using the SetMinThreads() method to manage the number of threads. The SetMinThreads() method can be tuned depending on the application. When multiple JMS sessions or connections are used, set the value of SetMinThreads() to ensure that connections are not starved while waiting to read messages from the network or deliver messages to consumers. If the thread count is set too low, then the messages will be queued until a thread is available, resulting in slower application performance and potentially large memory consumption.

Workaround Set the SetMinThreads() method to 2 times the number of JMS connections plus an additional thread per session beyond the base thread count required for the application.

KG-1023 Summary The TIBCO Web Messaging for TIBCO Enterprise Message Service ™ Flash and JavaScript libraries are not supported on Opera running in UNIX platforms.

Workaround If using UNIX, use another browser, such as Mozilla Firefox 4.0+ or Google Chrome 10.0+.

Date post:	13-Apr-2018
Category:	Documents
Upload:	hoangthuan
View:	225 times
Download:	4 times

TIBCO Web Messaging for TIBCO Enterprise Message … · |4 Release Notes TIBCO Web Messaging for...

Documents