Hi,
did you solve the problem?
We have the same phenomena. When the large structure contains null data, the program is called and data is passed (there are other containers too). When the large structure is filled, the zOS request contains zero bytes.
------------------------------
Frauke Bah
------------------------------
Original Message:
Sent: Mon December 21, 2020 10:51 AM
From: Shibu Kumar
Subject: Large POST Request failing when called from ZOS Connect Server
Hi Steve,
The JSON is within the limit of the COBOL definitions, because we can see the complete JSON created correctly in ZOS logs as well. But somehow ZOS Connect is not able to send anything in that case. I captured the web server logs (endpoint which accepts the requests and provides response), but we can see when it is smaller, it generated response and sends us the details. But for a larger JSON, web server is not receiving anything from ZOS Connect.
Also, when i try the same JSON request and endpoint in SOAPUI Tool, it works fine. So ,this is specific to ZOS Connect server.
Regards,
shibu kumar
------------------------------
Shibu Kumar Parambath
Louisville, KY
------------------------------
Original Message:
Sent: Mon December 21, 2020 10:43 AM
From: Shibu Kumar
Subject: Large POST Request failing when called from ZOS Connect Server
Hi Steve,
When i say JSON size is big, it doesn't mean that it exceeds any
swagger/COBOL definitions. it is within that definition limit. Also,
in ZOS Connect logs, we can see that the JSON is created correctly,
but ZOS Connect is not able to send anything to the web server. Not
sure if there is any limits for JSON length defined somewhere in ZOS
Connect server?
--
Thanks and regards,
Shibu Kumar,
Exton, PA
Contact me @ 1 224-425-7291
Original Message:
Sent: 12/21/2020 4:57:00 AM
From: Steve McAuliffe
Subject: RE: Large POST Request failing when called from ZOS Connect Server
Hi,
when you say the JSON size is increased is this beyond the field limits defined as part of the swagger/cobol created by zconbt? It sounds like you are exceeding a defined field size somewhere. There should be additional msgs around the 500 response in zOS Connect. If not put the api requester tracing on and see what that gives you.
------------------------------
Steve McAuliffe