What could be one of the causes of the "TCP Message timed out" error? Can one of the causes be, the message stays in the queue for too long after SiteMinder receives it and it times out?

Document ID : KB000012403
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

This question/answer below relates to the fact that in this type of TCP time out scenario, the trace log can  show a messages like CSm_Auth_Message::AnalyzeAgentAuthMessage that rarely takes a long time to  complete.  

At the same time you received the TCP timed out message, the CSm_Auth_Message::AnalyzeAgentAuthMessage  took a long time to  complete in this type of scenario.

Note - The TCP time out is not the cause of CSm_Auth_Message::AnalyzeAgentAuthMessage  taking  a long time to complete. It is just reflection of the CSm_Auth_Message::AnalyzeAgentAuthMessage  taking a long time to  complete.

This question/answer -  answers  one of  part of the flow when this type of scenario happens.  

Question:

What could be one of the causes of the "TCP Message timed out" error?

Can one of the causes be the message stays in the queue for too long after SiteMinder receives it and it times out?

It looks like a worker thread issued this error immediately after it dequeued a message

Answer:

Below explains the process of the message in the queue after SiteMinder receives it. The reasons for the actual TCP time out could be many. Mainly network related, non siteminder related.

  • A pool of worker threads is utilized to handle requests from the Web Agent. A reactor thread handles the initial connection from all incoming requests and passes them into a queue serviced by the worker threads. The position in the queue can differ depending on the type of incoming request 
  • The web agent should time out earlier than the message in the queue would. The agent would retransmit the message possibly to another policy server 
  • This is why we made the -flushrequests command available. 
  • Back on the PolicyServer, if the normal priority messages timed out in the Policy Server queue, the [TCP Message timed out. It will be discarded.] 

                        

  • Message is logged and the request is discarded from the queue. This TCP timeout is govern by the RequestTimeout parameters  defined in the HCO
  • The RequestTimeout parameters, which are set in the Host Configuration file (HCO), SmHost.conf.
  • Settings in the Host Configuration File apply only when the trusted host initializes. Once the trusted host initializes, the settings in the Host Configuration Object take effect.
  • Request Timeout.   Use the RequestTimeout parameter to specify the number of seconds that the trusted host should wait before deciding that a Policy Server is unavailable. This setting allows you to optimize the response time of the Web server. The default value is 60 seconds.  
  • Note: If the Policy Server is busy due to heavy traffic or a slow network connection, you may want to increase the RequestTimeout value.