Kbase P21588: Compatibility Of Different Versions of SonicMQ
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
01/01/2004 |
|
Status: Unverified
GOAL:
Compatibility Of Different Versions of SonicMQ
FACT(s) (Environment):
SonicMQ
FIX:
Not all client and broker versions may connect to each other. This solution discusses the runtime compatibility of different versions of SonicMQ brokers and clients.
EXPLANATION:
Interoperability when using mixed versions of SonicMQ brokers and clients is as follows:
- Version 2000.x clients may not connect to a different version broker.
- A version 2000.x broker will not accept connections from a different version client.
- Version 2000.x brokers may not connect to any version of broker in a multi-node environment, since version 2000.x does not support Dynamic Routing Architecture.
- Version 3.0 JMS clients may connect to a version 3.5 broker or a version 4.0.x broker.
- Version 3.5 JMS clients may not connect to a version 3.0 broker.
They may connect to a version 4.0.x broker.
- Version 4.0.x JMS clients may not connect to any version 3.x broker.
- An administrative client of a given version may only connect to the same version broker.
- All brokers within a single cluster must be the of same version, and a cluster's configuration server (which is not necessarily a member of the cluster) must be the same version as the brokers in the cluster it administers.
- Therefore, all brokers within a routing node must be of the same version.
- Version 3.0, version 3.5, and version 4.0.x routing nodes may connect
to each other.
In general, the goal is to allow JMS clients of the previous release to connect to a broker of the next release. This is based on the premise that brokers are in central locations, while clients are more numerous and widely distributed; therefore, it is easier to upgrade brokers first, and all at once, and then to allow clients to be upgraded gradually.