When commenting the line with .correlationData(correlationData.getBytes()) the message appears on the test page MQTT Websocket Client and at my subscribers.
When using that line, the message is successfully sent as shown by the logger in ‘whenComplete’ but never appears in the websocket-client, and doesn’t arrive at any subscriber.
So I guess I’m using the correlationData in the wrong way? Or did I just discover a bug?
Thanks Florian for the link, but I don’t really understand this example. It uses two simultaneous connections to HiveMQ Cloud? Anyhow this code, which looks now very similar to the sending part of that example has the same issue, need to disable the line with correlation data to see the message arriving…
Tried the same code and works OK with correlationData when pushing/subscribing to a local HiveMQ instance in a Docker (without SSL) which was started with
docker run -p 8080:8080 -p 1883:1883 hivemq/hivemq4
Also works OK with a Mosquitto broker on stackhero.io.
So that would mean that there is a problem with HiveMQ Cloud when using correlationData…
Thank you for your patience. We were able to verify this is something misbehaving on our cloud service.
Our devs are already on the case.
Will let you know as soon as we have a solution.