-
Notifications
You must be signed in to change notification settings - Fork 215
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
Changing publishednodes.json causes LegacyJobOrchestrator to hang or lock up, does not process changes anymore #1032
Labels
bug
Something isn't working
Comments
I could reproduce this by overwriting the publishednodes.json file with invalid content (notice the space before the port number): [{"OpcNodes":[{"Id":"http://microsoft.com/Opc/OpcPlc/#s=FastUInt1","OpcSamplingInterval":500,"OpcPublishingInterval":10000,"HeartbeatInterval":10}],"EndpointUrl":"opc.tcp://opcplc1: 50000","UseSecurity":false,"ConfigurationId":"681f9962-ffc9-eb11-94b3-0003ff297e00"}] Publisher is stuck here:
Further changes to the file don't trigger the reload. Restarting publisher module results in:
OS: Ubuntu 18.04 |
8 tasks
Closed because the issue cannot be reproduced in version 2.8. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When changing the publishednodes.json file in OpcPublisher 2.7.206.36449, the LegacyJobOrchestrator / PublishedNodesJobConverter often hangs after detecting a file change, and will neither change the published nodes, nor will it ever listen/see another file change. No error is ever logged.
This problem comes in two flavours:
It is irrelevant which nodes we change, if we add/remove nodes or change a node's configuration. It seems to randomly work sometimes, and then refuses to work at all after the first failure.
All jsons we deploy are well-formed and after restarting the docker container the container can process the file.
To Reproduce
Expected behavior
Desktop (please complete the following information):
Additional context
It might be that there is a race condition, or something happens during unsubscribing from the OPC UA server. The long time between "converted items to jobs" and actually unsubscribing that sometimes occurs might also give a clue what is going wrong. The LegacyJobOrchestrator might be blocked and/or crashes and then nothing in the system can react to changes.
The text was updated successfully, but these errors were encountered: