Sun Java System Application Server Platform Edition 8.1 2005Q2 Update 2 Administration Guide

- Previous: Admin Console Tasks for Enabling and Disabling Monitoring
- Next: Using JConsole

# Admin Console Tasks for Viewing Monitoring Data

- To view monitoring data in the Admin Console

- Viewing Monitoring Data With the asadmin Tool

## To view monitoring data in the Admin Console

For more information on the attributes for each component or service, refer to the Monitoring chapter of the Administration Guide.About Statistics for Monitored Components and Services.

1. Access the Monitoring page. To do this:

   1. In the tree component, select the Application Server node.

   2. Select the Monitor page.

   3. Select the Monitor Values tab.

2. From the View list, select a component or service that has been deployed onto the server instance and for which monitoring is enabled.

   Monitoring data for the selected component or service displays below the View field. For a description of the monitorable properties, refer to the Monitoring chapter of the Administration Guide.About Statistics for Monitored Components and Services.

   On this page, it is possible to view monitoring data for JVM, Server, Thread Pools, HTTP Service, and Transaction Service if monitoring is enabled for these components and services. A diagram showing how these components and services are organized is shown in About the Tree Structure of Monitorable Objects.

3. If you do not see the component or service you wish to monitor in this list, select the Setup tab to enable and disable monitoring for selected components and services.

   Select OFF to disable monitoring for a component or service. Select LOW or HIGH to enable monitoring for a component or service.

   For more information on enabling and disabling monitoring, refer to To configure monitoring levels using the Admin Console or To configure monitoring using the asadmin tool.

4. Select the Applications page to view monitoring data for application components that are deployed onto the server instance and for which monitoring is enabled. Select the application from the Application list. Select the specific component from the Component list.

   If no monitoring data appears for the application or component, select the Setup tab to enable or disable monitoring for a component or service. To monitor applications, turn on the container in which they execute. For example, select Low or High for the Web Container for web applications and/or the EJB Container for EJB applications.

   If no monitoring data is displayed for applications, it is most likely that the application does not exist or is not exercised. Applications monitoring data is available only when the application exists, monitoring is enabled for the application, and the application is being exercised. Once the application is executed, it is registered in the monitoring registry and the monitoring data displays.

   Monitoring data for the selected component displays below the selected component. For a description of the monitorable properties, refer to the Monitoring chapter of the Administration Guide.About Statistics for Monitored Components and Services. A diagram showing how these components and services are organized for applications can be viewed in About the Tree Structure of Monitorable Objects.

5. Select the Resources page to view monitoring data for resources that are deployed onto the server instance and for which monitoring has been enabled. Select the resource from the View list.

   If the resource for which you wish to view monitoring data does not appear, select the Setup tab to enable or disable monitoring for a resource.

   If no monitoring data is displayed for resources, it is most likely that the resource does not exist or is not exercised. Resources monitoring data is available only when the resources exist, monitoring is enabled for the resource at a level of HIGH, and the resource is being exercised. For example, if you have created a JDBC connector service, but applications that use that connector service have not yet requested a connector from the service, that service has not yet been created, therefore, no service exists and no monitoring data is available. Once the JDBC application is executed and requests a connector from a service, the service is registered in the monitoring registry and monitoring data appears.

   Monitoring data for the selected component or service displays below the View field. For a description of the monitorable properties, refer to the Monitoring chapter of the Administration Guide.About Statistics for Monitored Components and Services. A diagram showing how these components and services are organized for resources can be viewed in About the Tree Structure of Monitorable Objects.

6. Select the Transactions page to freeze the transaction subsystem in order to roll back transactions and determine the transactions that are in process at the time of the freeze.

7. To enable monitoring for the Transaction Service, select the Setup tab and make sure that Transaction Service is set to LOW.

   To freeze the Transaction Service in order to roll back transactions, select Freeze. To rollback a transaction, select the checkbox beside the transaction and click Rollback.

##### Equivalent asadmin command

`get --monitor`

For example, to view monitoring data for the JVM, use the following `asadmin` command:

`asadmin> get --user adminuser --monitor server.jvm.*`

##### See Also

- To configure monitoring levels using the Admin Console

- The Monitoring Components and Services chapter in the Application Server Administration Guide (For the guide’s URL, see Further Information.)

## Viewing Monitoring Data With the asadmin Tool

- To use the asadmin tool to view monitoring data

