16.0 Detection Servers taking significantly longer be to connect

Products

• Data Loss Prevention Core Package

Issue/Introduction

After restarting Enforce services on DLP 16.0 Detection servers take almost an hour to come back to running.

You may also see Error 2600 communications error in the Enforce UI

Environment

Release : 16.0

Cause

In the logs you will see

SEVERE: Communication error. Unexpected error occurred while sending DIValidator_C updates to detection:filereader.
Shipment task has exceeded maximum idle time of 540,000 milliseconds!

Note can also be DataIdentifier_C instead of DIValidator_C and "detectionsvr" in "set detectionsvr:filereader:DIValidator_C" is the name of the detection server.

Eventually, detection servers return to a Reporting status. Servers that had to restart are delayed in starting while servers already running before Monitor Controller was restarted continue to run but just take time to report that they are running.

Resolution

This is a known issue with DLP 16.0. 

It has been corrected with MP2 HF1