Internal error, caused by no new message IDs being available #9583
Replies: 1 comment
-
Please, don't duplicate questions in different places. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I was using the Spring-Integration-mqtt module to send and receive MQTT messages and the following exception occurred:
Below are the versions of each component I used
Java: 21
Spring: 6
Spring-Integration: 6.3.0
Spring-Boot: 3.3.0
The following is my core logic. I configured two Mqtt clients using Spring-Integration integration flow. One is used to receive information, and the other is used to send messages. The frequency of sending messages is about 5000 messages per second.
I use the MessagingGateway annotation to direct messages to my
mqttOutboundChannel
so I can use MqttGateway to send mqtt messagesWhen the message delivery rate is very low, generally less than 200 messages per second, the error I mentioned at the beginning will not occur, but when I increase the message production rate to 5,000
When I removed the inbound part of mqtt messages, I found that the program worked very well without any errors. Once I introduced the
statusInboundFlow
integrated flow in the above code, the mqtt outbound client could not send messages normally and a large number of messages appeared. The exception mentioned beforeIn fact, I searched for an issue in paho's repository that has been closed for a long time. I think it may be related to him, but since paho's repository has been archived, I don't think I can get updated news from here.
#323
I expect that according to the above logic, I can send and receive MQTT messages normally
Beta Was this translation helpful? Give feedback.
All reactions