After the server is started using Nodemanager, what is the value of "Heap Size Max" value do you see in WLS Admin Console under Environment--->servers---> <server_name>----->Monitoring--->Performance? If this value is nearer to 8GB, then you are fine.
The value shown in this page is the actual Max heap the process will use irrespective of the value it displays in "ps -ef | grep java" output.
Thanks for the above reply, if i get you clearly you say that actual memory can be found out from monitoring--> performance ..In similar fashion i found out the actual usage parameters by spanning jconsole utility ( i dont know whether this is the right check). From here (i mean jconsole) i could see the value is around 8G for me it looks to be the answer for the question i had .But here what i am interested to know is why this value is not getting shown when we run ps -ef | grep java from the command line of the server (linux).
1-Why is this value shown different?
2-Would you think that it should not be the same?
I think the managed server it is self is running on the machine ,so it should be obvious that to show same on the server end too.
One reason could be when you start your server using Nodemanager (you have StartScriptEnabled=true) and Nodemanager is using the StartScript you mentioned in your nodemanager.properties which has the MEM_ARGS set to -Xms256m -Xmx512m -XX:MaxPermSize=512m", this is the value it picks up and prints as java_arguments in the process output. The printed values should not be the only way to determine the memory that the process is using. Always, the memory (heap) usage that the Server runtime statistics display are the correct values that the JVM process picked up when it booted.