My Oracle Support Banner

WIPgetXMLBuffer - Presenter Restarting Because It Has Not Reported Back In The Last 120 Seconds (Doc ID 2865128.1)

Last updated on APRIL 29, 2022

Applies to:

Oracle Documaker - Version 12.6.4 and later
Information in this document applies to any platform.

Symptoms

On : 12.6.4 version, Enterprise Edition


Unable to generate a scheduled batch PDFs files with a large number of transactions . When a batch contains less than 1000 transactions we can generate the PDF file. But when we reach a certain number(might be around 1000) we always get the two following errors in the database:


ERROR
-----------------------
Restarting the Presenter instance 1 with process id 2666 because it has not reported with a status message in the last 120 seconds. The last time the instance reported with a status message was 121 seconds ago.
DM12041: : FAP library error: Transaction:< >, area:<WIPLoadFormset> code1:<0>, code2:<0> message:<Unable to WIPGetXMLBuffer>.

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


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