We are using HiveMQ to send message from a few publishers (something like 10), to a few applications. For each topic, the consummer need the last message so all our published messaged are retained.
When we are starting the publishers, we first need to clean the topics so to be sure that the information in the broker is uptodate comparing to the one in the publisher. To do that, we send a payload of 0 bytes in each topic (not that much, around 6000 topics).
In hive Mq, I got these funny warning line 
No payload was found for the retained message on topic XXXX after a few days running. The message is a bit weird for me as normally either there is a payload, either, the 0 byte payload means the broker needs to delete the retained topic.
I had a look in HiveMQCE code but could really find a concrete explanation on these logs.
Hi @jonathan.robert,
Thank you for your patience.
Can you please let me know what exact version CE you are using?
It would also help to see the exact log statement.
Kind regards,
Florian form The HiveMQ Team.
The complete log is “No payload was found for the retained message on topic PARCIVAL/SR/XXXXXXX”
Hive v2020.2
very basic configuration file:
1883
0.0.0.0
I had a look in the source code but could really clearly see why I can arrive in that log…
Oups, the config file in a more readable format
<listeners>
<tcp-listener>
<port>1883</port>
<bind-address>0.0.0.0</bind-address>
</tcp-listener>
</listeners>
Hey @jonathan.robert,
Can you show us the exact log you are seeing please?
It would also help to understand what it is you are exactly doing with your HiveMQ deployment to reach that.
Thanks and regards,
Florian
Here an exemple:
2020-08-07 17:16:31,703 WARN - No payload was found for the retained message on topic PARCIVAL/SRVTR/SrtEquipementManager/VueEquipementCartoOSM/LigneDeFeuxIlog/8431.
2020-08-07 17:16:31,703 WARN - No payload was found for the retained message on topic PARCIVAL/SRVTR/SrtEquipementManager/VueEquipementCartoOSM/LigneDeFeuxIlog/7118.
2020-08-07 17:16:31,704 WARN - No payload was found for the retained message on topic PARCIVAL/SRVTR/SrtEquipementManager/VueEquipementCartoOSM/LigneDeFeuxIlog/7104.
2020-08-07 17:16:31,704 WARN - No payload was found for the retained message on topic PARCIVAL/SRVTR/SrtEquipementManager/VueEquipementCartoOSM/LigneDeFeuxIlog/8443.
2020-08-07 17:16:31,706 WARN - No payload was found for the retained message on topic PARCIVAL/SRVTR/SrtEquipementManager/VueEquipementCartoOSM/LigneDeFeuxIlog/8444.
2020-08-07 17:16:31,707 WARN - No payload was found for the retained message on topic PARCIVAL/SRVTR/SrtEquipementManager/VueEquipementCartoOSM/LigneDeFeuxIlog/8441.
2020-08-07 17:16:31,708 WARN - No payload was found for the retained message on topic PARCIVAL/SRVTR/SrtEquipementManager/VueEquipementCartoOSM/LigneDeFeuxIlog/8442.
2020-08-07 17:16:31,709 WARN - No payload was found for the retained message on topic PARCIVAL/SRVTR/SrtEquipementManager/VueEquipementCartoOSM/LigneDeFeuxIlog/7117.
2020-08-07 17:16:31,709 WARN - No payload was found for the retained message on topic PARCIVAL/SRVTR/SrtEquipementManager/VueEquipementCartoOSM/LigneDeFeuxIlog/7107.
2020-08-07 17:16:31,711 WARN - No payload was found for the retained message on topic PARCIVAL/SRVTR/SrtEquipementManager/VueEquipementCartoOSM/LigneDeFeuxIlog/7102.
2020-08-07 17:16:31,711 WARN - No payload was found for the retained message on topic PARCIVAL/SRVTR/SrtEquipementManager/VueEquipementCartoOSM/LigneDeFeuxIlog/8432.
2020-08-07 17:16:31,713 WARN - No payload was found for the retained message on topic PARCIVAL/SRVTR/SrtEquipementManager/VueEquipementCartoOSM/LigneDeFeuxIlog/8430.
2020-08-07 17:16:31,715 WARN - No payload was found for the retained message on topic PARCIVAL/SRVTR/SrtEquipementManager/VueEquipementCartoOSM/LigneDeFeuxIlog/8429.
2020-08-07 17:16:31,716 WARN - No payload was found for the retained message on topic PARCIVAL/SRVTR/SrtEquipementManager/VueEquipementCartoOSM/LigneDeFeuxIlog/7106.
2020-08-07 17:16:31,715 WARN - No payload was found for the retained message on topic PARCIVAL/SRVTR/SrtEquipementManager/VueEquipementCartoOSM/LigneDeFeuxIlog/7103.
2020-08-07 17:16:31,717 WARN - No payload was found for the retained message on topic PARCIVAL/SRVTR/SrtEquipementManager/VueEquipementCartoOSM/LigneDeFeuxIlog/8440.
2020-08-07 17:16:31,718 WARN - No payload was found for the retained message on topic PARCIVAL/SRVTR/SrtEquipementManager/VueEquipementCartoOSM/LigneDeFeuxIlog/8421.
2020-08-07 17:16:31,719 WARN - No payload was found for the retained message on topic PARCIVAL/SRVTR/SrtEquipementManager/VueEquipementCartoOSM/LigneDeFeuxIlog/8427.
2020-08-07 17:16:31,720 WARN - No payload was found for the retained message on topic PARCIVAL/SRVTR/SrtEquipementManager/VueEquipementCartoOSM/LigneDeFeuxIlog/7105.
2020-08-07 17:16:31,721 WARN - No payload was found for the retained message on topic PARCIVAL/SRVTR/SrtEquipementManager/VueEquipementCartoOSM/LigneDeFeuxIlog/8428.
2020-08-07 17:16:31,721 WARN - No payload was found for the retained message on topic PARCIVAL/SRVTR/SrtEquipementManager/VueEquipementCartoOSM/LigneDeFeuxIlog/8426.
2020-08-07 17:16:31,722 WARN - No payload was found for the retained message on topic PARCIVAL/SRVTR/SrtEquipementManager/VueEquipementCartoOSM/LigneDeFeuxIlog/8420.
As for what we are using hivemq CE for:
-
we are sending information from a centralized server containing real time information on traffic ligths system to HiveMQ (4 producers)
-
We are getting all this information to a consumer in order to visualize this real time data on a geosoftware (with maps).
-
We are using retain message as a new consumer must get access to old value of the message (we need to not wait for the next message to arrive). As a result, when we when to delete an information, we send a byte 0 data to hive MQ CE in the topic.
-
At the launch of the producer, to be sure that the data in hivemq CE is synchornised with the one on the producer part, we purge all hive mq data by sending a byte 0 payload to hive mq on the topics.
-
At the launch of the system, there is no such errors but by the time, the error is increasing in number.
I cannot really understand why there could be this kind of error in HiveMQ. I have checked the hd space and it is still ok. Do you have any hint ?
Hi,
we seem to have a very similar situation with our single Broker instance. Our use case seems to be very similar to Jonathan. In our case its flight information which are published retained regularly and are deleted after a couple of days.
We get a lot of messages like:
2020-08-20 13:23:39,509 WARN - No payload was found for the retained message on topic ...
and additionally a few of those:
2020-08-20 13:25:15,614 WARN - Tried to decrement a payload reference counter (2292463) that was already zero.
In this project we use the following Docker image as base hivemq/hivemq-ce:2020.2.
Quick followup: We updated to hivemq/hivemq-ce:2020.4 a week ago but still encounter the issue.
Is there anything we can provide to narrow down the issue?
Hello Mirko,
first of all welcome to the community!
Is it possible for you to describe your specific scenario in detail? Does your persistence contain sensitive information, or would you be able to share it with us for a closer analysis?
Kind regards,
Finn
Sorry for the delay, I just came back from holidays :).
As for another problem which can be related, we have seen an continuous increase of the size of the data folder containing the retained message data ( that folder size increased until all space was consumed (20Go).)
We will try to use the last version to see if the pb is solved.