When this issue was first logged it was a case of implementing
- JMS_SPEC-73 (Define how messages from a topic are delivered to clustered application server instances) and
JMS_SPEC-30 (Define mandatory activation config properties clientId and subscriptionName)
Since then there has been a change of requirement. JMS_SPEC-73 has been deferred until a later version of JMS and so is not needed for MQ 5.0. I am therefore removing the dependency on this issue.
Please remove the features defined in JMS_SPEC-73, but make sure that the features defined in