Open jsanyi opened 2 years ago
ah, right, looks like WampMQTTServerProtocol
needs some adjustment to the recent multi-node / clustering (proxy workers, rlinks) changes in crossbar. nothing big, but someone would need to dig into.
has there been any progress on this issue?
apologies for the double comment – this is blocking us from upgrading to newer versions of crossbar. we're willing to pay to have this issue resolved if someone with more expertise is willing to fix it.
/cc @oberstet
@richard-pianka Hi Richard, sorry for not reacting before, but I'm busy these days with mundane things like making money;) However, as you mention you would pay for fixing this, so I'd be happy to resolve it. Please get in touch with me via email "tobias dot oberstein at gmail dot com".
As mentioned before, I don't expect this to be complex but tricky to fix the right location in the right way. I know the code base inside out, and for fixing the issue, I'd also create proper, automated test cases using your MQTT client library (or any standard one that fits the bill, like we already use in crossbar-examples) and actually running Crossbar.io in multi-process/node clustered configuration (multiple proxy and router worker) - the whole reason for the original change that lead to this regression ...
I'm running 22.6.1 from a pip install in venv, and cannot get mqtt transport working, see crash log below.
=====
=====
This is my transport configuration: