-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[innogysmarthome] Reconnect fixes (#8182) #8353
[innogysmarthome] Reconnect fixes (#8182) #8353
Conversation
…8324)" This reverts commit ce5d4d8. Signed-off-by: Sven Strohschein <[email protected]>
…ore it wasn't rescheduled, because startClient is called by a scheduler which is everytime still running, so the detection was broken) Signed-off-by: Sven Strohschein <[email protected]>
Signed-off-by: Sven Strohschein <[email protected]>
Signed-off-by: Sven Strohschein <[email protected]>
… when an error occurs it is scheduled automatically again (so it is useless and disturbing the it is re-scheduled automatically with a fixed rate). Signed-off-by: Sven Strohschein <[email protected]>
Signed-off-by: Sven Strohschein <[email protected]>
Signed-off-by: Sven Strohschein <[email protected]>
Signed-off-by: Sven Strohschein <[email protected]>
Signed-off-by: Sven Strohschein <[email protected]>
Signed-off-by: Sven Strohschein <[email protected]>
Signed-off-by: Sven Strohschein <[email protected]>
Signed-off-by: Sven Strohschein <[email protected]>
Signed-off-by: Sven Strohschein <[email protected]>
Signed-off-by: Sven Strohschein <[email protected]>
Signed-off-by: Sven Strohschein <[email protected]>
Signed-off-by: Sven Strohschein <[email protected]>
Signed-off-by: Sven Strohschein <[email protected]>
Signed-off-by: Sven Strohschein <[email protected]>
…Exception(...), the scheduler was canceled again, because the code ran normally again after the Exception handling which reaches cancelReinitJob()... That caused that the scheduler wasn't executed in this case... Signed-off-by: Sven Strohschein <[email protected]>
Travis tests were successfulHey @Novanic, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I'll keep it open for a few more days so you can test if it's running ok this time 😉
Ok. :-) Here is a built version with the changes for testing, some people of a OpenHAB Innogy Facebook group seem also to test it now: https://www.dropbox.com/s/5vv5qpnznelq10d/org.openhab.binding.innogysmarthome-2.5.9-SNAPSHOT.jar?dl=0 |
Looks like you need to fix the conflicts cause by your other pr: #8375 |
Travis tests were successfulHey @Novanic, |
I hate Git... Just forgot to add Signed-off-by to the commit message.............. I think I have to create a new branch and a new pull-request........ |
Signed-off-by: Sven Strohschein <[email protected]>
Travis tests were successfulHey @Novanic, |
Signed-off-by: Sven Strohschein <[email protected]>
Looks like everything is ok? No need to create a new pr. When having to fix previous commits you can always use |
Travis tests were successfulHey @Novanic, |
Yes, I had luck that there was only the last commit message without sign-off. I had problems in the past with rebase and merge (rebases and merge commits weren't recognized correctly, all commits of other people were added to the pull-request). I think the problem is that I'm working with a fork and creating pull-requests from a branch of the fork... I should give up the fork for the next pull-requests. |
I think the pull-request could now get merged. At least 3 people tested the version for a few days and there were some reconnect attempts which were all successfully. The greatest risk is that I did something wrong on fixing the branch today... ;-) |
* startClient can now also get rescheduled when the method crashes (before it wasn't rescheduled, because startClient is called by a scheduler which is everytime still running, so the detection was broken) * The re-init job isn't scheduled for more than 1 time anymore, because when an error occurs it is scheduled automatically again (so it is useless and disturbing the it is re-scheduled automatically with a fixed rate). * Tests for InnogyBridgeHandler added * Bug-Fix: When an Exception occurred which was handled by handleClientException(...), the scheduler was canceled again, because the code ran normally again after the Exception handling which reaches cancelReinitJob()... That caused that the scheduler wasn't executed in this case... * Warning message improved Closes openhab#8182 Signed-off-by: Sven Strohschein <[email protected]>
* startClient can now also get rescheduled when the method crashes (before it wasn't rescheduled, because startClient is called by a scheduler which is everytime still running, so the detection was broken) * The re-init job isn't scheduled for more than 1 time anymore, because when an error occurs it is scheduled automatically again (so it is useless and disturbing the it is re-scheduled automatically with a fixed rate). * Tests for InnogyBridgeHandler added * Bug-Fix: When an Exception occurred which was handled by handleClientException(...), the scheduler was canceled again, because the code ran normally again after the Exception handling which reaches cancelReinitJob()... That caused that the scheduler wasn't executed in this case... * Warning message improved Closes openhab#8182 Signed-off-by: Sven Strohschein <[email protected]>
* startClient can now also get rescheduled when the method crashes (before it wasn't rescheduled, because startClient is called by a scheduler which is everytime still running, so the detection was broken) * The re-init job isn't scheduled for more than 1 time anymore, because when an error occurs it is scheduled automatically again (so it is useless and disturbing the it is re-scheduled automatically with a fixed rate). * Tests for InnogyBridgeHandler added * Bug-Fix: When an Exception occurred which was handled by handleClientException(...), the scheduler was canceled again, because the code ran normally again after the Exception handling which reaches cancelReinitJob()... That caused that the scheduler wasn't executed in this case... * Warning message improved Closes openhab#8182 Signed-off-by: Sven Strohschein <[email protected]>
This pull-request fixes a few reconnect problems regarding the WebSocket, see issue #8182 for more information