What's the expected behavior when using shared subscriptions in a single docker container? #2273
-
We have integration tests that run against a single local docker container running vernemq (that is configured with a custom lua script for auth script, but I don't think this is involved). We want to leave the shared subscription configuration the same when running in the test configuration as when we're running in a cluster. That is, we don't want to use When we run with a subscriber subscribing to a shared subscription, the subscriber never gets any messages when running vernemq as a single local container. What's the expected behavior? I expected it to just work, but it doesn't appear to be. Our custom auth logs show the broker happily accepting the shared subscription without warning:
There are many duplicated log messages like the following:
but that is expected, I think, because there's only one broker in this configuration. Thanks in advance. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Never mind. Typo in shared subject name. I had |
Beta Was this translation helpful? Give feedback.
Never mind. Typo in shared subject name. I had
$shared
(with ad
) instead of$share
. :/