A 16.1 detection server is switching between Running, Connected, Disconnected and Unknown statuses. After restarting the SymantecDLPEnforceConnectorService service, it is running OK but the issue appears after some time. You also see the below entries in SymantecEnforceConnector0.log:
Mar 27, 2025 4:06:21 PM com.symantec.dlp.communications.common.activitylogging.JavaLoggerImpl log
WARNING: Stack array is empty. The following exception does not have a proper stack trace.
java.lang.Exception: java.lang.OutOfMemoryError: GC overhead limit exceeded
at com.symantec.dlp.communications.common.activitylogging.ConnectionLogger.getThrottler(ConnectionLogger.java:553)
at com.symantec.dlp.communications.common.activitylogging.ConnectionLogger.shouldSuppressHSL(ConnectionLogger.java:506)
at com.symantec.dlp.communications.common.activitylogging.ConnectionLogger.writeToLogFileIfNeeded(ConnectionLogger.java:473)
at com.symantec.dlp.communications.common.activitylogging.ConnectionLogger.writeToLogs(ConnectionLogger.java:459)
at com.symantec.dlp.communications.common.activitylogging.ConnectionLogger.onException(ConnectionLogger.java:1080)
at com.symantec.dlp.communications.common.activitylogging.AsynchronousConnectionLogger$OnExceptionTask.run(AsynchronousConnectionLogger.java:1276)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:750)
Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded
16.1
The EnforceConnector service may require more Java heap assigned to operate correctly.
Go to Advanced Settings of your detector, and double the value under UDS.EnforceConnector.MaxMemory to see if it resolves the issue.