communication
protocol_error
ai_generated
true
MQTT CONNACK: 数据包标识符已被占用
MQTT CONNACK: packet identifier already in use
ID: communication/mqtt-packet-identifier-in-use
76%修复率
81%置信度
1证据数
2023-04-18首次发现
版本兼容性
| 版本 | 状态 | 引入 | 弃用 | 备注 |
|---|---|---|---|---|
| Mosquitto 2.0.15 | active | — | — | — |
| Paho MQTT 1.3.12 | active | — | — | — |
| EMQX 5.0 | active | — | — | — |
根因分析
MQTT 客户端发送的 PUBLISH 或 SUBSCRIBE 数据包使用了尚未确认的重复数据包标识符,违反了 MQTT 协议规范。
English
The MQTT client sent a PUBLISH or SUBSCRIBE packet with a packet identifier that is already in use for an outstanding acknowledgment, violating the MQTT protocol specification.
官方文档
https://docs.oasis-open.org/mqtt/mqtt/v5.0/os/mqtt-v5.0-os.html#_Toc3901194解决方案
-
Implement a proper packet identifier manager that reuses IDs only after acknowledgment or timeout. Example in C using Paho: `MQTTAsync_setCallbacks(client, NULL, connlost, msgarrvd, onDeliveryComplete)` and track IDs via a hash set.
-
Increase `max_inflight_messages` in broker config (e.g., Mosquitto: `max_inflight_messages 20`) to reduce identifier reuse pressure.
无效尝试
常见但无效的做法:
-
50% 失败
Disabling QoS entirely (QoS 0) avoids identifiers but loses delivery guarantees.
-
80% 失败
Manually incrementing packet IDs without tracking acknowledgments still causes collisions.
-
70% 失败
Restarting the broker clears state but doesn't fix the client's identifier management logic.