Error Message

Communication with Brava! Server error:

Failed to publish document.
HTTP response Code is 500, not 2XX
From Server: [#41057] Content processor error - 
java.util.concurrent.ExecutionException:
java.net.SocketException: Connection reset

 The converted document is not available when the request from the Brava Client is made.  
Since the document is available once the end user returns to that document, indicates the document conversion is successful and taking place on a different server from the Case Home Server.
The converted document is not being copied back to the Home Server in a timely manner.

- The issue is environmental and not a cause of any eDP/Clearwell coding.  This issue is commonly caused by installing eDP in a Distributed Architecture within an VM environment without reserving and locking the memory.  Involve the customer's Infrastructure and Security Teams to determine what may cause data transfer delays.
Refer to: 
How to Configure eDiscovery Platform on a Virtual Machine
https://isearch.veritas.com/internal-search/en_US/article.100038279.html
 

Workarounds:
1. For Native View conditions, run the Cache job on the case of concern.  This will not resolve the Production View, since the Production View conversion is made upon the initial request (no cache job available for production View)

2. Leave only the Case Home as the Review Node for this case.

When attempting to review an item in either Native or Production View the 'Communication with Brava! Server error:' error appears.
Once moved off that document and returned, the proper View is present.