You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I need to manage a shared subscription topic to handle two different flows
The topic is +/+/GICS/CMD/FEEDBACK/#
and the 2 subscriptions are:
$share/usem-group-tmp/+/+/GICS/CMD/FEEDBACK/#
$share/usem-group/+/+/GICS/CMD/FEEDBACK/#
What happened
It happen that every time a try on mqttX client to send a message on topic LO201/TEST/GICS/CMD/FEEDBACK/TEST
sometimes they both receive the message(correct) and sometime only 1 sub receive the message twice (that's the problem).
While if try to simplify the topic name i have no problem, both receive the same message and i don't see any problem
Environment
I discovered this problem within k8s cluster and i replied the problem on my local machine(W11) using mqttx
The text was updated successfully, but these errors were encountered:
Sorry for replying late. It seems that you have used different group names in the shared subscription. Therefore, in theory, the same message will be received simultaneously. Does this meet your expectation? I tested it. According to the information you provided, I sent 28 messages at the same time. Two different subscription clients received the messages. I am using EMQX. I am not sure what your MQTT Broker is? Is it related to the MQTT Broker? Or what's your MQTTX version?
What did I do
I need to manage a shared subscription topic to handle two different flows
The topic is +/+/GICS/CMD/FEEDBACK/#
and the 2 subscriptions are:
What happened
It happen that every time a try on mqttX client to send a message on topic LO201/TEST/GICS/CMD/FEEDBACK/TEST
sometimes they both receive the message(correct) and sometime only 1 sub receive the message twice (that's the problem).
While if try to simplify the topic name i have no problem, both receive the same message and i don't see any problem
Environment
I discovered this problem within k8s cluster and i replied the problem on my local machine(W11) using mqttx
The text was updated successfully, but these errors were encountered: