MOM EM becoming unresponsive every few days

Products

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

Issue/Introduction

APM MOM EM Service keeps crashing or becoming unresponsive every few days

[ERROR] [Carver data management] [Manager] Uncaught Exception in Enterprise Manager: In thread 'Carver data management' and the message is: java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
        at com.wily.introscope.server.enterprise.entity.fsdb.spoolfile.FastConverter$WholeNumberTimeslice.<init>(FastConverter.java:381)
        at com.wily.introscope.server.enterprise.entity.fsdb.spoolfile.FastConverter$IntTimeslice.<init>(FastConverter.java:455)
        at com.wily.introscope.server.enterprise.entity.fsdb.spoolfile.FastConverter.writeData(FastConverter.java:170)
        at com.wily.introscope.server.enterprise.entity.fsdb.spoolfile.FastConverter.doConvert(FastConverter.java:122)
        at com.wily.introscope.server.enterprise.entity.fsdb.spoolfile.FastConverter.convert(FastConverter.java:73)
        at com.wily.introscope.server.enterprise.entity.fsdb.spoolfile.SpoolToQueryConversionTask.doTask(SpoolToQueryConversionTask.java:66)
        at com.wily.introscope.server.enterprise.entity.fsdb.ADataFileTask.run(ADataFileTask.java:21)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)

Environment

Release : 10.7

Component : APM EM

Resolution

The problem was with EEM, which integrates with Office365 AD (Corporate Email) for authenticated access to APM. On the EEM/Office365 AD (Corporate Email) there was an overload of computational resources on the servers. EEM is being used in APM for authentication. We made changes to the EEM settings, and we have no problems with APM. The problem was solved with the adjustments made in the EEM environment that directly impacted the APM.