'No Server Response Received (HTTP Response Code: 500)' Appears in the Data Entry Window for a Certain CRF.
(Doc ID 2727249.1)
Last updated on JANUARY 02, 2025
Applies to:
Oracle Clinical Remote Data Capture Option - Version 5.2.1 and laterInformation in this document applies to any platform.
Symptoms
1)
Post Production changes where made to the screening CRF.
2)
RDC Onsite TEST mode: when trying to test the Screening CRF, the following error appears when entering any data point:
"No server response received (HTTP Response Code: 500). This may be due to a temporary loss of network connectivity. Select 'Retry' to try again. Select 'Close CRF' to close the CRF. If you close the CRF, any unsaved changes may be lost".
3)
If the "retry" button is pressed then the following error appears:
Error
The data entry window has encountered an unexpected error and
will shut down. If the problem recurs, please report the following
information for diagnostic purposes:
Expected identifier, string or number
The data entry window has encountered an unexpected error and
will shut down. If the problem recurs, please report the following
information for diagnostic purposes:
Expected identifier, string or number
4)
The WebLogic '[server]_OPA_1.log' contains the below error stack:
####<Nov 4, 2020 5:34:34,113 AM CST> <Notice> <Diagnostics> <[server]> <[server]_OPA_1> <[ACTIVE] ExecuteThread: '16' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <[ID]> <[ID]> <[severity-value: 32] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-320068> <Watch "UncheckedException" in module "Module-FMWDFW" with severity "Notice" on server "[server]._OPA_1" has triggered at Nov 4, 2020 5:34:34 AM CST. Notification details:
WatchRuleType: Log
WatchRule: (log.severityString == 'Error') and ((log.messageId == 'WL-101020') or (log.messageId == 'WL-101017') or (log.messageId == 'WL-000802') or (log.messageId == 'BEA-101020') or (log.messageId == 'BEA-101017') or (log.messageId == 'BEA-000802'))
WatchData: MESSAGE = [ServletContext@1446610956[app:olsardc module:rdcadfsrnd path:null spec-version:3.1 version:5.2.1.2.2-b1]] Root cause of ServletException.
java.lang.StackOverflowError
at oracle.pharma.rdc.de.service.dcs.Block.setShowBlockValue(Block.java:584)
at oracle.pharma.rdc.de.service.dcs.Block.setShowBlockValue(Block.java:589)
at oracle.pharma.rdc.de.service.dcs.Block.setShowBlockValue(Block.java:589)
at oracle.pharma.rdc.de.service.dcs.Block.setShowBlockValue(Block.java:589)
at oracle.pharma.rdc.de.service.dcs.Block.setShowBlockValue(Block.java:589)
etc
WatchRuleType: Log
WatchRule: (log.severityString == 'Error') and ((log.messageId == 'WL-101020') or (log.messageId == 'WL-101017') or (log.messageId == 'WL-000802') or (log.messageId == 'BEA-101020') or (log.messageId == 'BEA-101017') or (log.messageId == 'BEA-000802'))
WatchData: MESSAGE = [ServletContext@1446610956[app:olsardc module:rdcadfsrnd path:null spec-version:3.1 version:5.2.1.2.2-b1]] Root cause of ServletException.
java.lang.StackOverflowError
at oracle.pharma.rdc.de.service.dcs.Block.setShowBlockValue(Block.java:584)
at oracle.pharma.rdc.de.service.dcs.Block.setShowBlockValue(Block.java:589)
at oracle.pharma.rdc.de.service.dcs.Block.setShowBlockValue(Block.java:589)
at oracle.pharma.rdc.de.service.dcs.Block.setShowBlockValue(Block.java:589)
at oracle.pharma.rdc.de.service.dcs.Block.setShowBlockValue(Block.java:589)
etc
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 |