- Understanding and Specifying Dotted Names

- Examples of the list and get Commands

- Examples for the list --user admin-user --monitor Command

- Examples for the get --user admin-user --monitor Command

- To use the PetStore example

- Expected Output for list and get Commands at All Levels

### To use the asadmin tool to view monitoring data

To view monitoring data using the `asadmin` tool, use the `asadmin list` and `asadmin get` commands followed by the dotted name of a monitorable object, as follows.

1. To view the names of the objects that can be monitored, use the `asadmin list` command.

   For example, to view a list of application components and subsystems that have monitoring enable for the server instance, type the following command in a terminal window:

       asadmin> list --user adminuser --monitor server

   The preceding command returns a list of application components and subsystems that have monitoring enabled, for example:

       server.resources
       server.connector-service
       server.orb
       server.jms-service
       server.jvm
       server.applications
       server.http-service
       server.thread-pools

   For further information on using the `list` command, refer to the Monitoring Components and Services chapter in the Administration Guide. (For the guide’s URL, see Further Information.)

   For further examples using the `list` command, refer to Examples of the list and get Commands. For further information on the dotted names you can use with the `list` command, refer to Understanding and Specifying Dotted Names.

2. To display monitoring statistics for an application component or subsystem for which monitoring has been enabled, use the `asadmin get` command.

   To get the statistics, type the `asadmin get` command in a terminal window, specifying a name displayed by the `list` command in the preceding step. The following example attempts to get all attributes from a subsystem for a specific object:

       asadmin> get --user adminuser --monitor server.jvm.*

   The command returns the following attributes and data:

       server.jvm.dotted-name = server.jvm
       server.jvm.heapsize-current = 21241856
       server.jvm.heapsize-description = Provides statistical information about
          the JVM's memory heap size.
       server.jvm.heapsize-highwatermark = 21241856
       server.jvm.heapsize-lastsampletime = 1080232913938
       server.jvm.heapsize-lowerbound = 0
       server.jvm.heapsize-lowwatermark = 0
       server.jvm.heapsize-name = JvmHeapSize
       server.jvm.heapsize-starttime = 1080234457308
       server.jvm.heapsize-unit = bytes
       server.jvm.heapsize-upperbound = 518979584
       server.jvm.uptime-count = 1080234457308
       server.jvm.uptime-description = Provides the amount of time the JVM has
          been running.
       server.jvm.uptime-lastsampletime = 1080234457308
       server.jvm.uptime-name = JvmUpTime
       server.jvm.uptime-starttime = 1080232913928
       server.jvm.uptime-unit = milliseconds

   For further information using the `get` command, refer to the Monitoring Components and Services chapter in the Administration Guide. (For the guide’s URL, see Further Information.)

   For further examples using the `get` command, refer to Examples of the list and get Commands. For further information on the dotted names you can use with the `get` command, refer to Understanding and Specifying Dotted Names.

##### See Also

- Administration Guide (For the guide’s URL, see Further Information.)

- To configure monitoring levels using the Admin Console

- To view monitoring data in the Admin Console

### Understanding and Specifying Dotted Names

In the `asadmin list` and `get` commands, specify the dotted name of monitorable objects. All child objects are addressed using the dot (.) character as separator, thus these are referred to as dotted names. If a child node is of singleton type, then only the monitoring object type is needed to address the object, otherwise a name of the form `type.name` is needed to address the object.

For example, `http-service` is one of the valid monitorable object types and is a singleton. To address a singleton child node representing the `http-service` of instance `server`, the dotted name is:

    server.http-service

Another example, `application`, is a valid monitorable object type and is not a singleton. To address a non-singleton child node representing, for example, the application `PetStore`, the dotted name is:

    server.applications.petstore

The dotted names can also address specific attributes in monitorable objects. For example, `http-service` has a monitorable attribute called `bytesreceived-lastsampletime`. The following name addresses the `bytesreceived` attribute:

    server.http-service.server.http-listener-1.
      bytesreceived-lastsampletime

The administrator is not expected to know the valid dotted names for `asadmin list` and `get` commands. The `list` command displays available monitorable objects, while the `get` command used with a wildcard parameter allows the inspection of all available attributes on any monitorable object.

The underlying assumptions for using the `list` and `get` commands with dotted names are:

- Any `list` command that has a dotted name that is not followed by a wildcard (`*`) gets as its result the current node’s immediate children. For example, `list --user` adminuser `--monitor` `server` lists all immediate children belonging to the `server` node.

