TEC1165964: Enterprise Manager cannot reach TIM

Document created by Yanna Employee on May 26, 2016Last modified by J.J. Lovett on May 26, 2016
Version 2Show Document
  • View in full screen mode

Document ID:  TEC1165964

Last Modified Date:  4/6/2015
Authored By: Yanna

  • Products
    • CA Application Performance Management
  • Releases
    • CA Application Performance Management:Release:9.1.0
    • CA Application Performance Management:Release:9.1.1
    • CA Application Performance Management:Release:9.1.4
    • CA Application Performance Management:Release:9.1.5
    • CA Application Performance Management:Release:CA APM 9.5
    • CA Application Performance Management:Release:9.1 SP2
    • CA Application Performance Management:Release:9.1.6
    • CA Application Performance Management:Release:9.1.7
    • CA Application Performance Management:Release:9.5
    • CA Application Performance Management:Release:9.5.1
    • CA Application Performance Management:Release:9.5.2
    • CA Application Performance Management:Release:9.5.3
    • CA Application Performance Management:Release:9.5.5
    • CA Application Performance Management:Release:9.5.6
    • CA Application Performance Management:Release:9.6
    • CA Application Performance Management:Release:9.6.1
    • CA Application Performance Management:Release:9.7
    • CA Application Performance Management:Release:CA APM 9.6
    • CA Application Performance Management:Release:CA APM 9.7
  • Components
    • CEM SYSTEM SETUP
    • CEM TESS SYSTEM SETUP
    • INTEGRATION INTROSCOPE FOR SPECTRUM
    • CUSTOMER EXPERIENCE MANAGER
    • WILY CEM

 

Description:

Seeing message: "Enterprise Manager cannot reach TIM: Error retrieving response

http://#.#.#.#/wily/cem/tim/mod_python/timfiles/listDefects: Read timed out."

 

Solution:

For some reason, the TIM Collection Service (TCS) stops polling defects from the TIM\MTP. The result is a buildup of data on TIM side. Because of this huge amount of data processed,  read timed outs are happening.

At this point, the best thing to do is manually delete all the defects from the MTP\TIM box(/etc/wily/cem/data/out/defects.)

However, before doing this, disable the TIM from UI so it doesn’t keep generating new defects. Also stop the TCS EM while doing this. Then once defects are cleared, restart the EM, re-enable the TIM and there should be defects processed by EM.

Note:

If the defect data is important, then it is better to delete old defects based on time stamp from all the workers directories (at least match the value from “"Delete Defects after:" setting in “Incident Settings” page). This helps retain at least last X days defects data.

 

Search the Entire CA APM Knowledge Base

 

search-kb.jpg

Attachments

    Outcomes