The Incident Persister service fails to start after an upgrade to DLP v11

book

Article ID: 160450

calendar_today

Updated On:

Products

Data Loss Prevention Enforce

Issue/Introduction

After upgrading to DLP version 11, the Incident Persister service fails to start on the Enforce server.

In some cases, IncidentPersister0.log contains the following error:

Feb 4, 2011 3:06:39 PM (SEVERE) Thread: 10 [com.vontu.util.jdbc.JDBCLogger.<clinit>] Failed to initialize JDBC Logging
java.io.IOException: Couldn't get lock for C:/Vontu/Protect/logs/debug/IncidentPersister_jdbc_%g.log

Other reported manifestations include issues with custom attribute lookups, including system events ("Response rule execution failed") and the following errors in IncidentPersister_0.log:

Apr 11, 2011 2:32:10 PM (SEVERE) Thread: 10 [com.vontu.incidenthandler.IncidentPersister.main] (INCIDENT_PERSISTER.6) An unrecoverable error occurred during the startup of the Incident Persister. The process will be terminated.
com.vontu.incidenthandler.command.enforce.ResponseRuleServiceException: Could not start CustomAttributeLookup.

Later in the log, the following error points to the ultimate cause:

Caused by: java.lang.NullPointerException
 at com.vontu.util.jdbc.JDBCLogger.isLoggable(JDBCLogger.java:51)
 at com.vontu.util.jdbc.LoggingStatement.executeQuery(LoggingStatement.java:192)
[etc.]

Resolution

This problem is caused by an invalid path for JDBC logging by the Incident Persister service; it occurs even if JDBC logging was not previously enabled. Correct the path in the following variable located in \Vontu\Protect\config\IncidentPersisterLogging.properties :

com.vontu.util.jdbc.JDBCLogHandler.Pattern

Note: This problem occurs on a system that was originally installed with version 8.0 or earlier, to a drive other than C:. See Etrack #1313250 for more information.