Friday, 13 September 2019
Oracle Integration REST HTTP/1.1 500 Internal Server Error
Developing new cloud interfaces you will often get the HTTP/1.1 500 Internal Server Error. And the error details sometimes gives you the root cause for the error. Like example -
Error Creating Supplier :HTTP/1.1 500 Internal Server Error: env:Server <Supplier WebServiceOperation="createSupplier" Supplier="New Supplier" SupplierNumber="12345" SupplierId="">
<SupplierAddresses Operation="CREATE" AddressId="" AddressName="ADD123">
<Rejection>The address is not valid. At least one of the address attributes failed validation. Review the address format and geography setup for more details.</Rejection>
</SupplierAddresses>
But in many cases it does not give you a detailed error message. In that case most likely the error is with the incorrect xml tags being used in the payload.
Example from supplier site payload -
True/sup:PayPurposeFlag>
If you notice carefully < was missing after the value(True). So check the payload carefully and ensure you are using the correct tags.
So the below tag might also cause the same error. (sup: is missing from the tags)
True/
Happy Integrating.
Subscribe to:
Post Comments (Atom)
Integrations Lead - Lessons learnt
Integrations have been my passion for a while but like anything tech there is no credit given when things go right but always heaps of pres...
-
For most outbound interfaces bursting to content server and then picking the file from UCM is the best approach for large extracts. Default...
-
While developing Cloud integrations I could not find a single place for all details like InterfaceID or jobdefinitionname or job name etc. ...
-
You can use valueset(Ex-ORG_LEVEL1) to use the query table functionality in Fast Formulas. Below is sample how you pass parameters(P_ORG_ID)...
nice blog.
ReplyDeleteBig Data Hadoop Course
Good Article, Alots of information provided, Thanks for sharing this information.
ReplyDeleteBig Data Hadoop Course