Description

JMS Event Listener on server has an option to connect to an endpoint as a durable subscriber.

In this model, the listener identifies to the JMS broker with some name. Currently, this name is not configurable - it is autogenerated in format subscr_<node-id>_<listener-id>.

For some use cases, it is important to be able to configure this name. One of these use cases is following:

JMS topic, all messages from the topic should be consumed exactly once

4-node cluster

Listener is configured with single-instance failover - i.e. exactly one instance of listener should be active at all times across the cluster

When the node with active listener goes down (e.g. HW or network failure), a different cluster node starts up the listener. But now the durable subscriber name is different because nodeId is different. With a different subscriber name, the JMS messages received are not the ones following the place where the previous listener instance left.

Acceptance criteria:

durable subscriber name can be configured to be always the same regardless of the node where the listener instance runs