No connection could be made because the target machine actively refused it

  • Thread starter Thread starter gdhar
  • Start date Start date
G

gdhar

Guest
Hi there,

I have .net framework 2 remoting windows service that listens on a particular port. I see service is running properly and 300+ users are actively connected doing multiple calls. Randomly, it throws following exception stating not able to connect to the remote machine. I see my network is proper, port is properly open, machine is running and windows service is also in running state. Some users will get this exception and some will be too slow to get request processed. Is there any limit on # of remote connectivity, which I dont think the case is. Are there any other limits or settings that can help to troubleshoot this problem.


Could not connect to remote object: System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it <internal ip>:52000

Server stack trace:
at System.Net.Sockets.Socket.Connect(IPAddress[] addresses, Int32 port)
at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket(AddressFamily family)
at System.Runtime.Remoting.Channels.SocketCache.GetSocket(String machinePortAndSid, Boolean openNew)
at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.SendRequestWithRetry(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream)
at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)
at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)

Thanks in advance.




GB

Continue reading...
 
Back
Top