Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Want to see what's currently in public preview? We've pulled it all together in one place. Check it out here
cancel
Showing results for 
Search instead for 
Did you mean: 
numutesi
Contributor II
Contributor II

Out of memory issue with tREST API call

Hi,

I am trying to call a tREST API that returns huge amount of data (more than 50k records) and getting "Out of Memory" error message. I tried increasing the JVM parameters (-Xms = 2048M and -Xmx=6144M) which worked for a few days but now the same issue reappeared.

I am storing the data into a file in /tmp folder.

numutesi_0-1733253198032.png

numutesi_1-1733253270483.png

The call to the API looks like this:

numutesi_2-1733253342039.png

 

 

What else should I do to make this work? I believe our API does not allow pagination.

Thank you!

Labels (3)
3 Solutions

Accepted Solutions
Sonal_Reddy_18
Partner - Contributor II
Partner - Contributor II

Can you try using the tHTTPClient component.

View solution in original post

numutesi
Contributor II
Contributor II
Author

I have never used it before but I can try. But what the difference that is going to make? 

View solution in original post

numutesi
Contributor II
Contributor II
Author

Hi,

So I did try to use the tHTTPClient component instead of tREST but the issue of insufficient memory is still there. The job works fine when I try to retrieve only one record!

So, now I really dont know what to do here!

View solution in original post

4 Replies
Sonal_Reddy_18
Partner - Contributor II
Partner - Contributor II

Can you try using the tHTTPClient component.

numutesi
Contributor II
Contributor II
Author

I have never used it before but I can try. But what the difference that is going to make? 

numutesi
Contributor II
Contributor II
Author

Hi,

So I did try to use the tHTTPClient component instead of tREST but the issue of insufficient memory is still there. The job works fine when I try to retrieve only one record!

So, now I really dont know what to do here!

Dave_Simo
Creator II
Creator II

Hello,

Try with the tHttprequest component maybe that will give a better result

Dave_Simo_0-1734450310707.png

And if that still doesn't work you should perhaps think about recovering the data by page (pagination) rather than trying to recover everything at once.

Best Regards,