Description: Multiple durable subscribers are created for the same BW JMSReceiveMessage process starter.
Symptoms: Not setting client ID will generate output which will be similar to the following.
tcp://localhost:7222> show durables
Topic Name Durable User Msgs Size
* topic.sample TestNode-testflowcount.module.JMSConnectionResource-0c609208-0661-4c82-b546-56b1e026471e:TestSubscriber <offline> 6 0.6 Kb
* topic.sample TestNode-testflowcount.module.JMSConnectionResource-2f5e975d-1c54-4ee3-acf2-3ed2a562f9bb:TestSubscriber <offline> 10 1.0 Kb
* topic.sample TestNode-testflowcount.module.JMSConnectionResource-3e821e62-1e43-456d-bf9d-1443f76db95a:TestSubscriber <offline> 10 1.0 Kb
* topic.sample TestNode-testflowcount.module.JMSConnectionResource-d725cf9d-f863-4f76-8ed5-7cad67861097:TestSubscriber <offline> 3 0.3 Kb
* topic.sample TestNode-testflowcount.module.JMSConnectionResource-f958ad56-c045-4403-8cfc-9bffbb7262c8:TestSubscriber <offline> 10 1.0 Kb
Cause: Basically, Auto Generate Client ID will generate a new client ID every time a connection is made to the JMS Server.