-
Notifications
You must be signed in to change notification settings - Fork 407
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request cannot be sent in the class that implements *Listener class #388
Comments
Hi,
Could you be more precise ? Which kind of issue ?
I already do that without issue.
I do not understand which redis channel ? |
If one overrides updated and registered methods and sends request in these method, You can try to register 500 devices and sending a write request in the updated methods. I believe one needs to listen LESHAN_REG_UP and, then, send the write request to LESHAN_REQ, |
Without logs or more details about that this will be difficult to do anything.
What clients implementation are you using ?
You seems to talk about LeshanClusterServer. Just to let you know, this is just an experimental work. |
I feel the issue may be because
I guess this is why the deregistration happened ... Thanks :) |
FMPOV, I don't think removal of Q mode was involved in this issue. About UDP you're right : order is not guaranteed and message can be lost. => About update, the server will clean registration when "lifetime" is out of date. This is up to the client to update before this "lifetime" expired. Some "bad" client implementation" try to send update request with a period of "lifetime" value. This is a mistake because the update request could take time before server receive it (because of packet lost and retransmission). A client should use a period as : LWM2M LIFETIME - CoAP HTH |
For the client, we are using Java's simulator, not wakaama. I don't feel client having issue because I can see the log from client. What do you mean by "client/server and CoAP rolw is not always synchronized" ? I think the client has no issue according to the log. One more thing, I created many clients in one container in the docker env. Thanks :) |
What I'm saying is : Client can send request too late. E.g. the client have a lifetime set to 3 minutes. Thats means the server will dropped the registration, after 3 minutes without receiving update request. Imagine a client which send its update request each 3 minutes or even 2 minutes 30 seconds.
This is just an hint to better understand the link provided. e.g. A LwM2M client behave as a CoAP client when it send a update request and as a CoAP server when it receive a read request.
Where do you get that ?
I don't think so. Are you using security ? and are you in a changing IP environment like behind a NAT ? (see #345) |
Hi sbernard31, I decided to send out the requests through redis channel, LESHAN_REQ, instead. I have a question. For example, for the write request, it will look like something below. Thanks :) |
I don't know what is your use case, but there is poor chance than using redis channel was a good idea. |
Got it :) Thanks :D |
Hi,
I have a class that implements RegistrationListener and
try to send the request in the methods, registered and updated.
I found that sending the request there will cause some unstable issues which result in
the devices being cancelled/unregistered.
Can someone send the request in the class or someone must do it through redis channel ?
Thanks :)
The text was updated successfully, but these errors were encountered: