My Oracle Support Banner

ODEE DWS Requests Randomly Timeout (Doc ID 2634888.1)

Last updated on FEBRUARY 03, 2020

Applies to:

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

Symptoms

On : 12.6 version, Enterprise Edition

ACTUAL BEHAVIOR
---------------
ODEE DWS Requests Randomly Timeout

We are seeing intermittent/random transaction timeouts throughout our environments and assembly lines. The transactions for all intents and purposes are successful, but the DWS SOAP requests timeout due to what appears a lack of response from ODEE.

Our configuration allows for PDF (immediate) and XER (scheduled)) batching options, and most transactions have both components. When a transaction times out, we see the RCPS records created, the PDF is created, the BCHS_RCPS records are staged/executed all with no errors. The Transaction is listed with a status code of 'P' in the TRNS table and TRNSTATUS is 416. However, the SOAP/DWS request randomly time outs with either SOAP response request time limit or the ODEE default timeout value (whichever is less).

For example, here is an example timing of events:

Tran Submitted: 2019-08-15 07:11:00.000

RCPS Start: 2019-08-15 07:11:00.983

BCHS_RCPS Start
XER: 2019-08-15 07:11:01.090
PDF: 2019-08-15 07:11:01.073

BCHS_RCPS Complete
XER: 2019-08-15 09:00:45.600 (scheduled)
PDF: 2019-08-15 07:11:01.597 (immediate)

Physical PDF Timestamp
PDF Created: 2019-08-15 07:11

ERRS Written: 2019-08-15 07:13:01.483

So, at exactly 120 seconds (the SOAP request value), a record is written to the ERRS table for error code: RCV0400400012. However, the transaction was successfully processed and scheduled a few seconds after submission. We are running version 12.6, but I came across patch: 25592347 for version 12.5 which is identical to our scenario. We are currently running the risk of duplication due to incorrect DWS response.

2019-08-15 00:13:01.445 PDT-FATAL-[Receiver_#1-T1-QueueReceiverWorker-1]-[QueueReceiverWorker.java:1162]-oracle.documaker.receiver.monitors.QueueReceiverWorker.logFatalErrorMessage: The operation has timed out for job 18: Timeout=120,000 milliseconds.

EXPECTED BEHAVIOR
-----------------------
transaction should not time out.
STEPS
-----------------------
The issue cannot be reproduced at will.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, transactions are timing out randomly.

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.