1 --

     2 --

     3 --

     4 -- Copyright (c) 2004, 2017, Oracle and/or its affiliates. All rights reserved.

     5 -- DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.

     6 --

     7 -- This code is free software; you can redistribute it and/or modify it

     8 -- under the terms of the GNU General Public License version 2 only, as

     9 -- published by the Free Software Foundation.  Oracle designates this

    10 -- particular file as subject to the "Classpath" exception as provided

    11 -- by Oracle in the LICENSE file that accompanied this code.

    12 --

    13 -- This code is distributed in the hope that it will be useful, but WITHOUT

    14 -- ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or

    15 -- FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License

    16 -- version 2 for more details (a copy is included in the LICENSE file that

    17 -- accompanied this code).

    18 --

    19 -- You should have received a copy of the GNU General Public License version

    20 -- 2 along with this work; if not, write to the Free Software Foundation,

    21 -- Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.

    22 --

    23 -- Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA

    24 -- or visit www.oracle.com if you need additional information or have any

    25 -- questions.

    26 --

    27 --

    28 -- The JVM-MANAGEMENT-MIB Module

    29 --

    30 -- See jvmManagementMIB MODULE-IDENTITY for a description overview.

    31 -- See conformance statements for mandatory objects

    32 --

    33 

    34 JVM-MANAGEMENT-MIB DEFINITIONS ::= BEGIN

    35 

    36 IMPORTS

    37     MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Counter32, Gauge32,

    38 	Integer32, Counter64, enterprises

    39         FROM SNMPv2-SMI

    40     DisplayString, TEXTUAL-CONVENTION, RowPointer

    41         FROM SNMPv2-TC

    42     MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP

    43         FROM SNMPv2-CONF;

    44 

    45 -- Module Identity

    46 ------------------

    47 

    48 jvmMgtMIB MODULE-IDENTITY

    49     LAST-UPDATED "200403041800Z"

    50     -- Format is "YYYYMMDDhhmmZ"

    51     ORGANIZATION "Sun Microsystems, Inc."

    52     CONTACT-INFO "Sun Microsystems, Inc.

    53                   4150 Network Circle

    54 		  Santa Clara, CA 95054

    55 		  1-800-555-9SUN or

    56 		  1-650-960-1300

    57 		  http://www.sun.com

    58 		  or contact your local support representative"

    59     DESCRIPTION

    60             "Copyright 2004 Sun Microsystems, Inc. All rights reserved.

    61 

    62              This module defines the MIB that provides access to the

    63 	     Java[tm] Virtual Machine monitoring data.

    64 	     This module is derived from the Java[tm] programming language APIs

    65              described in the java.lang.management package of

    66              Java[tm] 2, Standard Edition, 5.0.

    67 

    68 	     See the Java programming language APIs of JSR 163 for

    69              'Monitoring and Management of the Java[TM] Virtual Machine'

    70              for more details.

    71 

    72 	     Where the Java programming language API uses long, or int,

    73              the MIB often uses the corresponding unsigned quantity -

    74              which is closer to the object semantics.

    75 

    76              In those cases, it often happens that the -1 value that might

    77              be used by the API to indicate an unknown/unimplemented

    78              value cannot be used. Instead the MIB uses the value 0, which

    79              stricly speaking cannot be distinguished from a valid value.

    80              In many cases however, a running system will have non-zero

    81              values, so using 0 instead of -1 to indicate an unknown

    82              quantity does not lose any functionality.

    83 	    "

    84     REVISION     "200403041800Z"

    85     -- Format is "YYYYMMDDhhmmZ"

    86     DESCRIPTION

    87             "

    88             JVM-MANAGEMENT-MIB - JSR 163 Final Release 1.0

    89             "

    90 

    91     ::= { standard jsr163(163) 1 }

    92 

    93 

    94 -- Enterprise OIDs

    95 ------------------

    96 

    97 --        internet          OBJECT IDENTIFIER ::= { iso(1) org(3) dod(6) 1 }

    98 --        private           OBJECT IDENTIFIER ::= { internet 4 }

    99 --        enterprises       OBJECT IDENTIFIER ::= { private 1 }

   100 	sun	  	  OBJECT IDENTIFIER ::= { enterprises 42 }

   101 	jmgt		  OBJECT IDENTIFIER ::= { sun products(2) 145 }

   102 	-- experimental      OBJECT IDENTIFIER ::= { jmgt 1 }

   103         standard          OBJECT IDENTIFIER ::= { jmgt 3 }

   104 

   105 ----------------------------------------------------------------------------

   106 -- Textual Conventions

   107 ----------------------

   108 --

   109 -- Note: Some of the TEXTUAL-CONVENTIONs defined in this module are

   110 --       OCTET STRING with a 1023 size limitation (SIZE(0..1023)).

   111 --

   112 -- As per RFC2578, section 7.1.2.  OCTET STRING:

   113 --

   114 --       "The OCTET STRING type represents arbitrary binary or textual data.

   115 --        Although the SMI-specified size limitation for this type is 65535

   116 --        octets, MIB designers should realize that there may be

   117 --        implementation and interoperability limitations for sizes in

   118 --        excess of 255 octets."

   119 --

   120 -- As a consequence an agent implementing this MIB may decide to

   121 -- restrict this maximum size to a lesser value than 1023, provided that

   122 -- it makes it clear in an AGENT-CAPABILITY statement.

   123 --

   124 ----------------------------------------------------------------------------

   125 

   126 JvmUnsigned64TC ::= TEXTUAL-CONVENTION

   127     STATUS       current

   128     DESCRIPTION

   129            "A non-negative 64-bit bit integer, without counter

   130             semantics."

   131     -- We have cloned the Unsigned64TC defined in RFC 2564 rather

   132     -- than importing it because the JVM-MANAGEMENT-MIB and the

   133     -- APPLICATION-MIB are not related.

   134     --

   135     REFERENCE "RFC 2564 - APPLICATION-MIB, Unsigned64TC."

   136     SYNTAX Counter64

   137 

   138 

   139 JvmJavaObjectNameTC ::= TEXTUAL-CONVENTION

   140     DISPLAY-HINT "255a"

   141     STATUS       current

   142     DESCRIPTION

   143           "An Object Name, as implemented by the java.lang.management API,

   144 	  which identify a runtime Object (e.g. a Class Loader, a

   145           Memory Manager, etc...).

   146 	  The name is assumed to be unique in the scope of the object's

   147 	  class.

   148 

   149 	  This object syntax is equivalent to a DisplayString, but with a

   150           a 1023 bytes size limits (instead of 255 for a DisplayString).

   151 

   152 	  Note that the SNMP agent may have to truncate the string returned

   153           by the underlying API if it does not fit in this type.

   154 	  (1023 bytes max).

   155 	  "

   156     SYNTAX       OCTET STRING (SIZE (0..1023))

   157 

   158 JvmPathElementTC ::= TEXTUAL-CONVENTION

   159     DISPLAY-HINT "255a"

   160     STATUS       current

   161     DESCRIPTION

   162           "A file or directory element in a PATH/CLASSPATH/LIBRARY_PATH

   163            structure.

   164 

   165 	  This object syntax is equivalent to a DisplayString, but with a

   166           a 1023 bytes size limits (instead of 255 for a DisplayString).

   167 

   168 	  Note that the SNMP agent may have to truncate the string returned

   169           by the underlying API if it does not fit in this type.

   170 	  (1023 bytes max).

   171 	  "

   172     SYNTAX       OCTET STRING (SIZE (0..1023))

   173 

   174 JvmArgValueTC ::= TEXTUAL-CONVENTION

   175     DISPLAY-HINT "255a"

   176     STATUS       current

   177     DESCRIPTION

   178           "A string representing an input argument.

   179 

   180 	  This object syntax is equivalent to a DisplayString, but with a

   181           a 1023 bytes size limits (instead of 255 for a DisplayString).

   182 

   183 	  Note that the SNMP agent may have to truncate the string returned

   184           by the underlying API if it does not fit in this type.

   185 	  (1023 bytes max).

   186 	  "

   187     SYNTAX       OCTET STRING (SIZE (0..1023))

   188 

   189 JvmVerboseLevelTC ::= TEXTUAL-CONVENTION

   190     STATUS       current

   191     DESCRIPTION

   192 	"Defines whether the verbose flag for a feature is active.

   193 	 verbose: the flag is on.

   194 	 silent:  the flag is off.

   195 	"

   196     SYNTAX INTEGER { silent(1), verbose(2) }

   197 

   198 

   199 JvmImplSupportStateTC ::= TEXTUAL-CONVENTION

   200     STATUS       current

   201     DESCRIPTION

   202 	"Defines whether a feature is supported or not.

   203 	"

   204     SYNTAX INTEGER { unsupported(1), supported(2) }

   205 

   206 JvmImplOptFeatureStateTC ::= TEXTUAL-CONVENTION

   207     STATUS       current

   208     DESCRIPTION

   209 	"Defines whether an optional feature is supported, enabled,

   210 	 or disabled.

   211 

   212          An optional feature can be:

   213 

   214 	 unsupported: The JVM does not support this feature.

   215 	 enabled    : The JVM supports this feature, and it

   216 	              is enabled.

   217 	 disabled   : The JVM supports this feature, and it

   218 	              is disabled.

   219 

   220          Only enabled(3) and disabled(4) may be supplied as values to a

   221          SET request. unsupported(1) can only be set internally by the

   222          agent.

   223 	 "

   224     SYNTAX INTEGER { unsupported(1), enabled(3), disabled(4) }

   225 

   226 JvmTimeMillis64TC ::= TEXTUAL-CONVENTION

   227     STATUS       current

   228     DESCRIPTION

   229           "An elapsed time, expressed in milli-seconds.

   230            This type is based on Counter64, but without its specific

   231            semantics.

   232 	  "

   233     SYNTAX Counter64

   234 

   235 JvmTimeNanos64TC ::= TEXTUAL-CONVENTION

   236     STATUS       current

   237     DESCRIPTION

   238           "An elapsed time, expressed in nano-seconds.

   239            This type is based on Counter64, but without its specific

   240            semantics.

   241 	  "

   242     SYNTAX Counter64

   243 

   244 JvmPositive32TC ::= TEXTUAL-CONVENTION

   245     STATUS       current

   246     DESCRIPTION

   247           "A positive Integer32. In Java that would be a number

   248            in [0..Integer.MAX_VALUE].

   249 	  "

   250     -- We use Integer32 (0..2147483647) rather than Unsigned32 because

   251     -- Unsigned32 (0..2147483647) because Unsigned32 is based on

   252     -- Gauge32 - which has a specific ASN.1 tag and a specific semantics.

   253     -- In principle you cannot use a Gauge32 as base type for an index

   254     -- in a table.

   255     -- Note also that Unsigned32 is (0..2^32-1)

   256     --          while Positive32 is (0..2^31-1)

   257     --

   258     SYNTAX Integer32 (0..2147483647)

   259 

   260 JvmManagedMemoryTypeTC ::= TEXTUAL-CONVENTION

   261     STATUS  current

   262     DESCRIPTION

   263 	"

   264          Defines the type of memory contained in a memory pool.

   265 	 The pool may contain, heap memory or non-heap memory.

   266 	"

   267     SYNTAX  INTEGER { nonheap(1), heap(2) }

   268 

   269 

   270 JvmValidityStateTC ::= TEXTUAL-CONVENTION

   271     STATUS  current

   272     DESCRIPTION

   273 	"

   274          Defines whether an object is still valid.

   275 	"

   276     SYNTAX  INTEGER { invalid(1), valid(2) }

   277 

   278 

   279 JvmThreadStateTC ::= TEXTUAL-CONVENTION

   280     STATUS  current

   281     DESCRIPTION

   282 	"Defines the possible states of a thread running in the

   283 	 Java virtual machine. They are virtual machine thread states

   284 	 and do not reflect any operating system thread states.

   285 

   286 	 The first two bits: inNative(1) and suspended(2) can be

   287          combined together and with any other bits. The remaining

   288          bits 3-9, are mutually exclusive. Bits 10-16 are reserved

   289          for future evolution of this MIB.

   290 

   291          An agent MUST always return a thread state with one of the

   292          bits in the range 3-9 set to 1. The other(9) bit should only

   293          be set to 1 if new thread states which are mutally exclusive

   294          with bits 3-8 are defined.  An implementation can define

   295          additional implementation dependant states and uses bits

   296          from bit 17.

   297 

   298 	 See java.lang.Thread.State,

   299 	     java.lang.management.ThreadInfo.

   300 	 "

   301      --

   302      -- Take care that in SNMP bits are numbered starting at 1, from

   303      -- left to right (1 is the highest bit). A bitmap defined by the

   304      -- BITS construct is thus a byte array where bit 1 is the highest bit

   305      -- of the first byte.

   306      --

   307      SYNTAX  BITS { -- Bits 1-2 may be specified in any combination

   308                     inNative(1),

   309                     suspended(2),

   310 

   311                     -- Bits 3-9 are mutually exclusive. Attempting to

   312                     -- set more than a single bit to 1 will result in

   313                     -- a returned error-status of inconsistentValue.

   314                     newThread(3),

   315                     runnable(4),

   316                     blocked(5),

   317                     terminated(6),

   318                     waiting(7),

   319                     timedWaiting(8),

   320                     other(9)

   321                     -- Bits 10-16 are reserved for future use by

   322                     -- this MIB

   323                   }

   324 

   325 

   326 JvmIndex64TC ::= TEXTUAL-CONVENTION

   327     STATUS current

   328     DESCRIPTION

   329 	"A 64 bits string mapping an unsigned 64 bits integer value

   330          in big-endian ordering (i.e: 1 is encoded as 0x0000000000000001).

   331 

   332 	 This type can be used when an unsigned 64 bits integer needs

   333 	 to be used inside a table index.

   334 	"

   335     SYNTAX OCTET STRING (SIZE(8))

   336 

   337 

   338 -- OBJECT-TYPE OID tree

   339 -----------------------

   340 

   341 jvmMgtMIBObjects

   342 	OBJECT IDENTIFIER ::= { jvmMgtMIB 1 }

   343 jvmMgtMIBNotifications

   344 	OBJECT IDENTIFIER ::= { jvmMgtMIB 2 }

   345 jvmMgtMIBConformance

   346 	OBJECT IDENTIFIER ::= { jvmMgtMIB 3 }

   347 

   348 -----------------------------------------------------------------------

   349 --

   350 -- The JVM Class Loading group

   351 --

   352 -- A collection of objects used to monitor Class Loading in the

   353 -- Java Virtual Machine. These objects define the SNMP  management

   354 -- interface for the class loading system of the Java virtual machine.

   355 --

   356 -- This group only contains a few scalar object and no tables. The objects

   357 -- from this group are mapped from the java.lang.management.ClassLoadingMXBean

   358 -- interface.

   359 --

   360 -- See J2SE 5.0 API Specification,

   361 --     java.lang.management.ClassLoadingMXBean

   362 -----------------------------------------------------------------------

   363 

   364 -- Root OBJECT IDENTIFIER for ClassLoading group.

   365 --

   366 jvmClassLoading   OBJECT IDENTIFIER ::= { jvmMgtMIBObjects 1 }

   367 

   368 -- The following objects are mapped from the ClassLoadingMXBean interface.

   369 -----------------------------------------------------------------------

   370 

   371 jvmClassesLoadedCount OBJECT-TYPE

   372     SYNTAX      Gauge32

   373     MAX-ACCESS  read-only

   374     STATUS      current

   375     DESCRIPTION

   376             "The number of classes currently loaded in the JVM.

   377 

   378 	     See java.lang.management.ClassLoadingMXBean.getLoadedClassCount()

   379             "

   380     REFERENCE "J2SE 5.0 API Specification,

   381               java.lang.management.ClassLoadingMXBean"

   382     ::= { jvmClassLoading 1 }

   383 

   384 jvmClassesTotalLoadedCount OBJECT-TYPE

   385     SYNTAX      Counter64

   386     MAX-ACCESS  read-only

   387     STATUS      current

   388     DESCRIPTION

   389             "The total number of classes that have been loaded since

   390 	     the JVM has started execution.

   391 

   392 	     See java.lang.management.ClassLoadingMXBean.

   393 	              getTotalLoadedClassCount()

   394             "

   395     REFERENCE "J2SE 5.0 API Specification,

   396               java.lang.management.ClassLoadingMXBean"

   397     ::= { jvmClassLoading 2 }

   398 

   399 jvmClassesUnloadedCount OBJECT-TYPE

   400     SYNTAX      Counter64

   401     MAX-ACCESS  read-only

   402     STATUS      current

   403     DESCRIPTION

   404             "The total number of classes that have been unloaded since

   405 	     the JVM has started execution.

   406 

   407 	     See java.lang.management.ClassLoadingMXBean.getUnloadedClassCount()

   408             "

   409     REFERENCE "J2SE 5.0 API Specification,

   410               java.lang.management.ClassLoadingMXBean"

   411     ::= { jvmClassLoading 3 }

   412 

   413 jvmClassesVerboseLevel OBJECT-TYPE

   414     SYNTAX      JvmVerboseLevelTC

   415     MAX-ACCESS  read-write

   416     STATUS      current

   417     DESCRIPTION

   418             "Enables or disables the verbose output for the class loading

   419              system. The verbose output information and the output stream

   420              to which the verbose information is emitted are implementation

   421              dependent. Typically, a Java virtual machine implementation

   422              prints a message each time a class file is loaded.

   423 

   424 	     verbose: if the verbose output is enabled.

   425 	     silent:  otherwise.

   426 

   427 	     See java.lang.management.ClassLoadingMXBean.isVerbose(),

   428                  java.lang.management.ClassLoadingMXBean.setVerbose()

   429             "

   430     REFERENCE "J2SE 5.0 API Specification,

   431               java.lang.management.ClassLoadingMXBean"

   432     DEFVAL { silent }

   433     ::= { jvmClassLoading 4 }

   434 

   435 

   436 -----------------------------------------------------------------------

   437 --

   438 -- The JVM Memory group

   439 --

   440 -- A collection of objects used to monitor memory management in the

   441 -- Java Virtual Machine. These objects define management interface for

   442 -- the memory system of the Java virtual machine.

   443 --

   444 -- Memory:

   445 --

   446 -- The memory system of the Java virtual machine manages the following

   447 -- kinds of memory: heap, and non-heap. More information on these types

   448 -- of memory can be obtained from the J2SE 5.0 API Specification,

   449 -- java.lang.management.MemoryMXBean.

   450 --

   451 -- Memory Pools and Memory Managers:

   452 --

   453 -- Memory pools and memory managers are the abstract entities that monitor

   454 -- and manage the memory system of the Java virtual machine.

   455 --

   456 -- Memory managers are represented by the jvmMemManagerTable, which contains

   457 -- one row per Memory manager.

   458 -- The garbage collector is one type of memory  manager responsible for

   459 -- reclaiming memory occupied by unreachable objects.

   460 -- The jvmMemGCTable is an extension of the jvmMemManagerTable, which contains

   461 -- the attribute specific to garbage collectors. A garbage collector entity

   462 -- is thus represented by one row in the jvmMemManagerTable, and one

   463 -- extension row in the jvmMemGCTable.

   464 --

   465 -- Memory Pools are represented by the jvmMemPoolTable, which contains one

   466 -- row per memory pool. A Java virtual machine may create or remove

   467 -- memory pools during execution. A memory pool can belong to either the

   468 -- heap or the non-heap memory.

   469 --

   470 -- A memory manager is responsible for managing one or more memory pools.

   471 -- A memory pool can be managed by more than one memory manager.

   472 -- The jvmMemMgrRelPoolTable represents this managing/managed relationship.

   473 --

   474 -- A Java virtual machine may add or remove memory managers during execution.

   475 --

   476 -- See J2SE 5.0 API Specification, java.lang.management.MemoryMXBean for

   477 --     more information on memory types, memory managers, memory pools,

   478 --     and the memory subsystem.

   479 --

   480 -----------------------------------------------------------------------

   481 

   482 -- Root OBJECT IDENTIFIER for the JVM Memory group.

   483 --

   484 jvmMemory   OBJECT IDENTIFIER ::= { jvmMgtMIBObjects 2 }

   485 

   486 -- The following objects are mapped from the MemoryMXBean interface.

   487 -----------------------------------------------------------------------

   488 

   489 jvmMemoryPendingFinalCount OBJECT-TYPE

   490     SYNTAX      Gauge32

   491     MAX-ACCESS  read-only

   492     STATUS      current

   493     DESCRIPTION

   494 	"The approximate number objects that are pending for finalization.

   495 

   496 	 See java.lang.management.MemoryMXBean.

   497                   getObjectPendingFinalizationCount()

   498         "

   499     REFERENCE "J2SE 5.0 API Specification,

   500               java.lang.management.MemoryMXBean"

   501     ::= { jvmMemory 1 }

   502 

   503 jvmMemoryGCVerboseLevel OBJECT-TYPE

   504     SYNTAX      JvmVerboseLevelTC

   505     MAX-ACCESS  read-write

   506     STATUS      current

   507     DESCRIPTION

   508 	"Enables or disables verbose output for the memory system.

   509          The verbose output information and the output stream to which

   510          the verbose information is emitted are implementation dependent.

   511          Typically, a Java virtual machine implementation prints a

   512          message whenever it frees memory at garbage collection.

   513 

   514 	 verbose: if the verbose output is enabled,

   515          silent:  otherwise.

   516 

   517 	 See java.lang.management.MemoryMXBean.isVerbose(),

   518              java.lang.management.MemoryMXBean.setVerbose()

   519         "

   520     REFERENCE "J2SE 5.0 API Specification,

   521               java.lang.management.MemoryMXBean"

   522     ::= { jvmMemory 2 }

   523 

   524 jvmMemoryGCCall OBJECT-TYPE

   525     SYNTAX      INTEGER { unsupported(1), supported(2), start(3),

   526                           started(4), failed(5) }

   527     MAX-ACCESS  read-write

   528     STATUS      current

   529     DESCRIPTION

   530 	"This object makes it possible to remotelly trigger the

   531 	 Garbage Collector in the JVM.

   532 

   533 	 This object's syntax is an enumeration which defines:

   534 

   535 	 * Two state values, that can be returned from a GET request:

   536 

   537            unsupported(1): means that remote invocation of gc() is not

   538                            supported by the SNMP agent.

   539            supported(2)  : means that remote invocation of gc() is supported

   540 	                   by the SNMP agent.

   541 

   542          * One action value, that can be provided in a SET request to

   543            trigger the garbage collector:

   544 

   545            start(3)      : means that a manager wishes to trigger

   546                            garbage collection.

   547 

   548          * Two result value, that will be returned in the response to a

   549            SET request when remote invocation of gc is supported

   550 	   by the SNMP agent:

   551 

   552 	   started(4)    : means that garbage collection was

   553                            successfully triggered. It does not mean

   554                            however that the action was successfullly

   555                            completed: gc might still be running when

   556                            this value is returned.

   557 	   failed(5)     : means that garbage collection couldn't be

   558                            triggered.

   559 

   560          * If remote invocation is not supported by the SNMP agent, then

   561            unsupported(1) will always be returned as a result of either

   562            a GET request, or a SET request with start(3) as input value.

   563 

   564          * If a SET request with anything but start(3) is received, then

   565 	   the agent will return a wrongValue error.

   566 

   567 	 See java.lang.management.MemoryMXBean.gc()

   568         "

   569     REFERENCE "J2SE 5.0 API Specification,

   570               java.lang.management.MemoryMXBean"

   571     ::= { jvmMemory 3 }

   572 

   573 -- The object identifiers in the range jvmMemory.[4-9] are reserved for future

   574 -- evolution of this MIB.

   575 --

   576 -- We use the range jvmMemory.[10..19] for objects related to global JVM

   577 -- heap memory  usage, as returned by

   578 --      java.lang.management.MemoryMXBean.getHeapMemoryUsage().

   579 -- Object identifiers in the range jvmMemory.[14..19] are not used but

   580 -- reserved for future evolution of this MIB.

   581 --

   582 jvmMemoryHeapInitSize OBJECT-TYPE

   583     SYNTAX      JvmUnsigned64TC

   584     UNITS       "bytes"

   585     MAX-ACCESS  read-only

   586     STATUS      current

   587     DESCRIPTION

   588 	"

   589         Total amount of memory (in bytes) that the Java virtual machine

   590         initially requests from the operating system for memory management

   591 	for heap memory pools.

   592 

   593 	See java.lang.management.MemoryMXBean.getHeapMemoryUsage().getInit()

   594         "

   595     REFERENCE "J2SE 5.0 API Specification,

   596               java.lang.management.MemoryMXBean,

   597               java.lang.management.MemoryUsage"

   598     ::= { jvmMemory 10 }

   599 

   600 

   601 jvmMemoryHeapUsed OBJECT-TYPE

   602     SYNTAX      JvmUnsigned64TC

   603     UNITS       "bytes"

   604     MAX-ACCESS  read-only

   605     STATUS      current

   606     DESCRIPTION

   607 	"

   608         Total amount of used memory (in bytes) from heap memory pools.

   609 

   610 	See java.lang.management.MemoryMXBean.getHeapMemoryUsage().getUsed()

   611         "

   612     REFERENCE "J2SE 5.0 API Specification,

   613               java.lang.management.MemoryMXBean,

   614               java.lang.management.MemoryUsage"

   615     ::= { jvmMemory 11 }

   616 

   617 jvmMemoryHeapCommitted OBJECT-TYPE

   618     SYNTAX      JvmUnsigned64TC

   619     UNITS       "bytes"

   620     MAX-ACCESS  read-only

   621     STATUS      current

   622     DESCRIPTION

   623 	"

   624         Total amount of memory (in bytes) committed by heap memory pools.

   625 

   626 	See java.lang.management.MemoryMXBean.getHeapMemoryUsage().

   627 	         getCommitted()

   628         "

   629     REFERENCE "J2SE 5.0 API Specification,

   630               java.lang.management.MemoryMXBean,

   631               java.lang.management.MemoryUsage"

   632     ::= { jvmMemory 12 }

   633 

   634 jvmMemoryHeapMaxSize OBJECT-TYPE

   635     SYNTAX      JvmUnsigned64TC

   636     UNITS       "bytes"

   637     MAX-ACCESS  read-only

   638     STATUS      current

   639     DESCRIPTION

   640 	"

   641         Total maximum size of memory (in bytes) for all heap memory pools.

   642 

   643 	See java.lang.management.MemoryMXBean.getHeapMemoryUsage().getMax()

   644         "

   645     REFERENCE "J2SE 5.0 API Specification,

   646               java.lang.management.MemoryMXBean,

   647               java.lang.management.MemoryUsage"

   648     ::= { jvmMemory 13 }

   649 

   650 -- We use the range jvmMemory.[20..29] for objects related to global JVM

   651 -- heap memory usage, as returned by

   652 --      lang.management.MemoryMXBean.getNonHeapMemoryUsage().

   653 -- Object identifiers in the range jvmMemory.[24..29] are not used but are

   654 -- reserved for future evolution of this MIB.

   655 --

   656 jvmMemoryNonHeapInitSize OBJECT-TYPE

   657     SYNTAX      JvmUnsigned64TC

   658     UNITS       "bytes"

   659     MAX-ACCESS  read-only

   660     STATUS      current

   661     DESCRIPTION

   662 	"

   663         Total amount of memory (in bytes) that the Java virtual machine

   664         initially requests from the operating system for memory management

   665 	for non heap memory pools.

   666 

   667 	See java.lang.management.MemoryMXBean.getNonHeapMemoryUsage().getInit()

   668         "

   669     REFERENCE "J2SE 5.0 API Specification,

   670               java.lang.management.MemoryMXBean,

   671               java.lang.management.MemoryUsage"

   672     ::= { jvmMemory 20 }

   673 

   674 

   675 jvmMemoryNonHeapUsed OBJECT-TYPE

   676     SYNTAX      JvmUnsigned64TC

   677     UNITS       "bytes"

   678     MAX-ACCESS  read-only

   679     STATUS      current

   680     DESCRIPTION

   681 	"

   682         Total amount of used memory (in bytes) from non heap memory pools.

   683 

   684 	See java.lang.management.MemoryMXBean.getNonHeapMemoryUsage().getUsed()

   685         "

   686     REFERENCE "J2SE 5.0 API Specification,

   687               java.lang.management.MemoryMXBean,

   688               java.lang.management.MemoryUsage"

   689     ::= { jvmMemory 21 }

   690 

   691 jvmMemoryNonHeapCommitted OBJECT-TYPE

   692     SYNTAX      JvmUnsigned64TC

   693     UNITS       "bytes"

   694     MAX-ACCESS  read-only

   695     STATUS      current

   696     DESCRIPTION

   697 	"

   698         Total amount of memory (in bytes) committed by non heap memory pools.

   699 

   700 	See java.lang.management.MemoryMXBean.

   701 	         getNonHeapMemoryUsage().getCommitted()

   702         "

   703     REFERENCE "J2SE 5.0 API Specification,

   704               java.lang.management.MemoryMXBean,

   705               java.lang.management.MemoryUsage"

   706     ::= { jvmMemory 22 }

   707 

   708 jvmMemoryNonHeapMaxSize OBJECT-TYPE

   709     SYNTAX      JvmUnsigned64TC

   710     UNITS       "bytes"

   711     MAX-ACCESS  read-only

   712     STATUS      current

   713     DESCRIPTION

   714 	"

   715         Total maximum size of memory (in bytes) for all non heap memory pools.

   716 

   717 	See java.lang.management.MemoryMXBean.getNonHeapMemoryUsage().getMax()

   718         "

   719     REFERENCE "J2SE 5.0 API Specification,

   720               java.lang.management.MemoryMXBean,

   721               java.lang.management.MemoryUsage"

   722     ::= { jvmMemory 23 }

   723 

   724 -- The object identifiers in the range jvmMemory.[30-99] are not used but are

   725 -- reserved for future evolution of this MIB.

   726 --

   727 -- The JVM Memory Manager Table

   728 --

   729 -- The jvmMemManagerTable represent memory manager abstract entities.

   730 -- The jvmMemManagerTable contains one row per memory manager. In

   731 -- addition, those memory managers which are also garbage collectors have

   732 -- an extension row in the jvmMemGCTable.

   733 --

   734 -- See J2SE 5.0 API Specification, java.lang.management.MemoryMXBean for

   735 --     a detailed description of the memory subsystem.

   736 --

   737 -- See J2SE 5.0 API Specification, java.lang.management.MemoryManagerMXBean

   738 --     for more information on memory managers.

   739 --

   740 -----------------------------------------------------------------------

   741 --

   742 -- We use the range jvmMemory.[100..109] for objects related to memory

   743 -- managers.

   744 -- Object identifiers in the range jvmMemory.[102-109] are not used

   745 -- but are reserved for future evolution of this MIB.

   746 --

   747 jvmMemManagerTable OBJECT-TYPE

   748     SYNTAX      SEQUENCE OF JvmMemManagerEntry

   749     MAX-ACCESS  not-accessible

   750     STATUS      current

   751     DESCRIPTION

   752 	"The Memory Manager Table contains the whole list of Memory

   753 	 Managers  as returned by ManagementFactory.getMemoryManagerMXBeans().

   754 

   755 	 When a MemoryManagerMXBean object is an instance of

   756 	 GarbageCollectorMXBean, then additional information specific to

   757 	 the GarbageCollectorMXBean class will be found in the

   758 	 jvmGCTable, at the same index.

   759 

   760 	 Relationships between MemoryManagers and MemoryPools are shown

   761 	 by the Memory Manager-Pool Relation table (jvmMemMgrPoolRelTable).

   762 	"

   763     REFERENCE "J2SE 5.0 API Specification,

   764               java.lang.management.MemoryManagerMXBean"

   765     ::= { jvmMemory 100 }

   766 

   767 jvmMemManagerEntry OBJECT-TYPE

   768     SYNTAX      JvmMemManagerEntry

   769     MAX-ACCESS  not-accessible

   770     STATUS      current

   771     DESCRIPTION

   772 	"A jvmMemManagerEntry conceptual row represent an instance of the

   773 	 java.lang.management.MemoryManagerMXBean interface. If that instance

   774 	 is also an instance of java.lang.management.GarbageCollectorMXBean,

   775 	 then additional information will be found in the jvmGCTable, at the

   776          same index.

   777 

   778 	 Columnar objects in this table are mapped from attributes of

   779 	 the MemoryManagerMXBean interface.

   780 

   781 	 See java.lang.management.MemoryManagerMXBean

   782         "

   783     REFERENCE "J2SE 5.0 API Specification,

   784               java.lang.management.MemoryManagerMXBean"

   785     INDEX { jvmMemManagerIndex }

   786     ::= { jvmMemManagerTable 1 }

   787 

   788 JvmMemManagerEntry ::= SEQUENCE {

   789         jvmMemManagerIndex JvmPositive32TC,

   790         jvmMemManagerName  JvmJavaObjectNameTC,

   791 	jvmMemManagerState JvmValidityStateTC

   792 }

   793 

   794 jvmMemManagerIndex OBJECT-TYPE

   795     SYNTAX      JvmPositive32TC

   796     MAX-ACCESS  not-accessible

   797     STATUS      current

   798     DESCRIPTION

   799 	"An index opaquely computed by the agent and which uniquely

   800 	 identifies a Memory Manager.

   801 

   802 	 The jvmMemManagerIndex index is opaquely computed by the agent,

   803 	 from e.g the hash code of the MemoryManager (or MemoryManager name).

   804 	 The agent is responsible for allocating a free index when it needs

   805 	 one (e.g. if two objects have the same hash, then it may increment

   806 	 one of the values until the conflict is resolved). As a result a

   807 	 manager must not depend on the value of that index across,

   808 	 e.g. reboot of the agent, as this value is not guaranteed to

   809 	 stay identical after the agent restarts.

   810 	 "

   811     REFERENCE "J2SE 5.0 API Specification,

   812               java.lang.management.MemoryManagerMXBean"

   813     ::= { jvmMemManagerEntry 1 }

   814 

   815 jvmMemManagerName OBJECT-TYPE

   816     SYNTAX      JvmJavaObjectNameTC

   817     MAX-ACCESS  read-only

   818     STATUS      current

   819     DESCRIPTION

   820 	"The name of this memory manager, as returned by

   821 	 MemoryManagerMXBean.getName().

   822 

   823 	 See java.mangement.MemoryManagerMXBean.getName().

   824 	"

   825     REFERENCE "J2SE 5.0 API Specification,

   826               java.lang.management.MemoryManagerMXBean"

   827     ::= { jvmMemManagerEntry 2 }

   828 

   829 jvmMemManagerState OBJECT-TYPE

   830     SYNTAX      JvmValidityStateTC

   831     MAX-ACCESS  read-only

   832     STATUS      current

   833     DESCRIPTION

   834 	"

   835          Indicates whether this memory manager is valid in the Java

   836          virtual machine. A memory manager becomes invalid once the

   837          Java virtual machine removes it from the memory system.

   838 

   839 	 See java.lang.management.MemoryManagerMXBean.isValid()

   840         "

   841     REFERENCE "J2SE 5.0 API Specification,

   842               java.lang.management.MemoryManagerMXBean"

   843     ::= { jvmMemManagerEntry 3 }

   844 

   845 

   846 -- The JVM Garbage Collector Table

   847 --

   848 -- The jvmMemGCTable is an extension of the jvmMemManagerTable.

   849 -- It represents garbage collector abstract entities. A garbage collector

   850 -- is a memory manager responsible for reclaiming  memory occupied by

   851 -- unreachable objects.

   852 --

   853 -- A garbage collector is thus represented by one row in the

   854 -- jvmMemManagerTable, plus an extension row in the jvmMemGCTable.

   855 -- The extension row in the jvmMemGCTable contains those attributes which

   856 -- are specific to garbage collectors.

   857 --

   858 -- See J2SE 5.0 API Specification, java.lang.management.MemoryMXBean for

   859 --     a detailed description of the memory subsystem.

   860 --

   861 -- See J2SE 5.0 API Specification, java.lang.management.MemoryManagerMXBean

   862 --     for more information on memory managers, and

   863 --     java.lang.management.GarbageCollectorMXBean for more information on

   864 --     garbage collectors.

   865 --

   866 -----------------------------------------------------------------------

   867 

   868 jvmMemGCTable OBJECT-TYPE

   869     SYNTAX      SEQUENCE OF JvmMemGCEntry

   870     MAX-ACCESS  not-accessible

   871     STATUS      current

   872     DESCRIPTION

   873 	"The Garbage Collector table provides additional information

   874 	 on those MemoryManagers which are also GarbageCollectors.

   875 	 This table extends the  jvmMemManagerTable table. The index

   876 	 used in the jvmMemGCTable table is imported from the

   877 	 jvmMemManagerTable table. If a row from the jvmMemManagerTable

   878 	 table is deleted, and if it has an extension in the jvmMemGCTable

   879 	 table, then the extension row will also be deleted.

   880         "

   881     REFERENCE "J2SE 5.0 API Specification,

   882               java.lang.management.GarbageCollectorMXBean"

   883     ::= { jvmMemory 101 }

   884 

   885 jvmMemGCEntry OBJECT-TYPE

   886     SYNTAX      JvmMemGCEntry

   887     MAX-ACCESS  not-accessible

   888     STATUS      current

   889     DESCRIPTION

   890 	"Provide additional information on Garbage Collectors.

   891 

   892 	 Columnar objects in this table are mapped from the

   893 	 GarbageCollectorMXBean interface.

   894 

   895 	 See java.lang.management.GarbageCollectorMXBean

   896         "

   897     REFERENCE "J2SE 5.0 API Specification,

   898               java.lang.management.GarbageCollectorMXBean"

   899     INDEX   { jvmMemManagerIndex }

   900     ::= {jvmMemGCTable 1 }

   901 

   902 JvmMemGCEntry ::= SEQUENCE {

   903         jvmMemGCCount  Counter64,

   904         jvmMemGCTimeMs JvmTimeMillis64TC

   905 }

   906 

   907 jvmMemGCCount OBJECT-TYPE

   908     SYNTAX      Counter64

   909     MAX-ACCESS  read-only

   910     STATUS      current

   911     DESCRIPTION

   912 	"The total number of collections that have occurred,

   913 	 as returned by GarbageCollectorMXBean.getCollectionCount().

   914 

   915 	 If garbage collection statistics are not available, this

   916 	 object is set to 0.

   917 

   918 	 See java.lang.management.GarbageCollectorMXBean.getCollectionCount()

   919 	"

   920     REFERENCE "J2SE 5.0 API Specification,

   921               java.lang.management.GarbageCollectorMXBean"

   922     ::= { jvmMemGCEntry 2 }

   923 

   924 jvmMemGCTimeMs OBJECT-TYPE

   925     SYNTAX      JvmTimeMillis64TC

   926     UNITS       "milliseconds"

   927     MAX-ACCESS  read-only

   928     STATUS      current

   929     DESCRIPTION

   930 	"The approximate accumulated collection elapsed time in

   931 	 milliseconds, since the Java virtual machine has started.

   932 	 This object is set to 0 if the collection elapsed time is

   933 	 undefined for this collector.

   934 

   935 	 See java.lang.management.GarbageCollectorMXBean.getCollectionTime()

   936         "

   937     REFERENCE "J2SE 5.0 API Specification,

   938               java.lang.management.GarbageCollectorMXBean"

   939     DEFVAL { 0 }

   940     ::= { jvmMemGCEntry 3 }

   941 

   942 -- The JVM Memory Pool Table

   943 --

   944 -- The jvmMemPoolTable represent memory pool abstract entities.

   945 -- The jvmMemPoolTable contains one row per memory pool.

   946 --

   947 -- See J2SE 5.0 API Specification, java.lang.management.MemoryMXBean for

   948 --     a detailed description of the memory subsystem.

   949 --

   950 -- See J2SE 5.0 API Specification, java.lang.management.MemoryPoolMXBean

   951 --     for more information on memory pool.

   952 --

   953 -----------------------------------------------------------------------

   954 --

   955 -- We use the range jvmMemory.[110..119] for objects related to memory pools.

   956 -- Object identifiers in the range jvmMemory.[111-119] are not used but

   957 -- are reserved for future evolution of this MIB.

   958 --

   959 jvmMemPoolTable OBJECT-TYPE

   960     SYNTAX      SEQUENCE OF JvmMemPoolEntry

   961     MAX-ACCESS  not-accessible

   962     STATUS      current

   963     DESCRIPTION

   964 	"The Memory Pool Table contains the whole list of MemoryPools

   965 	 as returned by ManagementFactory.getMemoryPoolMXBeans().

   966 	"

   967     REFERENCE "J2SE 5.0 API Specification,

   968               java.lang.management.MemoryPoolMXBean"

   969     ::= { jvmMemory 110 }

   970 

   971 jvmMemPoolEntry OBJECT-TYPE

   972     SYNTAX      JvmMemPoolEntry

   973     MAX-ACCESS  not-accessible

   974     STATUS      current

   975     DESCRIPTION

   976 	"

   977          Represents a memory pool. The pool may contain heap memory or

   978          non-heap memory. A row in this table represents

   979 	 an instance of MemoryPoolMXBean.

   980 

   981 	 See java.lang.management.MemoryPoolMXBean

   982         "

   983     REFERENCE "J2SE 5.0 API Specification,

   984               java.lang.management.MemoryPoolMXBean"

   985     INDEX { jvmMemPoolIndex }

   986     ::= { jvmMemPoolTable 1 }

   987 

   988 JvmMemPoolEntry ::= SEQUENCE {

   989         jvmMemPoolIndex                 JvmPositive32TC,

   990 	jvmMemPoolName                  JvmJavaObjectNameTC,

   991 	jvmMemPoolType                  JvmManagedMemoryTypeTC,

   992 	jvmMemPoolState                 JvmValidityStateTC,

   993 	jvmMemPoolPeakReset             JvmTimeMillis64TC,

   994 

   995 	jvmMemPoolInitSize              JvmUnsigned64TC,

   996 	jvmMemPoolUsed                  JvmUnsigned64TC,

   997 	jvmMemPoolCommitted             JvmUnsigned64TC,

   998 	jvmMemPoolMaxSize               JvmUnsigned64TC,

   999 

  1000 	jvmMemPoolPeakUsed              JvmUnsigned64TC,

  1001 	jvmMemPoolPeakCommitted         JvmUnsigned64TC,

  1002 	jvmMemPoolPeakMaxSize           JvmUnsigned64TC,

  1003 

  1004 	jvmMemPoolCollectUsed           JvmUnsigned64TC,

  1005 	jvmMemPoolCollectCommitted      JvmUnsigned64TC,

  1006 	jvmMemPoolCollectMaxSize        JvmUnsigned64TC,

  1007 

  1008 	jvmMemPoolThreshold             JvmUnsigned64TC,

  1009 	jvmMemPoolThreshdCount          Counter64,

  1010 	jvmMemPoolThreshdSupport        JvmImplSupportStateTC,

  1011 	jvmMemPoolCollectThreshold      JvmUnsigned64TC,

  1012 	jvmMemPoolCollectThreshdCount   Counter64,

  1013 	jvmMemPoolCollectThreshdSupport JvmImplSupportStateTC

  1014 

  1015 }

  1016 

  1017 jvmMemPoolIndex OBJECT-TYPE

  1018     SYNTAX      JvmPositive32TC

  1019     MAX-ACCESS  not-accessible

  1020     STATUS      current

  1021     DESCRIPTION

  1022 	"An index value opaquely computed by the agent which uniquely

  1023 	 identifies a row in the jvmMemPoolTable.

  1024 

  1025 	 The jvmMemPoolIndex index is opaquely computed by the agent,

  1026 	 from e.g the hash code of the MemoryPool (or MemoryPool name).

  1027 	 The agent is responsible for allocating a free index when it

  1028 	 needs one (e.g. if two objects have the same hash, then it may

  1029 	 increment one of the values until the conflict is resolved).

  1030 	 As a result a manager must not depend on the value of that

  1031 	 index across, e.g. reboot of the agent, as this value is not

  1032 	 guaranteed to stay identical after the agent restarts.

  1033         "

  1034     ::= { jvmMemPoolEntry 1 }

  1035 

  1036 jvmMemPoolName OBJECT-TYPE

  1037     SYNTAX      JvmJavaObjectNameTC

  1038     MAX-ACCESS  read-only

  1039     STATUS      current

  1040     DESCRIPTION

  1041 	"The name of this memory pool, as returned by

  1042          MemoryPoolMXBean.getName().

  1043 

  1044 	 See java.lang.management.MemoryPoolMXBean.getName()

  1045         "

  1046     REFERENCE "J2SE 5.0 API Specification,

  1047               java.lang.management.MemoryPoolMXBean"

  1048     ::= { jvmMemPoolEntry 2 }

  1049 

  1050 jvmMemPoolType OBJECT-TYPE

  1051     SYNTAX      JvmManagedMemoryTypeTC

  1052     MAX-ACCESS  read-only

  1053     STATUS      current

  1054     DESCRIPTION

  1055 	"The type of memory managed in this pool. This pool may be used for

  1056 	 heap memory or non-heap memory.

  1057 

  1058 	 See java.lang.management.MemoryPoolMXBean.getMemoryType()

  1059         "

  1060     REFERENCE "J2SE 5.0 API Specification,

  1061               java.lang.management.MemoryPoolMXBean"

  1062     ::= { jvmMemPoolEntry 3 }

  1063 

  1064 jvmMemPoolState OBJECT-TYPE

  1065     SYNTAX      JvmValidityStateTC

  1066     MAX-ACCESS  read-only

  1067     STATUS      current

  1068     DESCRIPTION

  1069 	"

  1070          Indicates whether this memory pool is valid in the Java

  1071          virtual machine. A memory pool becomes invalid once the

  1072          Java virtual machine removes it from the memory system.

  1073 

  1074 	 See java.lang.management.MemoryPoolMXBean.isValid()

  1075         "

  1076     REFERENCE "J2SE 5.0 API Specification,

  1077               java.lang.management.MemoryPoolMXBean"

  1078     ::= { jvmMemPoolEntry 4 }

  1079 

  1080 jvmMemPoolPeakReset OBJECT-TYPE

  1081     SYNTAX      JvmTimeMillis64TC

  1082     UNITS       "milliseconds"

  1083     MAX-ACCESS  read-write

  1084     STATUS      current

  1085     DESCRIPTION

  1086 	"

  1087         This object indicates the last time - in milliseconds - at which

  1088         the peak memory usage statistic of this memory pool was reset

  1089 	to the current memory usage. This corresponds to a time stamp

  1090 	as returned by java.lang.System.currentTimeMillis();

  1091 

  1092 	Setting this object to a time earlier than its current time value

  1093 	has no effect. Setting this object to a time later than its current

  1094 	time value causes the peak memory usage statistic of this memory

  1095 	pool to be reset to the current memory usage. The new value of this

  1096 	object will be the time at which the reset operation is triggered.

  1097 

  1098 	There could be a delay between the time at which the reset operation

  1099 	is triggered and the time at which the actual resetting happens, so

  1100 	this value is only indicative.

  1101 

  1102 	 See java.lang.management.MemoryPoolMXBean.resetPeakUsage()

  1103         "

  1104     REFERENCE "J2SE 5.0 API Specification,

  1105               java.lang.management.MemoryPoolMXBean"

  1106     ::= { jvmMemPoolEntry 5 }

  1107 

  1108 

  1109 -- The object identifier arcs in the range jvmMemPoolEntry.[6-9] are

  1110 -- reserved for future evolution of this MIB.

  1111 --

  1112 -- We use the range jvmMemPoolEntry.[10..19] for objects related to this

  1113 -- pool memory usage, as returned by

  1114 --      java.lang.management.MemoryPoolMXBean.getUsage().

  1115 -- Object identifiers in the range jvmMemPoolEntry.[14..19] are not

  1116 -- used but are reserved for future evolution of this MIB.

  1117 --

  1118 jvmMemPoolInitSize OBJECT-TYPE

  1119     SYNTAX      JvmUnsigned64TC

  1120     UNITS       "bytes"

  1121     MAX-ACCESS  read-only

  1122     STATUS      current

  1123     DESCRIPTION

  1124 	"

  1125         Initial size of this memory pool.

  1126 

  1127 	See java.lang.management.MemoryPoolMXBean.getUsage().getInit()

  1128         "

  1129     REFERENCE "J2SE 5.0 API Specification,

  1130               java.lang.management.MemoryPoolMXBean,

  1131               java.lang.management.MemoryUsage"

  1132     ::= { jvmMemPoolEntry 10 }

  1133 

  1134