i'm searching for the attribute "CommittedVirtualMemorySize" in the weblogic model but can't find it.
"CommittedVirtualMemorySize" in the weblogic model but can't find it.
--> getAttribute(operatingSystemMXBean, "CommittedVirtualMemorySize")
Maybe there is another identifier available. I need to monitor assigned native memory.
From the bea console i have the following columns inside a jmx-weblogic_OperatingSystem table:
In the Foglight Weblogic Model i can find something like:
The amount (in bytes) of physical memory that is currently being used on the host computer.
The value describes the memory that is being used by all processes on the computer, not just by the Virtual Machine."
The amount (in bytes) of physical memory on the host computer.
The value does not include memory that an operating system makes available through swap space on a disk or other types of virtual memory."
How can i identify the value for "CommittedVirtualMemorySize" and where do i find it in the JMX cartridge ?
The out of the box template Models we have with the JMX cartridge show important information BUT not all the information that is there in the JMX tree. When you create a JMX agent for weblogic you can copy the Weblogic model to a new model that the agent use and then edit your new model and add additional JMX Mbeans and attributes that are visible in the JMX tree.
i've searched in my exported weblogic model.
Does an export contain a full JMX Mbean tree or only the activated once ?
What you see in the exported weblogic model is only the information that we are trying to collect, not the full JMX Mbean tree.
When you edit the server model you can refresh the list of mbeans based on what is visible from the server.
When you are looking at the JVM information there is an operating system tab, do you see it and the information in it? We may get this information out of the box from the JVM MXBean
thank you for your hints !
when i have a look at one of our weblogic environments i miss these charts:
Does it depend on the weblogic model ?
Can you please check if this KB article corrects the problem?
JMX agent not showing jvm data
Oracle WebLogic normally uses its own MBean Server which is separate from the Platform MBean Server and only provides remote access to its own MBean Server. As aresult, the JMX agent is unable to collect JVM data.
How to enable this:Oracle WebLogic provides an option in the Domain -> General -> Advanced configuration page, which forces WebLogic to use the Platform MBean Server for itsown MBeans instead of a separate MBean Server. This option is turned on by default by WebLogic 10.3.3 and higher. Versions prior to 10.3.3 need to be changed. Enabling this option on allows the JMX agent to collect both WebLogic MBean data as well JVM data.
For more information you can read Oracle Weblogic documentation
we have several weblogic 10.x and 11g environments with
where i have
and some servers where the Mbean Server is completely disabled with no chart available.
But my final question:
Is "CommittedVirtualMemorySize" the same like "Heap used and Capacity" ?
CommittedVirtualMemorySize" the same like "Heap used and Capacity" ?
I'm confused about the different charts of the above transcipt e.g. "Heap used and committed" as well as "Heap Usage"
the above transcipt e.g.
"Heap used and committed" as well as "Heap Usage"
or "Heap used and Capacity" in "Custom Applications Monitor" --> "Mbean Server".
"Heap used and Capacity"
Does the flow chart kind vary with setting of the weblogic "Mbean Server" switch ?
Checking Oracle docs it looks like heap info and CommittedVirtualMemorySize are coming from different MBeans, if I read this correctly it looks like one is looking at the JVM itself while the other is looking at things from the OS standpoint.
CommittedVirtualMemorySize are coming from different MBeans, if I read this correctly it looks like one is looking at the JVM itself while the other is looking at things from the OS standpoint.
is for management interface for the memory system of the Java virtual machine.
is for Platform-specific management interface for the operating system on which the Java virtual machine is running.
In reply to benny:
More about....Java Memory Management