***************************************** ECO SUMMARY INFORMATION ***************************************** Release Date: July 12, 2007 Kit Name: DEC-AXPVMS-RTR-V0500-427-1.EXE Kit Applies To: OpenVMS Alpha V7.3-2 Approximate Uncompressed Kit Size:30208 blocks Installation Rating: Install_3 Kits Superseded By This Kit:DEC-AXPVMS-RTR-V0500-414-1.EXE Kit Dependencies: NONE System Reboot Necessary: NO Checksum of the Compressed Kit:498170871 HP Reliable Transaction Router______________________ Release Notes July 2007 HP Reliable Transaction Router (RTR) is fault tolerant transactional messaging middleware used to implement large, multitier, distributed applications using client/server technology. These notes describe the new features, corrections, restrictions, and known problems with workarounds for RTR Version 5.0 ECO2. Software Version: HP Reliable Transaction Router Version 5.0 ECO2 Hewlett-Packard Company Palo Alto, California ________________________________________________________________ © Copyright 2007 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. UNIX is a registered trademark of The Open Group. Java is a US trademark of Sun Microsystems, Inc. This document was prepared using DECdocument, Version 3.3- 1B. _________________________________________________________________ Contents Preface................................................... v 1 RTR Version 5.0 ECO2 1.1 Changes Applicable to All Platforms........... 1-1 2 RTR Version 5.0 ECO1 2.1 Changes Applicable to All Platforms........... 2-1 3 RTR Version 5.0 3.1 New Features.................................. 3-1 3.2 Changes Applicable to All Platforms........... 3-3 3.3 Information Applicable to All Platforms....... 3-3 3.4 Information Applicable to Windows Service Pack 2............................................. 3-4 3.5 Information Applicable to OpenVMS Platforms... 3-4 Tables 1 RTR Documents............................. v iii _________________________________________________________________ Preface Purpose of these Release Notes This document provides information for Reliable Transaction Router Version 5.0 ECO2. Intended Audience These Release Notes are intended for all users of Reliable Transaction Router. Please read this entire document before using the product. Related Documentation Table 1 describes RTR documents and groups them by audience. Table_1_RTR_Documents______________________________________ Document_________________Content___________________________ For all users: HP Reliable Transaction Describes new features, Router Release Notes[1] corrections, restrictions, and known problems for RTR. HP Reliable Transaction Provides an overview of RTR Router Getting Started technology and solutions, and includes the glossary that defines all RTR terms. [1]Distributed_on_software_kit.____________________________ (continued on next page) v Table_1_(Cont.)_RTR_Documents______________________________ Document_________________Content___________________________ HP Reliable Transaction Describes product features. Router Software Product Description For the system manager: HP Reliable Transaction Describes how to install RTR on Router Installation all supported platforms. Guide HP Reliable Transaction Describes how to configure, Router System Manager's manage, and monitor RTR. Manual For the application programmer: HP Reliable Transaction Describes how to design Router Application application programs for use Design Guide with RTR, with both C++ and C interfaces. HP Reliable Transaction Provides an overview of the Router JRTR Getting object-oriented JRTR Toolkit Started [2] including installation, configuration and Java programming concepts, with links to additional online documentation. HP Reliable Transaction Describes the object-oriented Router C++ Foundation C++ interface that can be used Classes to implement RTR object-oriented applications. HP Reliable Transaction Explains how to design and code Router C Application RTR applications using the C Programmer's Reference programming language and the RTR C Manual API. Contains full descriptions of the basic RTR API calls. [2]In_downloadable_kit.____________________________________ ___________________________________________________________ You can find additional information about RTR, including the Software Product Descriptions, on the RTR website found through http://www.hp.com links to middleware products or at http://www.hp.com/go/rtr . vi Conventions The following conventions are used in this manual: ___________________________________________________________ Convention________Meaning__________________________________ italic text Italic text emphasizes important information, indicates variables, and indicates complete titles of manuals. Italic text also represents information that can vary in system messages (for example, Internal error number), command lines (for example, /PRODUCER=name), and command parameters in text. UPPERCASE TEXT Uppercase text indicates a command, the name of a routine, the name of a file, or the abbreviation for a system privilege. user input This bold typeface is used in interactive examples to indicate typed user input. system output This typeface is used in interactive and __________________code_examples_to_indicate_system_output._ Reader's Comments HP welcomes your comments on this manual. Please send comments to either of the following addresses: Internet openvmsdoc@hp.com Postal Hewlett-Packard Company Mail RTR Documentation Group, ZKO3-4/Y17 110 Spit Brook Rd. Nashua, NH 03062-2698 vii 1 _________________________________________________________________ RTR Version 5.0 ECO2 This section contains information specific to RTR Version 5.0 ECO2. 1.1 Changes Applicable to All Platforms 1. QUIX QXCM1000364781/WFM 2209847619, Packet sequence number mismatch results in RTRACP crash RTRACP crashes when there is a mismatch in the packet sequence number. This problem has been corrected to terminate the link on which the corrupted packet is received instead of RTRACP crash. The link will be reestablished automatically by RTR. RTR also logs an appropriate error message in the log file. 2. RTR MONITOR QUEUE displays negative values RTR MONITOR QUEUE displays negative values for Queued TXN and Queued MSG fields. This problem has been corrected in this release. 3. QUIX QXCM1000346522/WFM 2208882597, To print appropriate error message when a node is not configured When a facility is not defined consistently on all nodes, RTR fails to connect to its peer node. This causes RTR to log "Node Not configured" error when the trace is enabled. Now RTR logging is enhanced to print "NODENOTCFG" error in the log file, by default. 4. QUIX QXCM1000395077/WFM 3217573329, RTRACP Crash on secondary backend nodes RTR Version 5.0 ECO2 1-1 RTR Version 5.0 ECO2 1.1 Changes Applicable to All Platforms The failover and fail back of frontend (FE) to preferred router (TR) triggers a situation where some of the voted transactions are aborted at the primary backend (BE) with strict order feature enabled. The transaction abort causes the primary backend to generate non-sequential Commit Sequence Numbers (CSN) used to maintain the same transaction presentation order at the secondary site. The secondary backend detects the non-sequential commit sequence numbers and also stops delivering the transactions to the server applications. Eventually this condition leads to memory exhaustion in secondary backend (BE) ACP process. This problem has been corrected in this release. 1-2 RTR Version 5.0 ECO2 RTR Version 5.0 ECO2 1.1 Changes Applicable to All Platforms 5. QUIX QXCM1000427922/WFM 2212963671, Timeout problem on OpenVMS I64 The Non-zero timeout value specified in SYS$START_TX() of RTRV2 API call is erroneously translated to zero on OpenVMS I64. Other supported platforms are not affected. This problem has been corrected in this release. 6. QUIX QXCM1000394600/WFM 1214255282, RTR fails to generate the process dump and error log when RTRACP process crashes While handling an exception related to threads library on OpenVMS, RTR fails to generate the process dump and rtr_error.log file. This problem has been corrected to generate the process dump and rtr_error.log file when RTRACP process crashes. 7. QUIX QXCM1000413680/WFM 1215038177, Transactions are delivered as uncertain messages during application startup During application startup, if the RTR router (TR) recieves any transaction messages for a partition in the local recovery, it requests the frontend to replay the transaction. These replay messages are delivered as uncertain messages to the server application, until 10 seconds after the partition becomes active. This problem has been corrected and the router (TR) now rejects the transactions instead of requesting for a replay. To provide this functionality, a new environmental variable RTR_NOREPLAY_ON_RECOVERY has been added and must be set to "1" on nodes configured as routers. RTR Version 5.0 ECO2 1-3 2 _________________________________________________________________ RTR Version 5.0 ECO1 This section contains information specific to RTR Version 5.0 ECO1. 2.1 Changes Applicable to All Platforms o QUIX QXCM1000229046/WFM 1207067034 Overlapping keys in key ranges Overlapping key range support can be enabled in RTR by defining an environment variable namely RTR_ENHANCED_ ROUTING with a value set to 1 on a node where router role is defined prior to ACP startup and opening server channels on backend node(s). In the absence of above mentioned environment variable, RTR uses the legacy routing mechanism where overlapping key range support is not available. This problem has been corrected in this release. o Suspend use of a network link if unreliable (AUTOISOLATE) RTR SET LINK/AUTOISOLATE/COUNT=- /TIMER= If auto-isolation has been enabled on a link between two nodes A and B, on node B and if node A reconnects "n times to node B" in "t time seconds" then, all connections from node A to node B will be rejected with LINKISOLATED error status. This AUTOISOLATION flag on the link from A to B at node B can be cleared by running the SET LINK/NOAUTOISOLATE. Any connection from A to B will be accepted post clearing the flag. RTR Version 5.0 ECO1 2-1 RTR Version 5.0 ECO1 2.1 Changes Applicable to All Platforms The default number of connections is 3, while the threshold time allowed for reconnections is 600 seconds. 3 and 600 are pure magic numbers and there is no rationale behind these values. This problem has been corrected in this release. o Facility Counters Facility broadcast flow control counters have been expanded to allow differentiation by broadcast flow directions and the monitoring of flow stall conditions. This change renders the following facility counters obsolete: fdb_cn_fct_brd_to_be_credit_avl fdb_cn_fct_brd_to_be_credit_rcvd fdb_cn_fct_brd_to_be_credit_used fdb_cn_fct_brd_to_be_grants_rcvd fdb_cn_fct_brd_to_be_grants_sent fdb_cn_fct_brd_to_be_reqs_rcvd fdb_cn_fct_brd_to_be_reqs_sent fdb_cn_fct_brd_to_be_wait_secs fdb_cn_fct_brd_to_tr_credit_avl fdb_cn_fct_brd_to_tr_credit_rcvd fdb_cn_fct_brd_to_tr_credit_used fdb_cn_fct_brd_to_tr_grants_rcvd fdb_cn_fct_brd_to_tr_grants_sent fdb_cn_fct_brd_to_tr_reqs_rcvd fdb_cn_fct_brd_to_tr_reqs_sent fdb_cn_fct_brd_to_tr_wait_secs They are superceded by a collection of counters using the following systematic names: fdb_cn_fct_brd__to__credit_avl fdb_cn_fct_brd__to__credit_rcvd fdb_cn_fct_brd__to__credit_used fdb_cn_fct_brd__to__grants_rcvd fdb_cn_fct_brd__to__grants_sent fdb_cn_fct_brd__to__reqs_rcvd fdb_cn_fct_brd__to__reqs_sent fdb_cn_fct_brd__to__wait_secs Valid role combinations are FE-TR, TR-BE, BE-TR and TR-FE. This problem has been corrected in this release. 2-2 RTR Version 5.0 ECO1 RTR Version 5.0 ECO1 2.1 Changes Applicable to All Platforms o Partition stuck in WAIT_TR_OK A new timer has been introduced to limit the duration for a partition waiting in WAIT_TR_OK state. The timer will be set when the partition goes to WT_TR_OK state. Upon the timer expiry, if the partition is still in the WT_TR_OK state, then all server channels will be closed and following error message is sent to the server application Error: WTTROKERR - "Unable to change the partition state from WT_TR_OK -server channel closed automatically" ________________________ Note ________________________ For V2 API the error code WTTROKERR is mapped to RTR$_ SHUTPEND ______________________________________________________ The default value for the WT_TR_OK timer is set to zero sec (Disabled). The timer value can be changed by the following command: $ RTR SET NODE/TR_OK_DELAY=value ________________________ Note ________________________ Setting a value of '0' disables the timer ______________________________________________________ Use the SHOW NODE command to check the value of WT_TR_OK timer This problem has been corrected in this release. RTR Version 5.0 ECO1 2-3 RTR Version 5.0 ECO1 2.1 Changes Applicable to All Platforms o RTR Explorer - data collection frequency disabled by default The detection interval for node monitoring has been set to zero (disabled) by default. Refer to the HP Reliable Transaction Router System Manager's Manual, for details on problem detection under REMEMBER EXPRESSION and SET NODE commands. This problem has been corrected in this release. 2-4 RTR Version 5.0 ECO1 3 _________________________________________________________________ RTR Version 5.0 This section contains information specific to RTR Version 5.0. 3.1 New Features o RTR Manager and RTR Explorer RTR has an improved management interface that includes an updated RTR Manager with useful popups and added performance monitoring charts. The interface additionally contains RTR Explorer, an automated alert system with a point-and-click interface that lets the system manager or administrator observe which node, facility, or partition may have a fault and drill down with point-and-click to quickly reach the element in question. o OpenVMS I64 support RTR is now available on the OpenVMS I64 platform. o Enhanced performance management RTR enables you to capture certain RTR performance counters and display them for monitoring with the standard Windows Administrative Tools Performance utility. For additional information, refer to the HP Reliable Transaction Router System Manager's Manual. o Compressed data transmission Transaction data can be transmitted in a compressed format, to address the needs of users who wish to reduce their network bandwidth requirements for the transfer of such data. For additional information, refer to the HP Reliable Transaction Router System Manager's Manual. o Improved shadow recovery performance RTR Version 5.0 3-1 RTR Version 5.0 3.1 New Features With fast shadow recovery, a node becomes primary active or secondary active as soon as it has copied all the transactions from the remembering node. For additional information, refer to the HP Reliable Transaction Router System Manager's Manual. o Improved monitor pictures RTR includes the following new or improved monitor pictures: - summary.mon - lrc.mon - compress.mon For additional information, refer to the RTR Monitoring chapter of the HP Reliable Transaction Router System Manager's Manual. 3-2 RTR Version 5.0 RTR Version 5.0 3.1 New Features o JRTR toolkit The JRTR toolkit modernizes RTR with Java support. The toolkit can be found on the RTR website at: http://www.hp.com/go/rtr Click on the Java RTR link to access the toolkit. Java RTR (JRTR) is a toolkit that layers on top of RTR. It provides standard Java and J2EE interfaces for RTR applications. JRTR exposes the traditional RTR features of hardware and software high availability, fault tolerance and entire-site disaster recovery by using already well-established interfaces. Specifically it provides JTA (javax.transaction.usertransaction), java.io.InputStream, java.io.OutputStream, and JDBC datasources and connection pools. With JRTR, programmers are more productive because they already know the Java and J2EE concepts. Your investment is protected because you are writing applications that are more portable and better able to integrate with other offerings in the marketplace. 3.2 Changes Applicable to All Platforms o 14-3-580, DISPLAY NUMERIC/DESCRIPTION restrictions removed Earlier restrictions on the number of help popups in a monitor picture have been removed, and enables use of help popups that have no labels. This problem has been corrected in this release. 3.3 Information Applicable to All Platforms o RTR V5.0 and RTR V5.0 applications will work with RTR V4.2 and RTR V4.2 applications on all operating systems on which RTR V4.2 is supported. These include: o Linux (frontend only) o Sun Solaris RTR Version 5.0 3-3 RTR Version 5.0 3.3 Information Applicable to All Platforms o Tru64 UNIX o OpenVMS o Windows Refer to the relevant RTR Software Product Description for specifics of supported operating systems. 3.4 Information Applicable to Windows Service Pack 2 o With the Windows Firewall option turned ON and with "Don't allow exceptions" option not selected: Requires RTR executable to be included in the Exceptions tab of the Firewall settings window. This allows RTR processes to communicate with other participating nodes of the RTR virtual network. o With the Windows Firewall option turned ON and with the "Don't allow exceptions" option selected: RTR processes cannot communicate with other participating nodes of the RTR virtual network. o With the Windows Firewall option turned OFF, there are no settings required for RTR. For more information on Windows Firewall options, see the Windows XP Service Pack 2 documentation. 3.5 Information Applicable to OpenVMS Platforms In RTR V5.0, to calculate the minimum PGFLQUOTA requirements of a node playing a backend role in an RTR facility, use the following formula: PGFLQUOTA=((max-links+max-processes)*400)+35000+ (reserve_memory_size*2048)+ ((CHANNEL_WAITQ_CAPACITY*max-processes*5)/512)+ (MAX_TPS_RATE *75*180) = default pages where, CHANNEL_WAITQ_CAPACITY is larger of (MAX_CHANNEL_WAITQ_BYTES*EVENT_CHANNEL_LIMIT_PC)/100 or 3-4 RTR Version 5.0 RTR Version 5.0 3.5 Information Applicable to OpenVMS Platforms (MAX_CHANNEL_WAITQ_BYTES*2) and MAX_TPS_RATE being the aggregate of maximum TPS rates for each BE role played by the given node, in all the facilities defined on that node. It is recommended that the above formula to be used in case of high TPS rates on a given backend node. RTR Version 5.0 3-5