- Any `list` command that has a dotted name followed by a wildcard of the form `.*` gets as its result a hierarchical tree of children nodes from the current node. For example, `list --user` adminuser `--monitor server.applications.*` lists all children of `applications` and their subsequent child nodes and so on.

- Any `list` command that has a dotted name preceded or followed by a wildcard of the form *dottedname or dotted * name or `dotted name *` gets as its result all nodes and their children matching the regular expression created by the provided matching pattern.

- A `get` command followed by a `.*` or a `*` gets as its result the set of attributes and their values belonging to the current node to be matched.

For more information, read Expected Output for list and get Commands at All Levels.

### Examples of the list and get Commands

This section contains the following topics:

- Examples for the list --user admin-user --monitor Command

- Examples for the get --user admin-user --monitor Command

### Examples for the list --user admin-user --monitor Command

The `list` command provides information about the application components and subsystems currently being monitored for the specified server instance name. Using this command, you can see the monitorable components and subcomponents for a server instance. For a more complete listing of `list` examples, see Expected Output for list and get Commands at All Levels.

#### Example 1

    asadmin> list --user admin-user --monitor server

The preceding command returns a list of application components and subsystems that have monitoring enabled, for example:

    server.resources
    server.orb
    server.jvm
    server.jms-service
    server.connector-service
    server.applications
    server.http-service
    server.thread-pools

It is also possible to list applications that are currently monitored in the specified server instance. This is useful when particular monitoring statistics are sought from an application using the `get` command.

#### Example 2

    asadmin> list --user admin-user --monitor server.applications

Returns:

    server.applications.adminapp
     server.applications.admingui
    server.applications.myApp

For a more comprehensive example, see To use the PetStore example.

### Examples for the get --user admin-user --monitor Command

This command retrieves the following monitored information:

- All attribute(s) monitored within a component or subsystem

- Specific attribute monitored within a component or subsystem

  When an attribute is requested that does not exist for a particular component or subsystem, an error is returned. Similarly, when a specific attribute is requested that is not active for a component or subsystem, an error is returned.

  Refer to Expected Output for list and get Commands at All Levels for more information on the use of the `get` command.

#### Example 1

Attempt to get all attributes from a subsystem for a specific object:

    asadmin> get --user admin-user --monitor server.jvm.*

Returns:

    server.jvm.dotted-name= server.jvm
    server.jvm.heapsize-current = 21241856
    server.jvm.heapsize-description = Provides statistical information about
       the JVM's memory heap size.
    server.jvm.heapsize-highwatermark = 21241856
    server.jvm.heapsize-lastsampletime = 1080232913938
    server.jvm.heapsize-lowerbound = 0
    server.jvm.heapsize-lowwatermark = 0
    server.jvm.heapsize-name = JvmHeapSize
    server.jvm.heapsize-starttime = 1080234457308
    server.jvm.heapsize-unit = bytes
    server.jvm.heapsize-upperbound = 518979584
    server.jvm.uptime-count = 1080234457308
    server.jvm.uptime-description = Provides the amount of time the JVM has
       been running.
    server.jvm.uptime-lastsampletime = 1080234457308
    server.jvm.uptime-name = JvmUpTime
    server.jvm.uptime-starttime = 1080232913928
    server.jvm.uptime-unit = milliseconds

#### Example 2

Attempt to get all attributes from a J2EE application:

    asadmin> get --user admin-user --monitor server.applications.myJ2eeApp.*

Returns:

    No matches resulted from the wildcard expression.
    CLI137 Command get failed.

There are no monitorable attributes exposed at the J2EE-application level, therefore this reply displays.

#### Example 3

Attempt to get a specific attribute from a subsystem:

    asadmin> get --user admin-user --monitor server.jvm.uptime-lastsampletime

Returns:

    server.jvm.uptime-lastsampletime = 1093215374813

#### Example 4

Attempt to get an unknown attribute from within a subsystem attribute:

    asadmin> get --user admin-user --monitor server.jvm.badname

Returns:

    No such attribute found from reflecting the corresponding Stats
    interface: [badname]
    CLI137 Command get failed.

### To use the PetStore example

The following example illustrates how the `asadmin` tool might be used for monitoring purposes.

