-
When clients connect, they get the retained messages. There is no need to do that while holding the subscriptions lock.
-
This mutes all INFO and NOTICE. Also fixed the parsing of the log_subscriptions.
-
The file IO is blocking, so we don't want that in our thread loops.
-
One fix is client destruction happening on the correct thread (when kicking another one off with existing client ID). This caused deadlocks on the subscriptions lock during a race condition when doKeepAliveCheck() also ran. A related deadlock was that the queued functions were executed while holding the lock taskQueueMutex. Together with the subscriptions lock, that was executed in the $SYS topic function, this also caused deadlocks.
-
The initial concept of iterating over a vector being fast didn't help, and made having many subscribers to one topic very slow.
-
This avoids changing which thread runs the code. Also let auth_plugin_serialize_init affect cleanup serialization.
-
Firefox worked without it. Chrome didn't.
-
One part is a fix, where the frame was advertised to be bigger than it was. The other change is making it possible to send chunks larger than the initial buffer size, by resizing the buffer (and resetting it later).
-
We interpret the close frames as closed transport, and therefore set 'error' to 'disconnected'. See code comments.
-
MQTT-3.8.3-3
-
MQTT-3.6.1-1
-
This fixes dpkg errors on removal.
-
Mandatory normative statement MQTT-3.1.2-6.
-
[MQTT-2.3.1-1]
-
When there are many sessions, the copying action can actually take some time, and memory. A vector is faster and uses (a little) less memory. This is a theoretical fix, without benchmarks to support it.
-
The only mutable session data of a client is QoS related, so when we're copying sessions (for saving them), we need to lock the QoS data, because that gets modified from active client traffic in worker threads. Note: not super well tested at this point, nor was I ever able to trigger actual errors despite long stress testing, so it's a theoretical fix.
-
Empty leaves weren't removed, causing increase in memory use.
-
This method incurs no extra CPU load when messages aren't dropped.