REST Binding Adapter Resulting In HTTP 500 Due To Empty Query Parameters
(Doc ID 2380217.1)
Last updated on MAY 15, 2023
Applies to:
Oracle SOA Suite - Version 12.2.1.3.0 and laterInformation in this document applies to any platform.
Symptoms
On : 12.2.1.3.0 version
REST Adapter resulting in HTTP 500 due to empty parameters
REST Binding component is sending empty as well as actual entered query parameters to REST endpoint.
Same composite is working fine in SOA version 12.1.3 and other releases.
If you enable "oracle.integration.platform.blocks.rest" TRACE:32 debug log you can see in diagnostic log the parameters that are being sent to REST endpoint.
?fNAME=&lNAME=&fNAME=firstName&lNAME=lastName
The parameters are added twice one with empty value and other with proper value.
Steps :
1. Add input data to test the composite : PRODUCER_ID=SOA, EVENT_NAME=TestEmailNotification, EVENT_TYPE=TestEvent, P_EBO_NV_PAIR=NULL
At REST endpoint system end the below parameters are received :
PRODUCER_ID=&EVENT_NAME=&EVENT_TYPE=&P_EBO_NV_PAIR=&PRODUCER_ID='SOA'&EVENT_NAME='TestEmailNotification'&EVENT_TYPE='TestEvent'&P_EBO_NV_PAIR=NULL
This is resulting in HTTP 500.
Changes
Upgrade to 12.2.1.3.0_GENERIC_RELEASE
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 |
| References |