After a Network Outage, Automatic Replication Stops and the Following Error is Seen in the ServerOutput: Exception in thread "Archive TransferMonitor" java.lang.OutOfMemoryError (Doc ID 1062877.1)

Last updated on AUGUST 07, 2024

Applies to:

Symptoms

On a 10.1.3.5.0 version, Content Server Automatic Replication is set up between contribution and consumption. A network problem occurred, and the following error was seen:

Transfer error for archive archivename in collection collection_name: Unable to connect to server servername on port 4444. The server is not available. java.net.ConnectException: Connection refused [ Details ]
An error has occurred

!$servername: !$!csTransferErrorForArchiveInCollection,archivename,collectionname!csUnableToConnect2,servername,4444!syExceptionType2,java.net.ConnectException,Connection refusedintradoc.common

The network issue was resolved and all servers were restarted, but archives are not getting exported to the consumption server.  The Archive TransferMonitor thread is missing on consumption when going to administration->systemAudit information ->Thread details, and the following error is seen in the administration ->system audit information ->server output page.

ERROR
-----------------------
Exception in thread "Archive TransferMonitor" java.lang.OutOfMemoryError
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.(ZipFile.java:203)
at java.util.zip.ZipFile.(ZipFile.java:84)
at intradoc.zip.ZipFunctions.extractZipFiles(ZipFunctions.java:232)
at intradoc.server.archive.TransferMon

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.