Lars Hesel Christensen
Lars Hesel Christensen
Hi, Thanks for opening the issue. That's a good point, this is unfortunately a hardcoded limit which is set to 5 seconds at the moment: https://github.com/erlio/vernemq/blob/master/apps/vmq_server/src/vmq_mqtt_fsm.erl#L22 We'll have to see...
Hmm, looking close at this, it's actually really simple to change so it's globally configurable. I'll create a PR with it and see if there's agreement to go with that...
Ah, interesting. I didn't think about it before, but there might also be a timeout in the Erlang SSL stack - I'll check if that's the case.
Hi @szymonk it indeed look like we're forwarding the QoS2 message if a second PUBLISH for the same message id arrives. I'll create a PR with a testcase and a...
Pr is ready- would you have to possibility to test it?
Great - note that we only fixed the forwarding of a second message if the PUBLISH with the same message id is sent during an existing QoS2 flow. According to...
Good the original issue was fixed - we'd have to look into this other issue. Is the DUP flag set on those 10 messages? Are you publishing across nodes when...
And just to rule out the obvious, can you confirm that the message isn't published twice due to some issue on the publisher side?
> I thought this might be caused by the allow_*_during_netsplit settings so I switched them off but the problems still occurs. Are those duplicates expected also with CAP settings turned...