[BUG]System.Net.Sockets.SocketException in netcoreapp TargetFramework

Describe the bug Simple console application targeting net48 works without problem, retargeting to netcoreapp3.0 cause SocketException Exception or Stack Trace No connection could be made because the target machine actively refused it

To Reproduce Change TargetFramework from net48 to necoreapp3.0

Code Snippet

    class Program
    {
        static void Main(string[] args)
        {
            var serviceBusConnectionString = "yourConnectionString"
           var queue = "yourqueue";
            var messageReceiver = new MessageReceiver(serviceBusConnectionString, queue);
            messageReceiver.ServiceBusConnection.TransportType = Microsoft.Azure.ServiceBus.TransportType.AmqpWebSockets;
            var message = messageReceiver.ReceiveAsync().Result;

        }
    }

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Setup (please complete the following information):

• OS: [Windows 10]
• IDE : [Visual Studio 2019]
• Version 4.0.0

Additional context Add any other context about the problem here.

Information Checklist Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

• Bug Description Added
• Repro Steps Added
• Setup information Added

[davidsh]

@davidsh , I see that PR dotnet/corefx#41692 issue is marked with 5.0 milestone.

Changes are made first to master branch (5.0). I suspect that after that change is validated, then @stephentoub will create a release/3.0 PR for evaluation for servicing release of .NET Core 3.0.

[apraovjr]

@AndreiDegtiarev The fix would be released in .net-core 3.0.2 and 3.1 version