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

CoapServer is not well destroyed if it is not running #934

Closed
sbernard31 opened this issue Apr 18, 2019 · 0 comments
Closed

CoapServer is not well destroyed if it is not running #934

sbernard31 opened this issue Apr 18, 2019 · 0 comments
Labels
could this be closed?

Comments

@sbernard31
Copy link
Contributor

If you start a CoapServer, then stop it, then destroy it. The attached executor is not shutdown.
sbernard31 added a commit to eclipse-leshan/leshan that referenced this issue Apr 18, 2019
@sbernard31
"client destroy" should destroy client even if client is not running.
f3be830 
This fix does not solve completely the issue because of
eclipse-californium/californium#934
@sbernard31 sbernard31 mentioned this issue Apr 18, 2019
Closed
sbernard31 added a commit that referenced this issue Apr 18, 2019
@sbernard31
#934: add test to ensure CoapServer destoyed all created threads.
f7b6e8a
sbernard31 added a commit that referenced this issue Apr 18, 2019
@sbernard31
#934: shutdown attached executor on destroy even if server is stopped.
3b4973a
@sbernard31 sbernard31 mentioned this issue Apr 18, 2019
Closed
sbernard31 added a commit that referenced this issue May 13, 2019
@sbernard31
#934: add test to ensure CoapServer destoyed all created threads.
e10796e 
Also-by: Achim Kraus <achim.kraus@bosch-si.com>
sbernard31 added a commit that referenced this issue May 13, 2019
@sbernard31
#934: shutdown attached executor on destroy even if server is stopped.
1305a87
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
could this be closed?
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sbernard31 @boaks