I see 2 subscribe services don’t subscribe to same msg at same time from same queue.
If Subscribe_Service1 invokes, subscribe_Service2 won’t invoke and vice versa.
==========================================================================================================
With Topic Type: I Have created 1 JMS Publish service and 2 subscribe service’s subscribing to same Topic
I see 2 subscribe services don’t subscribe to same msg at same time from same topic.
If Subscribe_Service1 invokes, subscribe_Service2 won’t invoke and vice versa.
Is this an expected behavior or is something wrong? Ideally, I guess both the target triggers must subscribe?
There is one queue or durable subscriber, so there is only one message. Then, two triggers pointing to same queue or durable subscriber, so only one will pick up the message and process it.
In case you want multiple copies of the message, and each copy processed by different triggers, then you can do that with Topic.
In case of topic, you can have multiple durable subscribers. Each subscriber will get one copy of message. Both the topic trigger will be invoked. In IS topic trigger definition, use different Durable Subscriber name and same Topic name. That should work for you.
when Iam trying to create a new trigger with same topic and different durable subscriber name. IS is throwing error " topic already exists on same JMS connection alais"
if I try using different “JMS connection alais” error msg : “JMS event : {topicName} already exists.”
I am not sure what could be wrong. I could setup two separate durable subscribers for same topic. I used Broker for my setup. UM JNDI/Topic will be slightly different. IS will work same way in either case.
Last screenshot shows disconnect client because I did not configure pub/sub permissions for the document type in broker.
Once done, both trigger will be enabled and subscribers should show connected.
