how to increase xms and xmx size in message-processor

hi folks

i want to increase xms and xmx size 

by default it is min 512m and max 2048m now i want to change this min to 1024m and max to 4096

i am following this 2 article

https://www.googlecloudcommunity.com/gc/Cloud-Product-Articles/Apigee-Private-Cloud-Performance-Opti...

https://www.googlecloudcommunity.com/gc/Cloud-Product-Articles/Java-Xmx-Xms-for-Message-Processor/ta...

rohanjangid_1-1627647873745.png

and also i installed jconsole for heap monitoring 

rohanjangid_2-1627648048830.png

so in vm argument is showing heap min and max file 

so i followed 

https://www.googlecloudcommunity.com/gc/Cloud-Product-Articles/Apigee-Private-Cloud-Performance-Opti...

this article and done same steps but still heap size is not increase

 

thanks for any guidance or help

 

0 6 1,132
6 REPLIES 6

Did you refer below

https://docs.apigee.com/how-to-guides/configuring-heap-memory-size-message-processors

&

check using to confirm if it reflected. 

ps -ef | grep message-processor | egrep -o 'Xms[0-9a-z]+|Xmx[0-9a-z]+' | tr '\r' ' '

 

@API-Evangelist thanks for replying i followed that link and also confirm using grep but it is not reflected 

Checked in my local setup and looks normal as per document and works as expected.

Where are you updating the values? Hope you are aware of apigee configuration.

Make sure you are making changes in  /opt/apigee/customer/application/message-processor.properties & performing a rolling restarts.

During startup logs you can validate the heap settings as well.

Just FYI: Go thru below document and make sure you have the file exists with proper permissions..

https://docs.apigee.com/private-cloud/v4.19.06/how-configure-edge

If you still face issues please share little more information on your setup & snapshots of the .properties file but in general it should work.

 

Just fyi from your snapshot 4.19.06 is no more in support & should be upgraded soon.

@API-Evangelist  yes may be this is the reason i cross check all the steps it is working well but i am using v4.19

@rohanjangid - Obvious questions - 
Did you restart the MP component after modifying the parameters in the message-processor.properties file under  /opt/apigee/customer/application/  directory?

bin_setenv_min_mem=1024m
bin_setenv_max_mem=4096m


If yes, when you restarted the MP your startup logs should have shown the changed delta?  

And you can use the grep command to check the run time values. 

 

@mpurwar thanks for replying yes i restart MP and also confirm using grep but it is not reflected