Symantec DLP Incident Persister fails to run after reboot
search cancel

Symantec DLP Incident Persister fails to run after reboot


Article ID: 236317


Updated On:


Data Loss Prevention Data Loss Prevention Enforce


After a reboot of the Enforce server, the Symantec DLP Incident Persister Service appears to start, but stops within a few minutes.

The IncidentPersister_0.log shows the following:

(SEVERE) Thread: 18 [org.apache.catalina.core.StandardService.addConnector] Failed to start connector [Connector[HTTP/1.1-9000]]
org.apache.catalina.LifecycleException: Failed to start component [Connector[HTTP/1.1-9000]]
 at org.apache.catalina.util.LifecycleBase.start(
 at org.apache.catalina.core.StandardService.addConnector(
 at org.springframework.boot.web.embedded.tomcat.TomcatWebServer.addPreviouslyRemovedConnectors(
 at org.springframework.boot.web.embedded.tomcat.TomcatWebServer.start(
 at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.startWebServer(
 at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.finishRefresh(
 at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(
 at org.springframework.boot.SpringApplication.refresh(
 at org.springframework.boot.SpringApplication.refreshContext(
 at com.vontu.incidenthandler.IncidentPersister.start(
 at com.vontu.incidenthandler.IncidentPersister.main(
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(
 at java.lang.reflect.Method.invoke(
Caused by: org.apache.catalina.LifecycleException: Protocol handler start failed
 at org.apache.catalina.connector.Connector.startInternal(
 at org.apache.catalina.util.LifecycleBase.start(
 ... 18 more
Caused by: Address already in use: bind
 at Method)
 at org.apache.coyote.AbstractProtocol.start(
 at org.apache.catalina.connector.Connector.startInternal(
 ... 19 more


The Tomcat connector configured to listen on port 9000 failed to start. The port may already be in use or the connector may be misconfigured.

Verify the connector's configuration, identify and stop any process that's listening on port 9000, or configure this application to listen on another port.


Symantec Data Loss Prevention 15.8 GA
Windows 2012 R2


Port 9000 is already in use.


A reboot of the server will free up the port.

If a reboot is not an option, or doesn't work, you can use the following steps to determine which service is using the port:
1. On the Enforce server, open Command Line and run the following command to collect the PID of the service using port 9000:

netstat -ano | find "9000"

Note:  the PID is the last number listed in the results.

2. Open Task Manager > Details tab > search for the PID. This will show you which service is using the port.
3. If the service is one that you have permission to stop, right-click on the service and end task.
4. Rerun the netstat command to confirm port 9000 is not being used.

5. Restart the Symantec DLP Incident Persister Service