Can full TIM logging create a nospace or frequent TIM Restart condition in a production MTP?

Products

• CA Application Performance Management Agent (APM / Wily / Introscope)
• INTROSCOPE

Issue/Introduction

Description:

A production MTP is experiencing frequent restarts and the nospace column in protocolstats has large numbers. What are possible causes?

Solution:

Using full logging in a TIM or MTP in production is never recommended.

A nospace condition for an APM CE (CEM)-enabled TIM with full logging may occur, due to one of the following two conditions:

• The quality of the network traffic is producing large pcap files. (See TEC600295 for more information)
  
  
• Full logging under TIM Trace options In a production environment, causes the MTP to capture every network connection, HTTP request/response parameter/value pairs, session/login, and defect processing for EACH transaction. This will result in large PCAP files that will overfill the RAMdisk resulting in the nospace condition. This creates an accompanying TIM condition of frequent restarts.

Full logging may be used sparingly (Preferably off-hours to debug a condition). If logging must be kept on, use a trial and error approach to see which TIM Trace options do not cause the restart/RAMDisk nospace condition.

Environment

Release:
Component: APMCEM