SEPM logs show a periodic Java IllegalThreadStateException within the AgentLogCollector task.


Article ID: 158057


Updated On:


Endpoint Protection


The scm-server logs on the Symantec Endpoint Protection Manager (SEPM) version server will periodically show an Unknown Exception. Further investigation of the log entry shows this to be a java.lang.IllegalThreadStateException within com.server.task.AgentLogCollector.

No issues are experienced except for this error appearing the logs.

Error Message in the scm-server-0.log will be similar to the following:

2013-05-17 20:18:49.122 SEVERE: Unknown Exception in: com.sygate.scm.server.task.AgentLogCollector java.lang.IllegalThreadStateException: process has not exited at java.lang.ProcessImpl.exitValue( at java.lang.ProcessImpl.waitFor( at com.sygate.scm.server.logreader.sep.LogHandler.washUSN( at com.sygate.scm.server.logreader.sep.LogHandler.process( at com.sygate.scm.server.task.AgentLogCollector.enumerateInbox(AgentLogCollector.ja va:289) at at java.util.TimerThread.mainLoop( at


The SEPM is incorrectly interpreting the thread status of the AgentLogCollector and reporting that it has been terminated improperly when it hasn't. The AgentLogCollector process completes successfully. This is a cosmetic issue as no functionality of the SEPM fails and all data is actually processed.


This issue is resolved in Symantec Endpoint Protection 12.1 RU2 and later. If upgrading to 12.1 is not possible, this error can be safely ignored.

This issue is currently reported as being present in the latest released build of Symantec Endpoint Protection 11.0, RU7 MP3. Symantec Development is aware of this and is currently evaluating the feasibility of correcting the issue within a future release of the SEP 11.0 product line. This document will be updated when further information is available.

Applies To

Reported on SEP 11.0 RU7 MP3. Other versions are likely to be impacted.