search

kerryjiang / WebSocket4Net

A popular .NET WebSocket Client
752 stars 272 forks source link

Sending big messages failing #125

Closed bPoller2810 closed 6 years ago

bPoller2810 commented 6 years ago

Server is implemented in Supersocket.Websocket Client is implemented in Websocket4net (all projects built from sources, except Websocket4net client engine refernce)

If i try to send big messages (multible kb in size) i run into this exception

System.IO.IOException: 228/5000 Data can not be read from the transmission connection: An existing connection was closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was closed by the remote host

bei System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult) 
bei System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult) 
--- Ende der internen Ausnahmestapelüberwachung --- 
bei System.Net.Security._SslStream.EndRead(IAsyncResult asyncResult) 
bei System.Net.Security.SslStream.EndRead(IAsyncResult asyncResult) 
bei SuperSocket.ClientEngine.AuthenticatedStreamTcpSession.OnDataRead(IAsyncResult result) in C:\Data\temp\SuperSocket.ClientEngine-master\Core\AuthenticatedStreamTcpSession.cs:Zeile 104.    bei System.Net.Security._SslStream.EndRead(IAsyncResult asyncResult) 
bei System.Net.Security.SslStream.EndRead(IAsyncResult asyncResult) 
bei SuperSocket.ClientEngine.AuthenticatedStreamTcpSession.OnDataRead(IAsyncResult result) in C:\Data\temp\SuperSocket.ClientEngine-master\Core\AuthenticatedStreamTcpSession.cs:Zeile 104.

i tried to increase: server size send and receive buffer client side receive buffer

slowly running out of ideas how to fix this issue.

edit: as soon as the message reaches 16300 chars in length i got the crash. 16299 works fine.

bPoller2810 commented 6 years ago

My bad after messing around with some settings i finaly localized my problem server side in MaxRequestLength.