E9.2 Orchestration Endpoint Error's when JSON >4500 lines

DevJess

Member
We have an JDE orchestration endpoint that uses a form request to do standard insert into the GL Worktable (F0911Z1). When the JSON request for this endpoint exceeds 4500 lines then JDE response is ERROR, but when it is less than 4500 lines then the response is successful. What could be causing this?
 
The error (below) is very generic and we are not able to find any logs providing any additional detail. We have tried to adjust several settings such as the AIS and JAS instance Java heap min/max size, but we have not had any success yet.



{
"message": {
"InsertF0911Z1": {}
},
"exception": "Exception",
"timeStamp": "2022-08-03T09:19:20.759-0500",
"userDefinedErrorText": "",
"status": "ERROR",
"exceptionId": "a373e652-5b69-4368-b6c8-47f3fc0152b6",
"jde__simpleMessage": "InsertF0911Z1 failed:",
"jde__status": "ERROR",
"jde__startTimestamp": "2022-08-03T09:19:11.064-0500",
"jde__endTimestamp": "2022-08-03T09:19:20.765-0500",
"jde__serverExecutionSeconds": 9.701
}
 
If it was the Java heap, the error message would include something about the heap. A simple insert failure is not what I would expect to see for something related to number of records. I'll give you my fallback suggestion for what I do when I don't have a clue. Run it with debug logging on and then work your way through the AIS logs. The logs are painful to work through, but you can glean information from the inner workings to help solve some problems.
 
Back
Top