You might have noticed two heap settings when you grep for a java processes on a linux machine. Below is an example:
This happens when StartScriptEnabled=true is enabled in nodemanager.properties file. The classpath from startWebLogic script and jvm arguments from the script setDomian.env will be used first and the values you specify on the Server Startup tab (In the Admin Console) will get appended to the end.
If two heap settings bothers or confuses you when you grep for the process on a linux machine, then this what you need to do to get rid of it.
1. Change the value of StartScriptEnabled=true to "StartScriptEnabled=false" in the nodemanager.properties file
This happens when StartScriptEnabled=true is enabled in nodemanager.properties file. The classpath from startWebLogic script and jvm arguments from the script setDomian.env will be used first and the values you specify on the Server Startup tab (In the Admin Console) will get appended to the end.
If two heap settings bothers or confuses you when you grep for the process on a linux machine, then this what you need to do to get rid of it.
1. Change the value of StartScriptEnabled=true to "StartScriptEnabled=false" in the nodemanager.properties file
2. Restart Nodemanager and the Managed server for the changes to take effect.
No comments:
Post a Comment