Connect timeout issue in MQTT Client

[anoop-007]

I have created an MQTT Client program which is working fine in Linux. When I compiled it for windows machine, if the client program fails to connect to server, it is not closing the connection. The connect() API inside mg_connect_resolved() is resulting in EWOULDBLOCK and it is keep trying for reconnecting instead of closing. But when I ran the same program in Linux, it simply close the connection with error message.

Attaching the log here.

67ce31e5 3 mongoose.c:3679:mg_iotest    select: -1 10022
67ce31e5 3 mongoose.c:2787:mg_connect   1 -> mqtt://<hostname>:1883
67ce31e5 2 client.c:131:event_handler   CREATED
67ce31e5 3 mongoose.c:2787:mg_connect   2 -> udp://1.1.1.1:53
67ce31e5 4 mongoose.c:362:mg_sendnsreq  1 resolving hostname @ 1.1.1.1, txnid 1
67ce31e5 4 mongoose.c:3281:iolog          2 01000001000000 0:0 35 err 0 (No error)
67ce33d9 4 mongoose.c:3721:mg_mgr_poll  2 r- tchrc
67ce33d9 4 mongoose.c:3281:iolog          2 01000001000010 0:0 51 err 0 (No error)
67ce33d9 4 mongoose.c:264:dns_cb       <hostname> 1
67ce33e9 3 mongoose.c:274:dns_cb        1 <hostname> resolved to XXX.XXX.XXX.XXX
67ce33e9 4 mongoose.c:3721:mg_mgr_poll  1 -- tChrc
67ce39c5 4 mongoose.c:3721:mg_mgr_poll  2 -- tchrc
67ce39c5 4 mongoose.c:3721:mg_mgr_poll  1 -- tChrc
67ce3fa1 4 mongoose.c:3721:mg_mgr_poll  2 -- tchrc
67ce3fa1 4 mongoose.c:3721:mg_mgr_poll  1 -- tChrc
67ce457d 4 mongoose.c:3721:mg_mgr_poll  2 -- tchrc
67ce457d 4 mongoose.c:3721:mg_mgr_poll  1 -- tChrc
..................

Is there anything needs to be specified for windows build to have a connect timeout?

[cpq]

To implement connect timeout, see https://github.com/cesanta/mongoose/blob/master/examples/http-client/main.c

The behavior seems to be correct. Could you attach a linux log as well, please?

[anoop-007]

I will make use of the timeout in http-client.

Attaching the Linux log for your reference

2577c 3 mongoose.c:2787:mg_connect      1 -> mqtt://aws.datashield.in:2883
2577d 2 client.c:131:event_handler      CREATED
2577d 3 mongoose.c:2787:mg_connect      2 -> udp://8.8.8.8:53
2577d 4 mongoose.c:362:mg_sendnsreq     1 resolving aws.datashield.in @ 8.8.8.8, txnid 1
2577d 4 mongoose.c:3281:iolog             2 01000001000000 0:0 35 err 0 (Success)
25971 4 mongoose.c:3721:mg_mgr_poll     2 r- tchrc
25971 4 mongoose.c:3281:iolog             2 01000001000010 0:0 51 err 0 (Success)
25971 4 mongoose.c:264:dns_cb           aws.datashield.in 1
25971 3 mongoose.c:274:dns_cb           1 aws.datashield.in resolved to 65.1.228.71
25971 4 mongoose.c:3721:mg_mgr_poll     1 -- tChrc
25f4e 4 mongoose.c:3721:mg_mgr_poll     2 -- tchrc
25f4e 4 mongoose.c:3721:mg_mgr_poll     1 -- tChrc
261c4 4 mongoose.c:3721:mg_mgr_poll     2 -- tchrc
261c4 4 mongoose.c:3721:mg_mgr_poll     1 rw tChrc
261c4 1 mongoose.c:402:mg_error         1 error connecting to 65.1.228.71:2883
261c4 1 client.c:137:event_handler      0x4 error connecting to 65.1.228.71:2883
261c4 2 client.c:183:event_handler      CLOSED
261c4 3 mongoose.c:2765:mg_close_conn   1 closed
261c4 3 mongoose.c:2787:mg_connect      3 -> mqtt://aws.datashield.in:2883
261c4 2 client.c:131:event_handler      CREATED
261c4 4 mongoose.c:362:mg_sendnsreq     3 resolving aws.datashield.in @ 8.8.8.8, txnid 1
261c4 4 mongoose.c:3281:iolog             2 01000001000000 0:0 35 err 115 (Operation now in progress)
263bb 4 mongoose.c:3721:mg_mgr_poll     3 -- tchRc
263bb 4 mongoose.c:3721:mg_mgr_poll     2 r- tchrc
263bb 4 mongoose.c:3281:iolog             2 01000001000010 0:0 51 err 115 (Operation now in progress)
263bb 4 mongoose.c:264:dns_cb           aws.datashield.in 1
263bb 3 mongoose.c:274:dns_cb           3 aws.datashield.in resolved to 65.1.228.71
269c5 4 mongoose.c:3721:mg_mgr_poll     3 -- tChrc
269c5 4 mongoose.c:3721:mg_mgr_poll     2 -- tchrc
26c12 4 mongoose.c:3721:mg_mgr_poll     3 rw tChrc
26c12 1 mongoose.c:402:mg_error         3 error connecting to 65.1.228.71:2883
26c12 1 client.c:137:event_handler      0x4 error connecting to 65.1.228.71:2883
26c12 2 client.c:183:event_handler      CLOSED
26c12 3 mongoose.c:2765:mg_close_conn   3 closed
26c12 4 mongoose.c:3721:mg_mgr_poll     2 -- tchrc
26c12 3 mongoose.c:2787:mg_connect      4 -> mqtt://aws.datashield.in:2883
26c12 2 client.c:131:event_handler      CREATED
26c12 4 mongoose.c:362:mg_sendnsreq     4 resolving aws.datashield.in @ 8.8.8.8, txnid 1
26c12 4 mongoose.c:3281:iolog             2 01000001000000 0:0 35 err 115 (Operation now in progress)
26e10 4 mongoose.c:3721:mg_mgr_poll     4 -- tchRc
26e10 4 mongoose.c:3721:mg_mgr_poll     2 r- tchrc
26e10 4 mongoose.c:3281:iolog             2 01000001000010 0:0 51 err 115 (Operation now in progress)

[cpq]

Please make an issue. This does not belong to discussions.

[anoop-007]

Sure. Thanks

…

On Sun, Jun 12, 2022 at 8:19 PM Sergey Lyubka ***@***.***> wrote: Please make an issue. This does not belong to discussions. — Reply to this email directly, view it on GitHub <#1585 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AV776SAFI3Y3JNGQPO3GFRLVOX2GNANCNFSM5YONRNIQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Best Regards, Anoop M