Leshan request timeout of 5 s too short for large files / representations about leshan

[sbernard31]

After only ~5 years, a PR for this issue : #808 ! 🎊

I think this should be something we must address at short term.

Never trust me ... 😖

[sbernard31]

We clearly need a way to configure timeout.
For now, this is just not possible.
I think this should be something we must address at short term.

[chuchiliusandc]

hi @sbernard31

i noticed that, for bootstrapped simulator with security communication, 10 min after simulator sent the reg update, the request sent by the server cannot reach the simulator anymore. hence, i got coap timeout error. (note: lifetime is set to 15 min and request from server can still reach right after the next reg update.)

however, for non-bootstrapped simulator with no security communication, this won't happen.

i think this is related to DTLS.
i feel the data in NAT is removed after a while after reg up.
Do you know how this can be fixed ?

Thanks :)

[sbernard31]

This seems not linked at all to this issue ... So I would prefer if we talk about that in a new issue, so I created #585.

[Alex-EEE]

Can you point us in the right direction on how to fix this? Either a clumsy fix ( where can we just increase the timeout to be longer ) or would it be simple to reset the timeout on each packet received?

[sbernard31]

In ClientServlet of leshan-server-demo, there is several calls of server.send(...).

This is where you can choose the timeout.

Look at LwM2mServer javadoc to have more details about the API.
You can also look at https://github.com/eclipse/leshan/wiki/Request-Timeout if you want to better understand timeout.