A user wants to inspect the number of calls made to a method in the sample `PetStore` application after it has been deployed onto the Application Server. The instance onto which it has been deployed is named `server`. A combination of the `list` and `get` commands are used to access desired statistics on a method.

1. Start the Application Server and the `asadmin` tool.

2. Set some useful environment variables to avoid entering them for every command:

       asadmin> export AS_ADMIN_USER=admin AS_ADMIN_PASSWORD=admin123
       asadmin>export AS_ADMIN_HOST=localhost AS_ADMIN_PORT=4849

3. List monitorable components for instance `server`:

       asadmin> list --user adminuser --monitor server*

   Returns (output will be similar to):

       server
       server.applications
       server.applications.CometEJB
       server.applications.ConverterApp
       server.applications.petstore
       server.http-service
       server.resources
       server.thread-pools

   The list of monitorable components includes `thread-pools`, `http-service`, `resources`, and all deployed (and enabled) `applications`.

4. List the monitorable subcomponents in the `PetStore` application (`-m` can be used instead of `--monitor`):

   `asadmin> list -m server.applications.petstore`

   Returns:

       server.applications.petstore.signon-ejb_jar
       server.applications.petstore.catalog-ejb_jar
       server.applications.petstore.uidgen-ejb_jar
       server.applications.petstore.customer-ejb_jar
       server.applications.petstore.petstore-ejb_jar
       server.applications.petstore.petstore\.war
       server.applications.petstore.AsyncSenderJAR_jar
       server.applications.petstore.cart-ejb_jar

5. List the monitorable subcomponents in the EJB module `signon-ejb_jar` of the `PetStore` application:

       asadmin> list -m server.applications.petstore.signon-ejb_jar

   Returns:

       server.applications.petstore.signon-ejb_jar.SignOnEJB
       server.applications.petstore.signon-ejb_jar.UserEJB

6. List the monitorable subcomponents in the entity bean `UserEJB` for the EJB module `signon-ejb_jar` of the `PetStore` application:

       asadmin> list -m server.applications.petstore.signon-ejb_jar.UserEJB

   Returns (with dotted name removed for space considerations):

       server.applications.petstore.signon-ejb_jar.UserEJB.bean-cache
       server.applications.petstore.signon-ejb_jar.UserEJB.bean-methods
       server.applications.petstore.signon-ejb_jar.UserEJB.bean-pool

7. List the monitorable subcomponents in the method `getUserName` for the entity bean `UserEJB` in the EJB module `signon-ejb_jar` of the `PetStore` application:

       asadmin> list -m
       server.applications.petstore.signon-ejb_jar.UserEJB.bean-methods.getUserName

   Returns:

       Nothing to list at server.applications.petstore.signon-ejb_jar.
       UserEJB.bean-methods.getUserName. To get the valid names beginning with a
       string, use the wildcard "*" character. For example, to list all names
       that begin with "server", use "list server*".

