Incidents not persisting after restarting services.
search cancel

Incidents not persisting after restarting services.

book

Article ID: 405219

calendar_today

Updated On:

Products

Data Loss Prevention Core Package

Issue/Introduction

After restarting all services, you are able to log into the DLP console but no incidents are persisting to the database. 

Environment

The following error may be observed in IncidentPersister_0.log
(SEVERE) Thread: 31 [com.vontu.incidenthandler.IncidentPersister.main] Exiting incident persister process with error
org.springframework.context.ApplicationContextException: Failed to start bean 'incidentCommandEnvironment'; nested exception is java.lang.RuntimeException: com.vontu.command.loader.CommandRuntimeLoaderException: Error loading command instructions for command config "new-incident-commands".
 <redacted for readability>
Caused by: com.vontu.model.DatabaseConnectionException: org.apache.ojb.broker.PersistenceBrokerException: Used ConnectionManager instance could not obtain a connection
 <redacted for readability>
Caused by: org.apache.ojb.broker.PersistenceBrokerException: Used ConnectionManager instance could not obtain a connection
 <redacted for readability>
Caused by: org.apache.ojb.broker.accesslayer.LookupException: Could not get connection from DBCP DataSource
 <redacted for readability>
Caused by: java.sql.SQLRecoverableException: IO Error: The Network Adapter could not establish the connection
 <redacted for readability>
Caused by: oracle.net.ns.NetException: The Network Adapter could not establish the connection
 <redacted for readability>
Caused by: java.io.IOException: Connection timed out: connect, socket connect lapse 21036 ms. <oracle host> 1521 0 1 false
 <redacted for readability>
Caused by: java.net.ConnectException: Connection timed out: connect

Cause

A transient database connection error may have allowed Manager and Detection Server Controller to connect to the database while Incident persister was unable to causing the service to fail to start. 

Resolution

Ensure the Incident Persister service is started.