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

[BUG] Polling of Tag value gets stoped after Session keep Alive failure error for a device in OPCUA #1567

Open
Kiruthick-Roxx opened this issue Jan 13, 2025 · 0 comments

Comments

@Kiruthick-Roxx
Copy link
Contributor

Description
When the OPC UA session encounters a "Keep Alive" failure, subsequent attempts to update tags fail. This issue persists even after the session is reconnected, causing disruptions in data synchronization.

Steps to Reproduce

Screenshot 2025-01-13 103536

  • Establish an OPC UA session and start updating tags.
  • Simulate a "Keep Alive" failure by disrupting the network or server connection (atleast more than a hour).
  • Reconnect the session after the failure.
  • Attempt to update tags.
  • Expected Behavior:
  • Tag updates should resume normally after the session is reconnected.

Actual Behavior
Tag updates fail even after the session is reconnected, requiring a complete restart of the server to restore functionality.

Environment

  • FUXA version: V.1.2.3-2105
  • Node.js version: 18.20
  • npm version: 10.9.0
  • Platform/OS: Ubuntu 20.04
  • Browser: Chrome
@Kiruthick-Roxx Kiruthick-Roxx changed the title [BUG] Tag updation gets stops after Session keep Alive failure in OPCUA [BUG] Polling of Tag value gets stoped after Session keep Alive failure in OPCUA Jan 17, 2025
@Kiruthick-Roxx Kiruthick-Roxx changed the title [BUG] Polling of Tag value gets stoped after Session keep Alive failure in OPCUA [BUG] Polling of Tag value gets stoped after Session keep Alive failure error for a device in OPCUA Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant