x Want to participate? Join the group to interact
  • State Not Answered
  • Replies 2 replies
  • Subscribers 76 subscribers
  • Views 544 views
  • Users 0 members are here
Browse Forums
Announcements
105
topics
32
replies
General Discussion
6k
topics
18k
replies
Matthew Shaw

TomCat constantly hitting 70% CPU

Posted By

I noticed the recent post about CRM 2020 R2 and the need to manually adjusted logs. I thought this was timely as I was experiencing that problem on a new site. 

(1) Advisory: How to prevent excess Tomcat StdOut logging in Sage CRM 2020 R2 and Sage CRM 2021 R1 - Sage CRM Announcements, News, and Alerts - Sage CRM - Sage City Community

BUT even after I did all the steps and start restarted CRM. TomCat still was going crazy, the only way I could get TomCat to calm down again was to delete the Exchange Integration. 

  • 0

    Oh and I forgot to mention that at one point I disabled the exchange Integration and TomCat will still going crazy, so deleting it was the next step. 

  • 0 in reply to Matthew Shaw

    Thanks Matthew. I know CRM has made several recent changes to the Tomcat logging model, possibly including no longer writing out to the ..\User subfolder:
         C:\Program Files (x86)\Sage\CRM\CRM\Logs\Exchange Integration\User
    I've been working with CRM Support in NA and they think this might be a bug.

    Given all the changes, I've also suggested that someone in Dublin should write a KB article on these various changes and - most importantly - explain how a CRM Admin should troubleshoot issues with Exchange sync, e.g. skipped appointments and/or other errors.

*Community Hub is the new name for Sage City