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.

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

Reconnect does not work after RESTART_APPLICATION #74

Closed
git-kick opened this issue Feb 2, 2022 · 2 comments
Closed

Reconnect does not work after RESTART_APPLICATION #74

git-kick opened this issue Feb 2, 2022 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@git-kick
Copy link
Owner

git-kick commented Feb 2, 2022

Describe the bug
As a consequence of SYS.RESTART_APPLICATION, the E3/DC device is offline for a while.
The e3dc-rscp Adapter hangs after the E3/DC device is up and running again.

To Reproduce
Steps to reproduce the behavior:

  1. Go to SYS
  2. Set RESTART_APPLICATIONto true
  3. Observe that the E3/DC device is unreachable for about 1 Minute
  4. After the E3/DC device is up and running again, the e3dc-rscp adapter does nod work anymore (needs a restart)

Expected behavior
The e3dc-rscp adapter should silently recover from a E3/DC interruption.

Screenshots & Logfiles
N/A

Versions:

  • Adapter version: 1.0.2
  • JS-Controller version: 3.3.22
  • Node version: 14.15.3
  • Operating system: Win11

Additional context
N/A

@git-kick git-kick added the bug Something isn't working label Feb 2, 2022
@git-kick git-kick self-assigned this Feb 2, 2022
@git-kick
Copy link
Owner Author

@git-kick
Copy link
Owner Author

Solved with v1.0.3

  • reconnect also on tcpConnection.close
  • clear all timers after connection broke
  • start all timers within initChannel() - used to be in onReady()

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant