Skip to content

Commit 74980d0

Browse files
mqtt: Add KNOWN_ISSUES file
The KNOWN_ISSUES file describes the following: - "Unable to connect" and timeout errors - Publisher and Subscriber limitations Jira: ZEP-428 Jira: ZEP-632 Jira: ZEP-669 Change-Id: I10591a1fd14bccbeb0b7f3876549d29ddf8ffd1f Signed-off-by: Flavio Santes <flavio.santes@intel.com>
1 parent d748577 commit 74980d0

2 files changed

Lines changed: 31 additions & 0 deletions

File tree

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
Issues and Limitations
2+
----------------------
3+
4+
- Unable to connect
5+
Caused by:
6+
Incorrect TCP flags handling from the Zephyr IP Stack.
7+
Workaround:
8+
Reset the board.
9+
10+
- Publish error
11+
- Subscribe error
12+
Caused by:
13+
The MQTT broker is sending another MQTT message while the
14+
client is still processing the QoS handshake from a
15+
previous MQTT message. MQTT QoS in Zephyr is implemented
16+
in a synchronous way. For asynchronous implementations, see:
17+
http://git.eclipse.org/c/mosquitto/org.eclipse.mosquitto.git/tree/
18+
Workaround 1:
19+
Reduce the speed/amount of messages received by the
20+
application.
21+
Workaroung 2:
22+
Use the mqtt_read function to handle all the incoming
23+
messages.
24+
25+
- RX or TX error
26+
Caused by:
27+
Perhaps the rx/tx timeouts are too short for the LAN.
28+
Workaround:
29+
Increase the rx or tx timeout.
30+
See: publisher/src/netz.c, struct netz_ctx_t.
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
See ../publisher/KNOWN_ISSUES

0 commit comments

Comments
 (0)