-
-
Notifications
You must be signed in to change notification settings - Fork 422
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
Websocket connection could not be stopped properly #607
Comments
Got the bad boy in DeconzBridgeHandler.
this guy is never killed on dispose, so the objects stay all alive and try to keep working after disposing. |
Nice catch. I would prefer separate PRs for the fix and the rewrite. Can you do that? Regarding the rewrite I will write my opinion in the other chat. |
Any fix for this yet? A github online editor fix would be enough as a start. |
I have looked into the code and did not find any obvious problem. The mentioned timer is stopped correctly in |
I consider this issue not being related to deCONZ. The number of warnings in my test environment increased. I am running OH Build 1535. This time no deCONZ. Only binding is Kodi, which uses the
|
A quick update - this currently happens in other cases too (on snapshot version 1607) - not only for deCONZ binding.
|
Nothing we can really do here - see eclipse-archived/smarthome#6636 (comment). The only thing we maybe can do is to reduce the logging level in org.ops4j.pax.logging.cfg:
|
After restarting the bundle (version current snapshot build 1487) or disposing the Bridge handler I got this message with the following warnings all day long.
@davidgraeff Any thoughts?
The text was updated successfully, but these errors were encountered: