The first specifies how much memory SEPM should start with. There are two memory-related parameters that you can set. Nicely, it is possible to specify the amount of memory that SEPM allocates when running. – The basic principles of garbage collection are: 1) Find data objects in a program that cannot be accessed in the future 2) Reclaim the resources used by those object.Įssentially, SEPM is written in Java, and the Java Virtual Machine used to run it is running out of memory. – It deallocates memory used by objects at runtime automaticallly by using various algorithms to assess the reachability and life cycle of an object. – Its purpose is to reclaim garbage that is memory occupied by objects that are no longer in use by a program. – Garbage Collection (GC) is a type of automatic memory management. Dynamically allocated memory exists until it is released either explicitly by the programmer, or by the Garbage Collector (GC): It can be seen also as a way of distributing ownership of limited memory resources among many pieces of data and code. Dynamic memory allocation (also known as heap-based memory allocation) is the allocation of memory storage for use in a computer program during the runtime of that program. The amount of dynamic memory allocated to the Java Virtual Machine / Java Runtime Environment is insufficient. Here’s Symantec’s explanation of the problem: This lead me to the solution on Symantec’s website. Upon digging into the SEPM logs (specifically, the scm-server-0.log file, located in %programfiles%\symantec\symantec endpoint protection manager\tomcat\logs\), I saw a number of Java-related memory errors. The easy fix was to restart the server (or just the SEPM service), but that was a temporary solution, at best. Workstations would lose their connection to SEPM, SEPM would stop downloading (let alone distributing) updates, and attempts to login to SEPM would fail. It would work for a number of days, then randomly lock up.
Read on for the full details.Įssentially, SEPM was frequently locking up. I was able to track down the solution, and it greatly improved the performance of Symantec Endpoint Protection Manager (SEPM). I recently ran into an issue on a server running version 11 of Symantec Endpoint Protection (SEP).
0 kommentar(er)
