Changes to cluster topic behavior

In this release, the behavior has changed when the publication ( PUB ) parameter differs across clustered topic definitions of the same name.

When the same named administered topic object is defined on multiple queue managers in a cluster, and each sets the CLUSTER parameter, the settings for all clustered topic object parameters should usually match across all definitions. If any settings do not match, this can result in different queue managers in the cluster using different settings for the topic parameters, with non-deterministic behavior being observed.

For this reason, when mismatches are detected, the following warning messages are written to each queue manager's error log:

Prior to this release, if the setting for the PUB parameter differed across definitions (for example if one was set to ENABLED and another to DISABLED ), then each queue manager in the cluster independently chose one value to use. This caused the acceptance or rejection of publications to be non-deterministic across the cluster.

With the introduction of topic host routing for publish/subscribe clusters in this release, the previously described behavior has been modified. If there is at least one definition of the clustered topic with a publication parameter set to ENABLED (or set to ASPARENT and locally resolving to ENABLED ), publications are now accepted. Publications are only rejected if all definitions for the topic in the cluster are set to DISABLED.

The following behavior is unchanged in this release: If a locally defined administered topic object exists, with or without the cluster attribute set, all parameter settings, including the setting for the PUB parameter, are taken from the local definition and not from the clustered topic definitions for remote queue managers.

For more information, see Multiple cluster topic definitions of the same name.