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

BadTimeout error during publish leads to non recovering connection #2136

Closed
marcschier opened this issue Dec 13, 2023 · 0 comments
Closed

BadTimeout error during publish leads to non recovering connection #2136

marcschier opened this issue Dec 13, 2023 · 0 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@marcschier
Copy link
Collaborator

marcschier commented Dec 13, 2023

Not sure if this can be related, but in one of our cases we're seeing a similar message:

[18:28:43.6074] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaStack[0]
      Publish #162, Reconnecting=False, Error: BadTimeout
[18:28:43.6840] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaStack[0]
      Publish #162, Reconnecting=False, Error: BadTimeout
[18:28:43.7077] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaStack[0]
      PUBLISH #162 - Unhandled error BadTimeout during Publish.
      Opc.Ua.ServiceResultException: BadTimeout
         at Opc.Ua.ClientBase.ValidateResponse(ResponseHeader header)
         at Opc.Ua.SessionClient.EndPublish(IAsyncResult result, UInt32& subscriptionId, UInt32Collection& availableSequenceNumbers, Boolean& moreNotifications, NotificationMessage& notificationMessage, StatusCodeCollection& results, DiagnosticInfoCollection& diagnosticInfos)
         at Opc.Ua.Client.Session.OnPublishComplete(IAsyncResult result)
[18:28:43.7842] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaStack[0]
      PUBLISH #162 - Unhandled error BadTimeout during Publish.
      Opc.Ua.ServiceResultException: BadTimeout
         at Opc.Ua.ClientBase.ValidateResponse(ResponseHeader header)
         at Opc.Ua.SessionClient.EndPublish(IAsyncResult result, UInt32& subscriptionId, UInt32Collection& availableSequenceNumbers, Boolean& moreNotifications, NotificationMessage& notificationMessage, StatusCodeCollection& results, DiagnosticInfoCollection& diagnosticInfos)
         at Opc.Ua.Client.Session.OnPublishComplete(IAsyncResult result)

This occurs without a specific cadence, but with quite some frequency, sometimes within 2 minutes, sometimes within 3-4 minutes.

Apparently we're receiving all the data, but we continuously see messages like the above on the logs in between the statistics messages.

We have just 2 nodes subscribed on 2 servers, so a very simple configuration:

[
  {
    "DataSetWriterGroup": "1231",
    "DataSetWriterId": "DSWID:1231",
    "EndpointUrl": "opc.tcp://xxx.xxx.xxx.xxx:nnnn",
    "DataSetPublishingInterval": 10000,
    "OpcNodes": [
      {
        "Id": "ns=7;s=<identifier 1 here>",
        "OpcSamplingInterval": 400
      },
      {
        "Id": "ns=7;s=<identifier 2 here>",
        "OpcSamplingInterval": 400
      }
    ]
  },
  {
    "DataSetWriterGroup": "1232",
    "DataSetWriterId": "DSWID:1232",
    "EndpointUrl": "opc.tcp://yyy.yyy.yyy.yyy:nnnn",
    "DataSetPublishingInterval": 10000,
    "OpcNodes": [
      {
        "Id": "ns=7;s=<identifier 1 here>",
        "OpcSamplingInterval": 400
      },
      {
        "Id": "ns=7;s=<identifier 2 here>",
        "OpcSamplingInterval": 400
      }
    ]
  }
]

Originally posted by @nelsonmorais in #2104 (comment)

@marcschier marcschier self-assigned this Dec 13, 2023
@marcschier marcschier added this to the 2.9.4 milestone Dec 13, 2023
@marcschier marcschier added the bug Something isn't working label Dec 13, 2023
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