Are there any known issues with crossbar forgetting registered URIs?
I haven't seen such thing.
CB forgetting without some trigger is highly unlikely - removing a callee from a registration is an _active_ process.
Something must be triggering this.
I'd setup a subscriber component listing on the respective WAMP meta events for callees being added/removed to/from registrations, and logging that to a separate file.
This is light weight, you could run that in prod for some time.
Am 30.05.2017 um 20:18 schrieb Greg Keys:
You are running auto-ping/pong from CB side?
AB JS in browser doesn't have AB inititated heartbeating (lack of API in browsers), but AB JS on node _could_ have that ability.
We are just now starting to debug this but i thought I'd ask to see if it's a known issue
What's happening, is for some unknown reason at apparently random times URIs stop responding.
The callees are not AB JS (in browser), but AB Py components in data center I assume?
And the callers are AB JS (in browser), right?
It Started on version 17.2.1, we updated to 17.5.1 and still notice the problem.
The current theory is something to do with mismatched versions, we were using an old Autobahn version 0.10
We are updating all services to the latest 17.5.2 hoping that fixes the problem
In general, it's a good idea to run on synchronized versions, eg CB and all ABs on the same version.
We have moved the version numbering of all ABs and CB to calendar now, so it is easy to see how far versions differs in time of release.