Exception thrown from Opening event handler causes hung state

[IGx89]

If an exception is thrown from the ICommunicationObject.Faulted event handler, execution becomes hung. It works fine on the old .NET Framework WCF.

Steps to Reproduce

1. Create a WCF client (I used dotnet-svcutil on a SOAP service)
2. Instantiate the client
3. Call client.Opening += (sender, args) => throw new Exception("Triggering Faulted state")
4. Execute a method on the client

Expected Result

• An exception is thrown and client.State becomes CommunicationState.Faulted

Actual Result

• Execution hangs

[StephenBonikowsky]

Thanks for reporting the issue @IGx89 we'll have someone take a look at this.

[Lxiamail]

@IGx89 Can you share the repro program?

[IGx89]

@Lxiamail Sure, easy enough to do! I've created one here, using a random SOAP service I found on Google: https://github.com/IGx89/OpeningExceptionExample

[Lxiamail]

@IGx89 Looks like a bug in WCF Core product. We appreciate you taking the time to report this problem. We are currently prioritizing problems that are impacting a broad set of our customers, so we may not be able to investigate this one immediately, but we will continue to monitor it.