This content has been marked as final. Show 4 replies
The parameters you have set as JVM arguments under Server Start tab is used by nodemanager when the nodemanager has to start the specific managed server.
If you are concerned about seeing whether the Jvm arguments have taken effect,then you may have to start the weblogic server instance and check the stdout log file to validate the jvm arguments that have been picked up.
If you want to monitor the memory consumption like the various allocation within the java heap and utilisation,then there are various tools for doing the same.
Hope this helps!
The catch here is i am using the default way to start weblogic i.e. by starting the admin server and the managed server from the console. Now in such a case i can only see the memory of the admin server in the stdout and not managed server.
Assuming console stands for weblogic console,
You cannot start an admin server from the Weblogic console as the weblogic console is hosted on the Admin server and if you can only stop the Admin server through the weblogic console but cannot start it.
You can start and stop the managed server instance using the weblogic console but starting a managed server from the weblogic console requires nodemanager to be configured without which you cannot start the managed server from the Admin console.
The JVM arguments you might have specified can be inspected in the .out file of the specific managed server which is under your domains\XYZ_domain\servers\MS1\logs
Try to use Jconsole / visualVM to verify how much heap you have set for your specific weblogic server.