We are having an issue with publish in crossbar io 22.6.1 and previous versions with Rlinks. We require Rlinks to forward local topic publications and RPC’s to cloud and vice versa.
Setup:
There is a crossbar router running on a local machine and another running on an AWS machine. Both have connected JS clients using Autobahn-JS which have 4 buttons to:
- Subscribe to “com.browser.hub”
- Subscribe to “com.browser.cloud”
- Publish to “com.browser.hub”
- Publish to “com.browser.cloud”
Steps:
- On the cloud machine, I subscribe to “com.browser.cloud” then subscribe to “com.browser.hub”
- On the local machine, I subscribe to “com.browser.cloud” then subscribe to “com.browser.hub”
- On the cloud machine, I publish to “com.browser.cloud” then publish to “com.browser.hub”
- On the local machine, I publish to “com.browser.cloud” then publish to “com.browser.hub”
You can see from the logs that the first 3 publishes are successfully sent to 2 receivers (sub on local and cloud) but the last one only goes to 1 receiver (sub on local):
Publishing on cloud to "com.browser.cloud"
Publishing on cloud to "com.browser.hub"
Publishing on local machine to "com.browser.cloud"
Publishing on local machine to "com.browser.hub"
This means that the second subscription is not being forwarded over the RLink. When making the subscriptions, this error message always accompanies subscriptions that are failed to be forwarded:
I believe that there is an issue with the syncing of sub IDs over RLinks.
It would be most appreciated if anyone can suggest any fixes or workarounds that could be done to get around this issue?
