Description:
Product Name:    TIBCO SmartSockets
Release Version: 6.7.0
Patch Version:   2
Release Date:    January 2006
======================================================================
Note: All SmartSockets hotfixes are cumulative, so this hotfix also contains all the fixes provided in hotfix 1. For the complete list of issues addressed along with the complete release notes see the link provided below.

Customers with an eSupport login account can use the link provided below to download this hotfix

** TIBCO employees will not be able to use the embedded link, please contact Support if you have access questions.
======================================================================
Reported Fixes (TIB_ss_6.7.0_CFIX_V2):

*       Limit the size of conn write_buffer nodes that will be pooled.
        This should reduce memory overhead in an environment where
        large messages are being sent.
        (CR 1-6W5T0T)

*       Added 'disable_mon_watch_types' option to RTserver. This
        option is a list of watches (as accepted by the 'watch' RTmon
        command) to ignore. The special identifier '_all' may be used
        to specify all watch types. List items prefixed with '!' will
        negate the functionality (e.g. the value '!client_names,_all'
        means disable all watch types except client_names).
        (CR 1-6TBSBA)

*       Fixed a problem in the RTserver that could cause lost messages
        when publishing GMD messages with priorities set, which could
        result in clients becoming suspended indefinitely.
        (CR 1-6R7ZC9)

*       Fixed a problem with compression that caused latency on the
        data stream (data already received might not be uncompressed
        until additional data was received). In some cases, this could
        cause handshakes to fail, leading to clients that would time
        out when trying to connect.
        (CR 1-6TQCF3)

*       Fixed a problem that caused RTserver to core on startup if
        '-threads 1' was used with a license that does not allow
        multi-threaded servers.
        (CR 1-6RTT0Z)

*       Changed allocation functions to print the size of the failed
        allocation in its call to TutFatalError (when a SmartSockets
        application runs out of memory). Note that this information
        will not be in the trace_file, and may only be available on
        the terminal.

*       Fixed a problem in RTserver that prevented clients connected
        via RTgms from being disconnected correctly if the connection
        to RTgms was lost. This only affected RTserver in single-
        threaded mode.
        (CR 1-6UWZ00)

*       Fixed a problem with client_msg_send/client_msg_recv watches
        with Java/C# clients that required ss.monitor_level to be set
        to 'all' on the watched client for these watches to work.
        (CR 1-6T3TUX)
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
Reported Fixes (TIB_ss_6.7.0_CFIX_V1):

*       Improved memory usage behavior of RTserver. This change allows
        a performance improvement that may be significant on some
        platforms.
        (CR 1-6PZ6SV)

*       Fixed a problem with subjects ending in '.../...' that could
        cause RTserver to crash.
        (CR 1-6MBQI2)

*       Fixed a problem in the RTserver that could cause it to crash
        under particular circumstances involving mixed GMD and non-GMD
        messages and RTservers disconnecting from each other.
        (CR 1-1B3HSF)

*       Fixed a timing problem that could cause RTclients connecting
        using the PGM link driver to core. The problem existed on all
        platforms, but was more prominent on Linux.
        (CR 1-6PMEEZ)

*       Fixed a problem in the Java API that could cause deadlocks
        when a subscriber disconnects while publishing GMD messages.
        (CR 1-6MBQH9)

*       Updates to the PGM link driver logging to improve diagnostics.
        (SR 1-61RER1)

*       Deprecated the 'stats' logging option in the PGM link driver.