Hi All,
Thanks for the reply. But, here the problem is not with the payload size, because API works fine with huge payload. I checked payload size, and there is no issue with that.
Further i tried to investigate more and found this issue seems to be API Plan Fragment, where there is a limitation of requests per day per API. Because, all these errors occur only at the end of the day. So, I am not sure why. Can anyone have any idea why these errors occur at the end of the day or can say start of any day(around 12AM)?
Another thing, the error is not limited to only one API, it is for many APIs.
Please suggest me what could be the issue?
Ravish
Original Message:
Sent: 04-20-2020 05:27 AM
From: Ronald Dsouza
Subject: Re: Unable to get request XML: Stream timeout
Hi There,
Community Ref: https://community.broadcom.com/communities/community-home/digestviewer/viewthread?MID=779205
Here is KB article to look at for Size related issue
https://comm.support.ca.com/kb/api-gateway-optimizing-for-large-files-and-messages/kb000042880
Stream timeout are usually due to large response received from the backend server that is over the timeout period. Mostly adjusting the timeout period sort the problem
Try hitting the server directly to get an estimate of expected size and time. Then you can adjust you policy to meet their requirement
Finally, you can also use the option of streaming
https://community.broadcom.com/communities/community-home/digestviewer/viewthread?MID=754654
------------------------------
Pre-Sales Consultant
CA Southern Africa
Original Message:
Sent: 04-17-2020 07:37 AM
From: Ravish Kumar
Subject: Re: Unable to get request XML: Stream timeout
Hi,
I have same issue. Actually, I am not sure if I am getting correct request payload from the source, because request payload contains
Unable to get request XML: Stream timeout
Can you please guide what should be the solution? I assume here as payload would be bit huge. Does huge payload size cause issues in processing? Is it the main cause of the connection reset?
Thanks,
Ravish
Original Message:
Sent: 12-17-2018 12:36 PM
From: Stephen Hughes
Subject: Re: Unable to get request XML: Stream timeout
Good morning,
The best place to start is to see what is happening to the back-end latency and how the HTTP Routing assertion is configured. It is best to fail fast so that the client is aware so setting the connection timeout to around 500ms, read timeout to between 2-5 seconds, and retries to 0. If the request has a longer response time from the back-end then look to increase the read timeout. From there review the client timeout and all the devices in between but this is normally only a concern if the request are taking more than 60 seconds but still worth reviewing.
Also a review of the other integration that happen in policy like if authentication calls OAuth / LDAP provider or JDBC connections that are long running. Ultimately this error is when the client tears down the connection as it has run too long.
Sincerely,
Stephen Hughes
Broadcom Support