Can RV 7.x components be intermixed in an environment with RV 8.x version components?
Article ID: KB0091451
Updated On:
| Products | Versions |
|---|---|
| TIBCO Rendezvous | - |
| Not Applicable | - |
Description
Resolution:
RV 8.x is fully backward compatible with RV 7.x, so in theory this configuration will work.
However, you must be aware that any known defects present in 7.x version, that have been fixed and included in 8.x version, may require both (eg. daemon) components to be of the same version in order to work correctly. It is generally recommended that daemon and client versions are of the same version in an environment at a given time where possible.
Secondly, RV 8.1.1 fixes a critical bug (CR 1-8YKCPR) which was introduced in RV 8.1.0.
Details of this fix are as follows:
1-8YKCPR
Fixed a defect (introduced in release 8.1.0) in which Rendezvous libraries and daemons could erroneously reject messages as corrupt when the reply subject longer than 120 characters. As a result, client applications could miss inbound messages. Note that rvrd routing—especially second-tier routing (border routing)—involves long reply subjects, and could trigger this symptom.
It is highly recommended that customers do not run RV 8.0.0 or 8.1.0 because of the above defect - instead upgrade to 8.1.2 (or latest GA version at that time)
RV 8.x is fully backward compatible with RV 7.x, so in theory this configuration will work.
However, you must be aware that any known defects present in 7.x version, that have been fixed and included in 8.x version, may require both (eg. daemon) components to be of the same version in order to work correctly. It is generally recommended that daemon and client versions are of the same version in an environment at a given time where possible.
Secondly, RV 8.1.1 fixes a critical bug (CR 1-8YKCPR) which was introduced in RV 8.1.0.
Details of this fix are as follows:
1-8YKCPR
Fixed a defect (introduced in release 8.1.0) in which Rendezvous libraries and daemons could erroneously reject messages as corrupt when the reply subject longer than 120 characters. As a result, client applications could miss inbound messages. Note that rvrd routing—especially second-tier routing (border routing)—involves long reply subjects, and could trigger this symptom.
It is highly recommended that customers do not run RV 8.0.0 or 8.1.0 because of the above defect - instead upgrade to 8.1.2 (or latest GA version at that time)
Issue/Introduction
Can RV 7.x components be intermixed in an environment with RV 8.x version components?
Feedback
Yes
No
Powered by