8. There are no monitorable subcomponents for methods. Get all monitorable statistics for the method `getUserName`.

       asadmin> get -m
       server.applications.petstore.signon-ejb_jar.UserEJB.bean-methods.getUserName.*

   Returns:

       server.applications.petstore.signon-ejb_jar.UserEJB.bean-methods.
       getUserName.executiontime-count = 0
       server.applications.petstore.signon-ejb_jar.UserEJB.bean-methods.
       getUserName.executiontime-description = Provides the time in milliseconds
          spent during the last successful/unsuccessful attempt to execute the
          operation.
       server.applications.petstore.signon-ejb_jar.UserEJB.bean-methods.
       getUserName.executiontime-lastsampletime = 1079981809259
       server.applications.petstore.signon-ejb_jar.UserEJB.bean-methods.
       getUserName.executiontime-name = ExecutionTime
       server.applications.petstore.signon-ejb_jar.UserEJB.bean-methods.
       getUserName.executiontime-starttime = 1079980593137
       server.applications.petstore.signon-ejb_jar.UserEJB.bean-methods.
       getUserName.executiontime-unit = count
       server.applications.petstore.signon-ejb_jar.UserEJB.bean-methods.
       getUserName.methodstatistic-count = 0
       server.applications.petstore.signon-ejb_jar.UserEJB.bean-methods.
       getUserName.methodstatistic-description = Provides the number of times an
          operation was called, the total time that was spent during the
          invocation and so on.
       server.applications.petstore.signon-ejb_jar.UserEJB.bean-methods.
       getUserName.methodstatistic-lastsampletime = 1079980593137
       server.applications.petstore.signon-ejb_jar.UserEJB.bean-methods.
       getUserName.methodstatistic-maxtime = 0
       server.applications.petstore.signon-ejb_jar.UserEJB.bean-methods.
       getUserName.methodstatistic-mintime = 0
       server.applications.petstore.signon-ejb_jar.UserEJB.bean-methods.
       getUserName.methodstatistic-name = ExecutionTime
       server.applications.petstore.signon-ejb_jar.UserEJB.bean-methods.
       getUserName.methodstatistic-starttime = 1079980593137
       server.applications.petstore.signon-ejb_jar.UserEJB.bean-methods.
       getUserName.methodstatistic-totaltime = 0
       server.applications.petstore.signon-ejb_jar.UserEJB.bean-methods.
       getUserName.methodstatistic-unit =
        server.applications.petstore.signon-ejb_jar.UserEJB.bean-methods.
       getUserName.totalnumerrors-count = 0
       server.applications.petstore.signon-ejb_jar.UserEJB.bean-methods.
       getUserName.totalnumerrors-description = Provides the total number of errors
          that occured during invocation or execution of an operation.
       server.applications.petstore.signon-ejb_jar.UserEJB.bean-methods.
       getUserName.totalnumerrors-lastsampletime = 1079981809273
       server.applications.petstore.signon-ejb_jar.UserEJB.bean-methods.
       getUserName.totalnumerrors-name = TotalNumErrors
       server.applications.petstore.signon-ejb_jar.UserEJB.bean-methods.
       getUserName.totalnumerrors-starttime = 1079980593137
       server.applications.petstore.signon-ejb_jar.UserEJB.bean-methods.
       getUserName.totalnumerrors-unit = count
       server.applications.petstore.signon-ejb_jar.UserEJB.bean-methods.
       getUserName.totalnumsuccess-count = 0
       server.applications.petstore.signon-ejb_jar.UserEJB.bean-methods.
       getUserName.totalnumsuccess-description = Provides the total number of
          successful invocations of the method.
       server.applications.petstore.signon-ejb_jar.UserEJB.bean-methods.
       getUserName.totalnumsuccess-lastsampletime = 1079981809255
       server.applications.petstore.signon-ejb_jar.UserEJB.bean-methods.
       getUserName.totalnumsuccess-name = TotalNumSuccess
       server.applications.petstore.signon-ejb_jar.UserEJB.bean-methods.
       getUserName.totalnumsuccess-starttime = 1079980593137
       server.applications.petstore.signon-ejb_jar.UserEJB.bean-methods.
       getUserName.totalnumsuccess-unit = count

9. To also get a specific statistic, such as execution time, use a command such as the following:

       asadmin> get -m server.applications.petstore.signon-ejb_jar.
       UserEJB.bean-methods.getUserName.executiontime-count

   Returns:

       server.applications.petstore.signon-ejb_jar.UserEJB.bean-methods.
       getUserName.executiontime-count = 1

### Expected Output for list and get Commands at All Levels

The following tables show the command, dotted name, and corresponding output at each level of the tree.

Table 16–33 Top Level

Command | Dotted Name | Output
--- | --- | ---
`list -m` | `server` |
    server.applicationsserver.thread-poolsserver.
    resourcesserver.http-serviceserver.transaction-
    serviceserver.orb.connection-managersserver.orb.
    connection-managers.orb\.Connections\.Inbound\.
    AcceptedConnectionsserver.jvm
`list -m` | `server.*` | Hierarchy of child nodes below this node.
`get -m` | `server.*` | No output except a message saying there are no attributes at this node.

The following table shows the command, dotted name, and corresponding output for the applications level.

Table 16–34 Applications Level

Command | Dotted Name | Output
--- | --- | ---
`list -m` | `server.applications` or `*applications` |
    appl1app2web-module1_warejb-module2_jar...
`list -m` | `server.applications.*` or `*applications.*` | Hierarchy of child nodes below this node.
`get -m` | `server.applications.*` or `*applications.*` | No output except message saying there are no attributes at this node.

The following table shows the command, dotted name, and corresponding output for stand-alone modules and enterprise applications at the applications level.

Table 16–35 Applications - Enterprise Applications and Standalone Modules

