Soss TLog error 10054

#1
Please review this log entry

16/09/21 07:11:16 - Connection write reported expected termination (10054)
16/09/21 07:11:33 - Received new service connection from ... (15acd480 s 373 r 0 p 3112); 33 connections in use.
16/09/21 07:11:33 - Connection write reported expected termination (10054)
16/09/21 07:11:38 - Received new service connection from ... (15acd558 s 374 r 0 p 3112); 34 connections in use.
16/09/21 07:11:38 - Connection write reported expected termination (10054)
16/09/21 07:11:39 - Connection write reported expected termination (10054)
16/09/21 07:11:44 - Connection write reported expected termination (10054)
16/09/21 07:11:47 - Connection write reported expected termination (10054)
16/09/21 07:11:48 - Received new service connection from ... (1c65dff0 s 375 r 0 p 3112); 35 connections in use.
16/09/21 07:11:52 - Connection write reported expected termination (10054)
16/09/21 07:11:53 - Received new service connection from ... (6457120 s 376 r 0 p 3112); 36 connections in use.
16/09/21 07:11:56 - Received new service connection from ... (64571f8 s 377 r 0 p 3240); 37 connections in use.
16/09/21 07:11:58 - Connection write reported expected termination (10054)
16/09/21 07:12:00 - Received new service connection from ...(6268198 s 378 r 0 p 3240); 38 connections in use.
16/09/21 07:12:02 - Received new service connection from ... (62680c0 s 379 r 0 p 3240); 39 connections in use.
16/09/21 07:12:02 - Received new service connection from ... (1c65e1a0 s 380 r 0 p 3240); 40 connections in use.
16/09/21 07:12:04 - Connection write reported expected termination (10054)
16/09/21 07:12:06 - Connection write reported expected termination (10054)

Is their anyone with experience with this error code 10054?
My soss environments posted this across all 6 servers in the cluster
 

admin

Administrator
#1
Winsock error 10054 is a "connection reset by peer" event, and in the context of SOSS, this is usually caused by one of two things:
  • A client application abruptly terminated a connection, usually as a result of an application restart (e.g., IIS reset or host restart).
  • If the max_access_time parameter is set to a non-zero value in the client host's soss_client_params.txt, the client libraries will reset the connection if this timeout value is exceeded.
As the log files indicate, our service treats a Winsock error 10054 as an "expected termination", and unless you're experiencing other problems with your environment or application, these trace statements can be safely ignored.
 
Top