Products | Versions |
---|---|
TIBCO SmartSockets | - |
Not Applicable | - |
Description:
Product Name: TIBCO SmartSockets
Release Version: 6.7.0
Patch Level: 4
Release Date: October 2006
======================================================================
Note:
TIBCO SmartSockets hotfixes are cumulative, therefore this release also incudes all the defects addressed in hotfixes 1 through 3. For the complete readme (including information on the defects addressed in the previous hotfixes) and installation instructions or to download this release, please see the links provided below.
======================================================================
Reported fixes (TIB_ss_6.7.0_CFIX_V4)
* Improved message send throughput and send latency in Java/C# client API's.
(CR 1-7HE7CO)
* Fixed a problem that could cause exceptions or other issues reading from a conn in Java/C# clients.
(CR 1-7D8YB3)
* Fixed a potential deadlock with multi-threaded Java/C# clients where one client is sending GMD/SOD messages while another one is receiving messages, and the client is being watched for `client_msg_recv' or `client_msg_send'.
(CR 1-72IKME)
* Fixed a timing issue in Java that could cause any method attempting to read a message (mainLoop, next, search, etc.) to ignore its timeout parameter and become suspended until data arrives.
(CR 1-73744B)
* Fixed a problem with Tipc*MsgNext in which the timeout could be ignored and the call could loop indefinitely if a steady stream consisting of only control messages (such as GMD_ACK's) is received.
(CR 1-717E11)
* Fixed a possible race condition in RTgms that could lead to data transmission being indefinitely suspended.
(CR 1-70564T)
* Fixed a problem that could cause clients to crash under rare circumstances after losing their connection.
(CR 1-6Z0D89)
* Fixed an issue that could cause conns with certain `unique_subject''s to monopolize a dispatcher if they lost their connection. This issue would cause clients that use the dispatcher to starve other connections while the offending connection tries to reconnect.
(CR 1-7GZ5NZ)
* Fixed a problem that could cause deadlocks in some circumstances involving multiple threads accessing a single conn if one thread is processing a keep-alive.
(CR 1-75ZX2B)