Memory resources may be reduced to a low threshold or even become unavailable when exporting a large quantity of items which include large objects such as calendar items or appointments.  Increasing the available page memory and lowering the process threads will enable the Enterprise Vault server enough time to decompress the message and convert the items for an export.
 
When too many production threads are working and the SQL server is out of connection sockets, the threads collide with each other and are forced to sleep for a period of time.  If a thread fails to contact the SQL connection socket five consecutive times, the thread generates event errors such as SQL timeouts or deadlocks and terminates the export.  This termination will be followed by a cascade of errors from the subsequent threads, which are not able complete their jobs because of their dependence on the failed thread.

The "sleeping" of the Production Threads slows down all processes. Lowering the Production Threads setting and allowing all threads to complete their jobs without sleeping will increase the overall performance of the export job.

Note: A thread can sleep up to four times consecutively without an error being logged.

 

The "Number of Production Threads" setting has a default value of 25 threads.  The recommendation is to set this value to 10 and test exports.  If successful, the thread value can be increased slightly.  If the errors return, lower the thread value until exports are successful.

How to change the Number of Production Threads setting:
 

a. Open the Discovery Accelerator web page

 

b. Within DA navigate to Application Administration > System Configuration > Export/production.

 

c. Change the Number of Production Threads from 25 to 10

 

d. Apply the changes

 

e. Restart Customer Background Tasks or Accelerator Manager Service