JMSTransportListener doesn't allow for predefined JMS ClientId

Anonymous avatarAnonymous created an issue

Spring allows you to set the JMS ClientID on the connectionFactory and in fact for durable subscribers, this is necessary as the setting the clientID must be the first operation.

The JMSTranportListener doesn't have an option to bypass setting the clientID - it must be either set specifically in the properties or else it takes on the name of the listener.

Specifically with durable subscribers, this will cause an error. I'm no export but I would imagine that if the listener property subscriptionDurable=true then the clientId should be ignored at this stage and a warning given if the admin also attempts to set the clientId on the listener.

Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.