Lynn,
Thanks for the information. Unfortuantley, I had already set the "IgnoreOnlyRequestErrorComponents" in the TIM settings with no effect on the missing and partial responses. Also, the documentation that is reference, I read before I posted to the community. We are addressing the root cause by looking at upgrading the network equipment to eliminate dedups. One other configuration that I modified was to reduce the Web Filters on the TIM to only necessary IP addresses; reducing the amount of data that the TIM analyzes. However, we still get a lot of out-of-order bytes, which will only be solved by getting rid of the dedups' at the network layer.
Also, the "Ignore" setting in CEM, only works to ignore the incident. The SLA is still calculated on the missing and partial responses. From a customer perspective, this gives the false impression that the application has problems. The application is working fine, but CEM is indicating an SLA of 40%, while Average Response times are well within norms. This could be solved, by having the "Ignore" setting not just stop incident creation, but to ignore the errors as part of the SLA, and to ignore sending it to the TESS agent in Introscope.
Is there anyother way to have CEM (until we get the additional network equipment) disable or truely ignore the Partial & Missing Responses, so that the SLA's are not calculated on Partial & Missing Responses, and the defects do not show in the TESS agent reporting to Introscope.
JW