I have a system that includes servers that allow remoting calls from a client with TCP as the underlying Tronsportlayr it usually But works like a charm, but if I do not extend the clients, the server starts randomly to close the TCP connection in the middle of the call.
This is really unexpected behavior ... do not get any exceptions me on the server side, only the client side exception:
System Net.Sockets.SocketException: a current connection forcibly remote host server was stopped by stack trace: Veda System.Net.Sockets.Socket.Receive (byte [] buffer, Int32 offset, Int32 size, socketFlags socketFlags) Ved System.Runtime. Remoting.Channels.SocketStream.Read (byte [] buffer, Int32 offset, Int32 size) Ved System.Runtime.Remoting.Channels.SocketHandler.ReadFromSocket (byte [] buffer, Int32 offset, Int32 count) Ved System.Runtime.Remoting. Channels.SocketHandler.Read (byte [] buffer, Int32 offset, Int32 count) Ved System.Runtime.Remoting.Channels.SocketHandler.ReadAndMatchFourBytes (byte [] buffer) Ved System.Runtime.Remoting.Channels.Tcp.TcpSocketHandler.ReadAndMatchPreamble ( ) Ved System. Runtime. Remoting channels. Tcp.TcpSocketHandler.ReadVersionAndOperation (UInt16 and Operation) V Ed System.Runtime.Remoting.Channels.Tcp.TcpClientSocketHandler.ReadHeaders () Ved System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.ProcessMessage (iMessage Messages, ITransportHeaders RequestHeaders stream requestStream, ITransportHeaders & amp; response header, stream & amp; Pratikriyapradrshn) ved Sistmkrntim. Remotection.Channel.binaryclientformer sync The syncprocess message (IMSAG msg) exception has been restored to [0]: ved system. From time to time. .Proxies.RealProxy.PrivateInvoke (MessageData & amp; msgData, Int32 type) Ved EBH.GuG.AgentKit.Transports.RemotingAgentHostEndPoint.SyncInvoke (agent, Int32 port)
If you are running on Windows XP / 2000/98?
Yes, XP 10 outbound are not inbuilt throttling mechanism socket stop (you are using to force to pay for Windows servers as servers and desktop machines) Suite The waste is that you can kill this limit.
Extra:
Perhaps your call callback so they are not created when an open socket work, which should improve your concurrent throughput.
Comments
Post a Comment