Command | Dotted Name | Output
--- | --- | ---
`list -m` | `server.applications.app1` or `*app1` Note: this level is only applicable if an enterprise application has been deployed. It is not applicable if a standalone module is deployed. | `ejb-module1_jarweb-module2_warejb-module3_jarweb-module3_war...`
`list -m` | `server.applications.app1.*` or `*app1.*` | Hierarchy of child nodes below this node.
`get -m` | `server.applications.app1.*` or `*app1.*` | No output except message saying there are no attributes at this node.
`list -m` | `server.applications.app1.ejb-module1_jar` or `*ejb-module1_jar` or `server.applications.ejb-module1_jar` | `bean1bean2bean3...`
`list -m` | `server.applications.app1.ejb-module1_jar` or `*ejb-module1_jar` or `server.applications.ejb-module1_jar` | Hierarchy of child nodes below this node.
`get -m` | `server.applications.app1.ejb-module1_jar.*` or `*ejb-module1_jar.*` or `server.applications.ejb-module1_jar.*` | No output except message saying there are no attributes at this node.
`list -m` | `server.applications.app1.ejb-module1_jar.bean1` Note: In standalone modules, the node containing the application name (`app1` in this example) will not appear. | List of child nodes: `bean-poolbean-cachebean-method`
`list -m` | `server.applications.app1.ejb-module1_jar.bean1` Note: In standalone modules, the node containing the application name (`app1` in this example) will not appear. | Hierarchy of child nodes and a list of all attributes for this node and for any subsequent child nodes.
`get -m` | `server.applications.app1.ejb-module1_jar.bean1.*` Note: In standalone modules, the node containing the application name (`app1` in this example) does not appear. | The following attributes and their associated values:
    CreateCount_CountCreateCount_
    DescriptionCreateCount_
    LastSampleTimeCreateCount_
    NameCreateCount_
    StartTimeCreateCount_
    UnitMethodReadyCount_
    CurrentMethodReadyCount_
    DescriptionMethodReadyCount_
    HighWaterMarkMethodReadyCount_
    LastSampleTimeMethodReadyCount_
    LowWaterMarkMethodReadyCount_
    NameMethodReadyCount_
    StartTimeMethodReadyCount_
    UnitRemoveCount_CountRemoveCount_
    DescriptionRemoveCount_
    LastSampleTimeRemoveCount_
    NameRemoveCount_StartTimeAttribute
    RemoveCount_Unit
`list -m` | `server.applications.app1.ejb-module1_jar.bean1.bean-pool` Note: In standalone modules, the node containing the application name (`app1` in this example) will not appear. | No attributes, but a message saying: Nothing to list at `server.applications.appl.ejb-module1_jar.bean1-cache`. To get the valid names beginning with a string, use the wildcard (*) character. For example, to list all names that begin with `server`, use `list server*`.
`get -m` | `server.applications.app1.ejb-module1_jar.bean1.bean-pool.*` Note: In standalone modules, the node containing the application name (`app1` in this example) will not appear. | List of attributes and values corresponding to EJB Pool attributes as described in Table 1-4.
`list -m` | `server.applications.app1.ejb-module1_jar.bean1.bean-cache` Note: In standalone modules, the node containing the application name (`app1` in this example) will not appear. | No attributes, but a message saying “Use get command with the --monitor option to view this node’s attributes and values.”
`get -m` | `server.applications.app1.ejb-module1_jar.bean1.bean-cache.*` Note: In standalone modules, the node containing the application name (`app1` in this example) does not appear. | List of attributes and values corresponding to EJB Cache attributes as described in Table 1-5.
`list -m` | `server.applications.app1.ejb-module1_jar.bean1.bean-method.method1` Note: In standalone modules, the node containing the application name (`app1` in this example) will not appear. | No attributes, but a message saying “Use get command with the --monitor option to view this node’s attributes and values.”
`get -m` | `server.applications.app1.ejb-module1_jar.bean1.bean-method.method1.*` Note: In standalone modules, the node containing the application name (`app1` in this example) will not appear. | List of attributes and values corresponding to EJB Methods attributes as described in Table 1-2.
`list -m` | `server.applications.app1.web-module1_war` | Displays the virtual server(s) assigned to the module.
`get -m` | `server.applications.app1.web-module1_war.*` | No output except a message saying there are no attributes at this node.
`list -m` | `server.applications.app1.web-module1_war.virtual_server` | Displays list of servlets registered.
`get -m` | `server.applications.app1.web-module1_war.virtual_server.*` | No output except a message saying there are no attributes at this node.
`list -m` | `server.applications.app1.web-module1_war.virtual_server.servlet1` | No attributes, but a message saying “Use get command with the --monitor option to view this node’s attributes and values.”
`get -m` | `server.applications.app1.web-module1_war.virtual_server.servlet1.*` | List of attributes and values corresponding to web container (Servlet) attributes as described in Table 1-7.

