I'm looking at adding durable subscriptions for the JMS listeners ala https://jira.jboss.org/browse/JBESB-1890
What I have at the moment results in a config like the following (note the durableSubscriptionName attribute):
<jms-listener name="JMS-Gateway" busidref="quickstart-topic" is-gateway="true" durableSubscriptionName="quickTopic_service2" />
So... at the moment it's not actually on the <jms-message-fileter> config as per the JIRA. I think it needs to be on the listener because each subscriber needs to have a unique subscription name, or you get an exception from the JMS Provider i.e. if you have 2 listeners listening to the same topic and both are durable, they both need to have unique subscription names i.e. it's on a per listener basis.
There's also a new (optional) clientId attribute on the jms-listener. This is needed for durable subs. It is set on the associated JMS Connection, which means it becomes part of the pool key, so as to have a connection pool per clientId. If the clientId is not configured on the listener (but durableSubscriptionName is configured), we default to the clientId to the listener name value.
Does this seem OK, or am I mising something?