Do you have any idea about why are we getting this problem in a 2.22 server while in an equivalent 2.20 server everything’s working fine (with the same amount of memory available for Tomcat)? Is this an api bug?
so, yes, in PSI we have several programs which metatadata needs to be downloaded using long API calls (throuth the DHIS2-SDK) resulting in really long json objects. But, as Ignacio said, we are getting an OutOfMemory exception in one of our servers. To give you an idea, that call generates a json object which size is about 3 MB → it downloads the metadata of a program that contains around 100 D.Elements, each dataelement has around 10 dataelement attriibutes and the program is activated in hundreds of org. units.
The server shows the following information:
memoryInfo: “Mem Total in JVM: 1552 Free in JVM: 874 Max Limit: 1552”,
Finally, the server is running a 2.22 DHIS2 version (revision 21773)…
However, we are not getting that error if we run the same API call in other server with the same memory configuration BUT running a 2.20 version (instead of 2.22).
So, do you have an idea of what is it happening here? Maybe are we close to the limit of memory of some object that for some reason is not being throwed in 2.20 but in 2.22?. Could it be a problem related just with the 2.22 version?
Also, we are going to work with programs of above 800 Data Elements (weird, we know) so I can easly think in objetcs of above 10 MB… Could it be a problem? What is the memory configuration that we need?
Do you have any idea about why are we getting this problem in a 2.22 server while in an equivalent 2.20 server everything’s working fine (with the same amount of memory available for Tomcat)? Is this an api bug?
this is just to inform you (I’m sure you’re already aware however) that using the recently available build 21778, the problem disappears. Thank you for this.
Do you have any idea about why are we getting this problem in a 2.22 server while in an equivalent 2.20 server everything’s working fine (with the same amount of memory available for Tomcat)? Is this an api bug?