Skip to content
Integration Technologies - JDE1 (MOSC)
MOSC Banner

how to handle the error about HTTP status code 444

edited January 2023 in Integration Technologies - JDE1 (MOSC) 4 commentsAnswered ✓

Hello everyone.

We would like to use the orchestration to be able to interface the business data between another system hosted on SAP commerce cloud. Recently, we had verified if the orchestration works correctly. We confirmed that it worked almost correctly, but sometimes, the orchestration ended with error indicating the status code 444.

In our environment, before calling the orchestration, SAP gets the access token from the Oracle Access Manager (OAM) by sending the request to the endpoint bellow.

https://{OAM_FQDN}/oauth2/rest/token

After this, SAP calls some orchestrations on JDE AIS server. Most of calling finish with success (status code 200). But sometimes, it fails with error and SAP receives the status code 444. I asked the SAP vender that how does the 444 error occur, and thay said that JDE must reject the access token incorrectly. But our verification, JDE seemed to handle the access token correctly. Additionally, SAP should receive the status code 401 when access token is invalidated.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Popular JDEdwards Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center