RTR V3.1D RTRA224 RTR for Windows NT _ 95 3.1D Alpha ECO Summary
TITLE: RTR V3.1D RTRA224 RTR for Windows NT _ 95 3.1D Alpha ECO Summary
Copyright (c) Compaq Computer Corporation 1999. All rights reserved.
Modification Date: 11-FEB-99
Modification Type: New Kit
PRODUCT: Reliable Transaction Router (RTR) V3.1D
OP/SYS: Windows NT and Windows 95
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: RTRA224
ECO Kits Superseded by This ECO Kit: None
ECO Kit Approximate Size: 4578 Blocks
2343936 Bytes
Kit Applies To: RTR V3.1D
Windows NT V4.0
Windows 95 V4.0
Installation Rating: INSTALL_UNKNOWN
ECO KIT SUMMARY:
An ECO kit exists for Reliable Transaction Router (RTR) V3.1D on
Windows NT and Windows 95. This kit contains the following corrections
to RTR V3.1D (210) ECO8.
Problems Addressed in the RTRA224 Kit (ECO-9):
o 14-3-221 RTR crash during server reject plus network problems
Under unusual conditions (for example, one server rejecting the TX
and another accepting the same TX, or a TX being aborted due to
resource problems -- all at the same time that network fluctuations
are occurring) it was possible that RTR would find an inconsistent
TX state while recovering a TX from JNL. This resulted in RTR
crashing and has now been fixed.
o 14-3-260 Superfluous network traffic for nonexistent channels
Whenever a channel opens or closes, RTR sends an update message to
the router so that it can modify its broadcast routing information,
if necessary. In previous versions of RTR such messages were sent
even if no channel existed for the facility. In cases where
machines with the Frontend role had a large number of facilities
defined, this could result in significant network traffic that would
be quite noticeable over slow links, such as asynchronous
connections over telephone wire. RTR no longer sends these messages
unless a channel exists on the facility.
o 14-3-262 Hash table algorithm bug
The algorithm for accessing certain RTR data stored using a hash
table was found to be inefficient and could sometimes fail to find
data elements correctly. This bug has primarily affected access to
Transaction IDs and may have caused excessive CPU usage during data
retrieval or failure to find certain data elements. This bug has
been corrected.
o 14-8-147,14-8-162,14-8-164 Servers hanging during failover recovery
Transaction recovery as a result of server failover could result in
server applications getting hung in 'local recovery' state if it
also happened that more than 10 client channels had simultaneously
caused new transactions to be presented to the backend node. This
has been fixed both by increasing the limit to 50 and by adding a
check to make sure that recovery is complete before enforcing the
limit, which is designed to keep a backend node from getting
overwhelmed when transactions are coming in at a rate faster than it
can handle.
o 14-8-152 Multiple broadcast or data recived on wrong channel
When running W95/NT and having pathworks installed, RTR would not
detect that the client had closed its channel when the client
application was aborted by closing down the window. RTR now detects
when the client has aborted the channel and closes the channel.
o 14-8-163 Corrupt network message caused RTR crash
Reception of a corrupt network message would hitherto result in a
failed assertion and the demise of the RTR ACP process. The
behaviour has been changed to yield a log file entry (BADNETMSG),
followed by a reset of the link concerned. If such log file entries
persist for a particular pair of nodes, it may mean that a network
problem exists, and you should consider checking the network
hardware for correct operation.
The RTR log entry has also been improved to be better able to
identify the link on which it reports errors.
o 14-8-167 Null bytes display in SHOW PARTITION output
The display of null bytes in the upper and lower key bounds has been
suppressed if the bytes appear at the end of a key of type string.
The following restrictions apply to this kit:
o 14-1-285: A temporary inconsistency in shadow server state can
occur during initial facility startup of a shadowed configuration.
A shadow server can erroneously remain in state "sec_act" until the
rest of the facility has been started.
o 14-3-67: An application's wakeup routine may be called more often
than necessary.
INSTALLATION NOTES:
The Reliable Transaction Router V3.1D ECO9 installation procedure is the
same as the installation procedure for RTR V3.1D. Refer to the
Installation Guide for further information.
All trademarks are the property of their respective owners.
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
rtra224.README
rtra224.CHKSUM
rtra224.CVRLET_TXT
rtra224.exe
|
