You notice that a large number of clients begin requesting full.zip definition downloads from the Symantec Endpoint Protection Manager (SEPM), which results in network performance issues. There appears to be no definition corruption on the clients. You may also notice that clients are failing to register with the SEPM.
Shortly before the issue starts, you notice the following error in scm-server-0.log
2014-05-28 12:04:52.127 THREAD 34 SEVERE: in: com.sygate.scm.server.task.ClientTransportInfoTask
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Thread.java:691)
You may also notice the following error in catalina.err:
Exception in thread "http-bio-9090-Acceptor-0" java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Thread.java:693)
at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:949)
at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1371)
at org.apache.tomcat.util.threads.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:176)
at org.apache.tomcat.util.threads.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:156)
at org.apache.catalina.core.StandardThreadExecutor.execute(StandardThreadExecutor.java:168)
at org.apache.tomcat.util.net.JIoEndpoint.processSocket(JIoEndpoint.java:525)
at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:230)
at java.lang.Thread.run(Thread.java:724)
The OutOfMemory errors listed above indicate that Tomcat does not have enough native memory available to generate a new thread. The Tomcat engine will open a new thread to process incoming HTTP requests. This results in the Tomcat HTTP acceptor(http-bio-9090-Acceptor) no longer processing incoming requests on 9090. This can include Delta requests for definitions, insertion of definitions into the database (either through LiveUpdate or manual JDB insertion), and client registrations.
Symantec is currently investigating this issue. As a workaround, you can perform the following performance tuning.