Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
HowTo handle "faulted" connection attempt
See original GitHub issueActually I want to implement an auto reconnect on faulted connection attempts.
After the connection failed, the actual State = CommunicationState.Faulted.
In OpenAsync() (https://github.com/convertersystems/opc-ua-client/blob/master/UaClient/ServiceModel/Ua/Channels/CommunicationObject.cs#L187) there is a check if the State == CommunicationState.Faulted (https://github.com/convertersystems/opc-ua-client/blob/master/UaClient/ServiceModel/Ua/Channels/CommunicationObject.cs#L473). This results into an InvalidOperationException("Channel not modifiable.") .
How should I resolve the problem?
CloseAsync() is not possible to be called -> Exception(Channel faulted)
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Back when I started this project, I tried to follow Microsoft’s WCF guidelines. When you used a WCF client, and there was an exception, you would catch the exception and Abort (vs Close) the Client. Abort disposes the channel without communicating to the server ( which probably has closed it’s session anyway)
@awcullen Hi Andrew. Why would AbortAsync be needed if the channel faulted? Shouldn’t it already be closed?