My Oracle Support Banner

"No Server Response Received (HTTP Response Code: 503)" Appears When CRF Save Takes A Long Time (Due To Long Running 'Online' Validation/Derivation Procedures). (Doc ID 2095760.1)

Last updated on MARCH 01, 2023

Applies to:

Oracle Clinical Remote Data Capture Option - Version 5.0.1 and later
Information in this document applies to any platform.

Symptoms

1)
"No server response received (HTTP response code : 503)' always appears when trying to save a certain CRF ie

 

FYI:
The '(HTTP response code : 504)' can also be seen if a proxy server is being used and the proxy timeout is reached.
For example a 'Nginx Proxy Server' is being used and the configured value for the 'proxy_read_time setting' in the 'nginx.conf' file is exceeded i.e. 

 

2)
The following error stack appears in the generated <random-number>.dump file :

Exception Details:Error in DCAPI Module: SocketTimeout - Failed to read message from Dcapi Engine
oracle.pharma.rdc.de.exception.FailedOperationException: Error in DCAPI Module: SocketTimeout - Failed to read message from Dcapi Engine
    at oracle.pharma.rdc.de.service.dcs.DciFormData.doDocSave(DciFormData.java:2988)
    at oracle.pharma.rdc.de.service.dcs.DciFormData.doDocSave(DciFormData.java:2782)
    at oracle.pharma.rdc.de.service.dcs.DciFormData.processDocCommands(DciFormData.java:7862)
    at oracle.pharma.rdc.de.service.dcs.DciFormData.processCommand(DciFormData.java:8044)
    at oracle.pharma.rdc.de.service.dcs.DataCaptureService.performAction(DataCaptureService.java:328)
    at oracle.pharma.rdc.de.service.dcs.DataCaptureService.processCommand(DataCaptureService.java:169)
    at oracle.pharma.rdc.de.servlet.RuntimeController.doPost(RuntimeController.java:546)

 

3)
The 'DcapiExec' debug file contains the following information which shows a considerable delay in the saving process :

Mon Dec 28 14:04:49.801 2015 : ------------------
Mon Dec 28 14:04:49.801 2015 : Function := SaveChanges
Mon Dec 28 14:04:49.801 2015 : arg(0) := SAVE
Mon Dec 28 14:04:49.801 2015 : arg(1) := 1
Mon Dec 28 14:04:49.801 2015 : Before Calling SaveChanges
Mon Dec 28 14:04:49.801 2015 : Inside CallDcapiMethod, Function name is: SaveChanges
Mon Dec 28 14:04:49.801 2015 : Reset closed flag to 0
Mon Dec 28 14:31:00.652 2015 : Function SaveChanges returns 32null20151228143100
Mon Dec 28 14:31:00.652 2015 : function send(dcapiService->dcapi.jar) returns 31
Mon Dec 28 14:31:00.652 2015 : Waiting for new function calls...
Mon Dec 28 14:31:00.652 2015 : ------------------

and the below also appears :

Mon Dec 28 14:31:00.652 2015 : Failed to read message (or remote client has disconnected):
Mon Dec 28 14:31:00.652 2015 : The virtual circuit was terminated due to a time-out or other failure. The application should close the socket as it is no longer usable.

 

4)
The 'DcapiHtml' debug file contains the following information which shows a considerable delay in the 'validateIndicatorsOnlineDcms' call :

Mon Dec 28 14:04:50.659 2015 : ------- In validateIndicatorsOnlineDcms
Mon Dec 28 14:31:00.652 2015 : In RdcapiSaveChanges finished with validateIndicatorsOnlineDcms

Changes

 

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
Changes
Cause
Solution


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