The following table shows the command, dotted name, and corresponding output for the HTTP Service level.

Table 16–36 HTTP-Service Level

Command | Dotted Name | Output
--- | --- | ---
`list -m` | `server.http-service` | List of virtual servers.
`get -m` | `server.http-service.*` | No output except message saying there are no attributes at this node.
`list -m` | `server.http-service.server` | List of HTTP Listeners.
`get -m` | `server.http-service.server.*` | No output except message saying there are no attributes at this node.
`list -m` | `server.http-service.server.http-listener1` | No attributes, but a message saying “Use get command with the --monitor option to view this node’s attributes and values.”
`get -m` | `server.http-service.server.*` | List of attributes and values corresponding to HTTP Service attributes as described in Table 1-9.

The following table shows the command, dotted name, and corresponding output for the thread pools level.

Table 16–37 Thread-Pools Level

Command | Dotted Name | Output
--- | --- | ---
`list -m` | `server.thread-pools` | List of thread-pool names.
`get -m` | `server.thread-pools.*` | No output except message saying there are no attributes at this node.
`list -m` | `server.thread-pools.orb\.threadpool\.thread-pool-1` | No attributes, but a message saying “Use get command with the --monitor option to view this node’s attributes and values.”
`get -m` | `server.thread-pools..orb\.threadpool\.thread-pool-1.*` | List of attributes and values corresponding to Thread Pool attributes as described in Table 1-14.

The following table shows the command, dotted name, and corresponding output for the resources level.

Table 16–38 Resources Level

Command | Dotted Name | Output
--- | --- | ---
`list -m` | `server.resources` | List of pool names.
`get -m` | `server.resources.*` | No output except message saying there are no attributes at this node.
`list -m` | `server.resources.jdbc-connection-pool-pool.connection-pool1` | No attributes, but a message saying “Use get command with the --monitor option to view this node’s attributes and values.”
`get -m` | `server.resources.jdbc-connection-pool-pool.connection-pool1.*` | List of attributes and values corresponding to Connection Pool attributes as described in Table 1-10.

The following table shows the command, dotted name, and corresponding output for the transaction service level.

Table 16–39 Transaction-Service Level

Command | Dotted Name | Output
--- | --- | ---
`list -m` | `server.transaction-service` | No attributes, but a message saying “Use get command with the --monitor option to view this node’s attributes and values.”
`get -m` | `server.transaction-service.*` | List of attributes and values corresponding to Transaction Service attributes as described in Table 1-15.

The following table shows the command, dotted name, and corresponding output for the ORB level.

Table 16–40 ORB Level

Command | Dotted Name | Output
--- | --- | ---
`list -m` | `server.orb` | `server-orb.connection-managers`
`get -m` | `server.orb.*` | No output except message saying there are no attributes at this node.
`list -m` | `server.orb.connection-managers` | Name(s) of ORB connection managers.
`get -m` | `server.orb.connection-managers.*` | No output except message saying there are no attributes at this node.
`list -m` | `server.orb.connection-managers.orb\.Connections\.Inbound\.AcceptedConnections` | No attributes, but a message saying “Use get command with the --monitor option to view this node’s attributes and values.”
`get -m` | `server.orb.connection-managers.orb\.Connections\.Inbound\.AcceptedConnections.*` | List of attributes and values corresponding to ORB Connection Manager attributes as described in Table 1-13.

The following table shows the command, dotted name, and corresponding output for the JVM level.

Table 16–41 JVM Level

Command | Dotted Name | Output
--- | --- | ---
`list -m` | `server.jvm` | No attributes, but a message saying “Use get command with the `--monitor` option to view this node’s attributes and values.”
`get -m` | `server.jvm.*` | List of attributes and values corresponding to JVM attributes as described in Table 1-16.

- Previous: Admin Console Tasks for Enabling and Disabling Monitoring
- Next: Using JConsole

- © 2010, Oracle Corporation and/or its affiliates