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

BadRequestTimeout on CoreClientUtils.SelectEndpoint after Update of Library from 1.4.371.96 to 1.5.374.36 #2671

Open
1 of 5 tasks
DerGary opened this issue Jul 11, 2024 · 1 comment
Assignees
Labels
bug A bug was identified and should be fixed. needs investigation

Comments

@DerGary
Copy link

DerGary commented Jul 11, 2024

Type of issue

  • Bug
  • Enhancement
  • Compliance
  • Question
  • Help wanted

Current Behavior

We currently have the following setup:
ARsim (B&R OPC Simulation) on Windows > WSL containing Docker > Docker Container containing OPCUA Client.

When this Code is execute with Version 1.5.374.36 :

var serverAddress = "opc.tcp://HOSTNAME:4841";
var endpointDescription = CoreClientUtils.SelectEndpoint(
            applicationConfiguration,
            serverAddress,
            useSecurity: true
        );

We obtain the following Exception:

Opc.Ua.ServiceResultException: BadRequestTimeout
    at Opc.Ua.Bindings.ChannelAsyncOperation`1.End(Int32 timeout, Boolean throwOnError)
    at Opc.Ua.Bindings.UaSCUaBinaryClientChannel.EndSendRequest(IAsyncResult result)
    at Opc.Ua.DiscoveryClient.GetEndpoints(RequestHeader requestHeader, String endpointUrl, StringCollection localeIds, StringCollection profileUris, EndpointDescriptionCollection& endpoints)
    at Opc.Ua.DiscoveryClient.GetEndpoints(StringCollection profileUris)
    at Opc.Ua.Client.CoreClientUtils.SelectEndpoint(ApplicationConfiguration application, String discoveryUrl, Boolean useSecurity, Int32 discoverTimeout)

When Version 1.4.371.96 is used instead, it works.

Expected Behavior

endpointDescription is returned and no exception is raised

Steps To Reproduce

As the Setup is somewhat complicated, it is hard to set up a sample to reproduce this.

Environment

- OS: Windows 10
- Environment: VSCode
- Runtime: .Net 8
- Nuget Version: 1.5.374.36
- Component: Opc.Ua.Client
- Server: B&R Simulation

Anything else?

No response

@mregen mregen added the bug A bug was identified and should be fixed. label Jul 12, 2024
@romanett
Copy link
Contributor

@DerGary I suspect some network issue here or an issue with the server. Could you please create a wireshark trace of the failed communication? If you filter to protocol type opc ua, you could find out if the client acts as defined in the spec.

@mregen mregen self-assigned this Aug 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A bug was identified and should be fixed. needs investigation
Projects
None yet
Development

No branches or pull requests

3 participants