Skip to content
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.

Sign up for GitHub

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

Jump to bottom

calling destroy() on a not running instance will not stop Coap server #685

Closed
sbernard31 opened this issue Apr 18, 2019 · 1 comment
Closed

calling destroy() on a not running instance will not stop Coap server #685

sbernard31 opened this issue Apr 18, 2019 · 1 comment
Labels
bsserver Impact LWM2M bootstrap server bug Dysfunctionnal behavior client Impact LWM2M client server Impact LWM2M server

Comments

@sbernard31
Copy link
Contributor

sbernard31 commented Apr 18, 2019 •
edited
Loading

Trying to destroy() a "not running" instance (client, server or bs server) will not stop internal coap server.
Step to reproduce start(), stop(), destroy().

It seems to be a californium issue : eclipse-californium/californium#934

(tested only on leshan client)
@sbernard31 sbernard31 added bug Dysfunctionnal behavior client Impact LWM2M client server Impact LWM2M server bsserver Impact LWM2M bootstrap server labels Apr 18, 2019
@sbernard31
Copy link
Contributor Author

It should be fixed in master with the Californium 2.0.0-M15 integration (commit abe036f)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bsserver Impact LWM2M bootstrap server bug Dysfunctionnal behavior client Impact LWM2M client server Impact LWM2M server
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sbernard31