When mqtt5.0 produces messages, the log error is found as follows:
However, there is no problem with the mqtt5.0 production and consumption process.
The reason is that when entering the topicAliasInvalid check, error-level logs are directly printed.
So, fix it to debug-level.
When mqtt5.0 produces messages, the log error is found as follows:
However, there is no problem with the mqtt5.0 production and consumption process.
The reason is that when entering the topicAliasInvalid check, error-level logs are directly printed.
So, fix it to debug-level.