Missing response defects caused by empty request packets inserted between request and response.
Article ID: 19783
Updated On:
Products
Issue/Introduction
Description:
As per existing TIM implementation, if TIM sees any error while processing the request packets on an open connection then TIM assumes that packets/data inthat connection are corrupted and hence TIM simply ignores the remaining packets in that connection, otherwise reports/statistics get corrupted.
Solution:
To ignore only the request related to the error/bad packets and continue to process the remaining packets (i.e. request/response) on that connection add and enable property name/value: IgnoreOnlyRequestErrorComponents/1 (1 for enable, 0 for disable, by default this property is not listed and this feature is disabled)
To add and enable this property go to TIM System Setup page > Configure TIM Settings > Define a new value
This setting was added to address a particular situation where a web application receives empty request packets by design.
The TIMs default behavior is to interpret empty packets as corrupt and to report a missing response defect.
When the IgnoreOnlyRequestErrorComponents is 1, empty and corrupt request packets are ignored and are not reported as missing response defects.
If IgnoreOnlyRequestErrorComponents is 1 and empty or corrupt response packets are found, an entry is placed in the TIM log detailing on why the request is ignored including connection details.
For example, Tue Feb 28 12:03:22 2011 19136 Trace: ignoring request on connection ([172.16.214.7]:2479->[172.18.10.20]:443) due to - bad start line
Environment
Component: APMCEM
Feedback
