{"action":"closed","issue":{"url":"https://api.github.com/repos/eclipse/mosquitto/issues/897","repository_url":"https://api.github.com/repos/eclipse/mosquitto","labels_url":"https://api.github.com/repos/eclipse/mosquitto/issues/897/labels{/name}","comments_url":"https://api.github.com/repos/eclipse/mosquitto/issues/897/comments","events_url":"https://api.github.com/repos/eclipse/mosquitto/issues/897/events","html_url":"https://github.com/eclipse/mosquitto/issues/897","id":344809676,"node_id":"MDU6SXNzdWUzNDQ4MDk2NzY=","number":897,"title":"Broker stops retransmitting at QOS1 when client does not send PUBACK (max_inflight_messages=1)","user":{"login":"keytee","id":14275514,"node_id":"MDQ6VXNlcjE0Mjc1NTE0","avatar_url":"https://avatars3.githubusercontent.com/u/14275514?v=4","gravatar_id":"","url":"https://api.github.com/users/keytee","html_url":"https://github.com/keytee","followers_url":"https://api.github.com/users/keytee/followers","following_url":"https://api.github.com/users/keytee/following{/other_user}","gists_url":"https://api.github.com/users/keytee/gists{/gist_id}","starred_url":"https://api.github.com/users/keytee/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/keytee/subscriptions","organizations_url":"https://api.github.com/users/keytee/orgs","repos_url":"https://api.github.com/users/keytee/repos","events_url":"https://api.github.com/users/keytee/events{/privacy}","received_events_url":"https://api.github.com/users/keytee/received_events","type":"User","site_admin":false},"labels":[{"id":384934294,"node_id":"MDU6TGFiZWwzODQ5MzQyOTQ=","url":"https://api.github.com/repos/eclipse/mosquitto/labels/packaging","name":"packaging","color":"d4c5f9","default":false}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":6,"created_at":"2018-07-26T11:45:17Z","updated_at":"2018-07-27T08:05:49Z","closed_at":"2018-07-27T08:05:49Z","author_association":"NONE","body":"We have an IoT system which has MQTT clients with limited resources. We are using QOS1 and the MQTT client can only handle one message at a time (no memory for queue). The concept is that if someone send 10 messages to that client (each client has its own topic) the client gets the message, process the message (send it over serial line) and if its OK send a PUBACK back. If something happens on the serial line and the client cannot forward the messages to is serial bus, then the client drops the MQTT message (not sending PUBACK back) and waits for the broker to retransmit the given message.\r\n\r\nBecause of the client can handle only one message at once, we are using max_inflight_messages = 1, which is working as expected (the broker not sending more than 1 message at a time) but after a client does not send PUBACK back, the broker not trying to resend the messages as expected (in every retry_interval time). The PINGREQ/PINGRESP works, and the client can send publish messages over the broker, the only problem is that client wont get any messages from the broker to the given topic until it reconnects.\r\n\r\nAre we doing something wrong or are we misunderstanding max_inflight_messages functionality?\r\n\r\nTested with 1.4.15 and 1.5 on linux (Debian 9.5)\r\n\r\nThanks"}}
{"actor":{"display_login":"keytee"}}