Error: "Shipment task has exceeded maximum idle time of 540,000 milliseconds" with Communication error, Code: 2600
search cancel

Error: "Shipment task has exceeded maximum idle time of 540,000 milliseconds" with Communication error, Code: 2600

book

Article ID: 258697

calendar_today

Updated On:

Products

Data Loss Prevention Core Package

Issue/Introduction

 The following error is reported in the Enforce Console:

Server or Detector

Enforce Server

 

Host

127.0.0.1

 

Message

Code

2600

Summary

Communication error

Detail

Unexpected error occurred while sending Policy_C updates to endpoint 7 dlpservername:filereader.
Shipment task has exceeded maximum idle time of 540,000 milliseconds!
Please look at the detection server controller logs for more information.

The following errors are seen in the IncidentWriter0.log on the DLP Detection Server:

  • WARNING: Failed to send a heartbeat. Shipment task has exceeded maximum idle time of 540,000 milliseconds!
  • WARNING: ShippingTask(controller-server, Structured Data Push, Heartbeat_C, 52636): Shipment task has exceeded maximum idle time of 540,000 milliseconds!

 

Resolution

Change the default acceptTimeout parameter in each DLP Detection Server communication.properties file located in the config folder:

# Timeout (milliseconds) for accept operations.
# Used by the BoxMonitor only.
acceptTimeout = 1200000

The communication.properties file is located on each Detection server, not on the Enforce Server. 
This file is located in" <dir>\Program Files\Symantec\DataLossPrevention\DetectionServer\<version>\Protect\config. 
No ramifications are expected when changing this parameter.
After making this change, recycle the services on each Detection Server.