"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.
"No server response received (HTTP response code : 503)' always appears when trying to save a certain CRF ie
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.
The following error stack appears in the generated <random-number>.dump file :
oracle.pharma.rdc.de.exception.FailedOperationException: Error in DCAPI Module: SocketTimeout - Failed to read message from Dcapi Engine
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 : 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 : 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.
The 'DcapiHtml' debug file contains the following information which shows a considerable delay in the 'validateIndicatorsOnlineDcms' call :
Mon Dec 28 14:31:00.652 2015 : In RdcapiSaveChanges finished with validateIndicatorsOnlineDcms
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