Forum Discussion

harry's avatar
harry
Contributor
3 years ago

Using HTTP redirect enabled call gets stuck after execution of multiple times & doesn't move to next

Using HTTP redirect enabled call gets stuck after execution of multiple times & doesn't move to next step as 302 status code is returned for redirecting ( follow redirect 302 enabled)& no response is returned.

3 Replies

  • richie's avatar
    richie
    Community Hero
    Hey harry,

    Im not really understanding everything that youre sayinf but i the redirect is failing after either a certain numbrr of requests or a time interval its likely not a soapui/readyapu issue and its likely to be an issue at thr server end.

    Have you checked the logging at thr server end?

    Ta

    Rich
    • harry's avatar
      harry
      Contributor

      sorry for the late response. Looks like HTTP request (tstep) is something we have added newly in the automation for login step. Each test case we login & logout. Issue is due to this HTTP request iam seeing memory is consumed more & that is causing the hang. Iam not sure why this http request is causing too much memory usage on ready API.Is there away that after http request can i clear the session or cache or memory?

  • harry's avatar
    harry
    Contributor

    we had implement same http calling using gatline. we are not seeing the issue. So, ist not server side code issue. Completely related to Ready API consumption of memory. Earlier with Rest request  we use to user 8 gb memory setting. I did change now to 14 gb. Then it worked.Why memory consumption with http request is more on ready APi?