Sun Java System Application Server Platform Edition 8.1 2005Q1 Administration Guide |
Chapter 16
Monitoring Components and ServicesThis chapter contains information about monitoring components using the Application Server Admin Console. This chapter contains the following sections:
About MonitoringMonitoring in the Application Server
Use monitoring to observe the runtime state of various components and services deployed in a server instance of the Sun Java System Application Server Platform Edition 8.1 2005Q1. With the information on the state of runtime components and processes, it is possible to identify performance bottlenecks for tuning purposes, aid capacity planning, predict failures, do root cause analysis in case of failures, and ensure that everything is functioning as expected.
Turning monitoring on reduces performance by increasing overhead.
Overview of Monitoring
To monitor the Application Server, perform these steps:
- Enable the monitoring of specific services and components using either the Admin Console or the
asadmin
tool.For more information on this step, refer to "Admin Console Tasks for Enabling and Disabling Monitoring".
- View monitoring data for the specified services or components using either the Admin Console or the
asadmin
tool.For more information on this step, refer to "Admin Console Tasks for Viewing Monitoring Data".
About the Tree Structure of Monitorable Objects
The Application Server uses a tree structure to track monitorable objects. Because the tree of monitoring objects is dynamic, it changes as components are added, updated, or removed in the instance. The root object in the tree is the server instance name, for example,
server
. (In the Platform Edition, just one server instance is permitted.)The following command displays the top level of the tree:
asadmin> list --monitor server
server.applications
server.http-service
server.connector-service
server.jms-service
server.jvm
server.orb
server.resources
server.thread-poolsThe following sections describe these sub-trees:
The Applications Tree
The following schematic shows the top and child nodes for the various components of enterprise applications. The nodes at which monitoring statistics are available are marked with an asterisk (*). For more information, refer to "EJB Container Statistics" and "Web Container Statistics".
Figure 16-1 Applications Node Tree Structure
applications
|--- application1
| |--- ejb-module-1
| | |--- ejb1 *
| | |--- cache (for entity/sfsb) *
| | |--- pool (for slsb/mdb/entity) *
| | |--- methods
| | |---method1 *
| | |---method2 *
| | |--- stateful-session-store (for sfsb)*
| | |--- timers (for s1sb/entity/mdb) *
| |--- web-module-1
| | |--- virtual-server-1 *
| | |---servlet1 *
| | |---servlet2 *
|--- standalone-web-module-1
| | |----- virtual-server-2 *
| | |---servlet3 *
| | |---servlet4 *
| | |----- virtual-server-3 *
| | |---servlet3 *(same servlet on different vs)
| | |---servlet5 *
|--- standalone-ejb-module-1
| | |--- ejb2 *
| | |--- cache (for entity/sfsb) *
| | |--- pool (for slsb/mdb/entity) *
| | |--- methods
| | |--- method1 *
| | |--- method2 *
|--- application2The HTTP Service Tree
The nodes of the HTTP service are shown in the following schematic. The nodes at which monitoring information is available are marked with an asterisk (*). See "The HTTP Service Tree".
Figure 16-2 HTTP Service Schematic (PE version)
http-service
|--- virtual-server-1
|--- http-listener-1 *
|--- http-listener-2 *
|--- virtual-server-2
|--- http-listener-1 *
|--- http-listener-2 *Figure 16-3 HTTP Service Schematic (EE version)
http-service *
|---connection-queue *
|---dns *
|---file-cache *
|---keep-alive *
|---pwc-thread-pool *
|---virtual-server-1*
| |--- request *
|---virtual-server-2*
| |--- request *The Resources Tree
The resources node holds monitorable attributes for pools such as the JDBC connection pool and connector connection pool. The following schematic shows the top and child nodes for the various resource components. The nodes at which monitoring statistics are available are marked with an asterisk (*). See "JDBC Connection Pools Statistics" and "JMS/Connector Service Statistics".
Figure 16-4 Resources Schematic
resources
|---connection-pool1(either connector-connection-pool or jdbc)*
|---connection-pool2(either connector-connection-pool or jdbc)*The Connector Service Tree
The connector services node holds monitorable attributes for pools such as the connector connection pool. The following schematic shows the top and child nodes for the various connector service components. The nodes at which monitoring statistics are available are marked with an asterisk (*). See "JMS/Connector Service Statistics".
Figure 16-5 Connector Service Schematic
connector-service
|--- resource-adapter-1
| |-- connection-pools
| | |-- pool-1 (All pool stats for this pool)
| |-- work-management (All work mgmt stats for this RA)The JMS Service Tree
The JMS services node holds monitorable attributes for pools such as the connector connection pool. The following schematic shows the top and child nodes for the various JMS service components. The nodes at which monitoring statistics are available are marked with an asterisk (*).
Figure 16-6 JMS Service Schematic
jms-service
|-- connection-factories [AKA conn. pools in the RA world]
| |-- connection-factory-1 (All CF stats for this CF)
|-- work-management (All work mgmt stats for the MQ-RA)The ORB Tree
The ORB node holds monitorable attributes for connection managers. The following schematic shows the top and child nodes for the ORB components. The nodes at which monitoring statistics are available are marked with an asterisk (*). See "Statistics for Connection Managers in an ORB".
Figure 16-7 ORB Schematic
orb
|--- connection-managers
| |--- connection-manager-1 *
| |--- connection-manager-1 *The Thread Pool Tree
The thread pool node holds monitorable attributes for connection managers. The following schematic shows the top and child nodes for the ORB components. The nodes at which monitoring statistics are available are marked with an asterisk (*). See "Thread Pools Statistics".
Figure 16-8 Thread Pool Schematic
thread-pools
| |--- thread-pool-1 *
| |--- thread-pool-2 *About Statistics for Monitored Components and Services
This section describes the monitoring statistics that are available:
EJB Container Statistics
EJB statistics are described in Table 16-1.
The statistics available for EJB method invocations are listed in Table 16-2.
The statistics for EJB Session Stores are listed in Table 16-3.
The statistics available for EJB pools are listed in Table 16-4.
The statistics available for EJB caches are listed in Table 16-5.
The statistics available for Timers are listed in Table 16-6.
Web Container Statistics
The web container fits into the tree of objects as shown in Figure 16-1. Web container statistics are displayed for each individual web application. Statistics available for the web container for Servlets are shown in Table 16-7 and statistics available for web modules are shown in Table 16-8.
Statistics available for web modules are shown in Table 16-8.
HTTP Service Statistics
The statistics available for the HTTP service are shown in Table 16-9. These statistics are applicable to the Platform Edition only. For statistics for the HTTP Service on the Enterprise Edition, see Table 16-32.
JDBC Connection Pools Statistics
Monitor JDBC resources to measure performance and capture resource usage at runtime. As the creation of JDBC connections are expensive and frequently cause performance bottlenecks in applications, it is crucial to monitor how a JDBC connection pool is releasing and creating new connections and how many threads are waiting to retrieve a connection from a particular pool.
The statistics available for the JDBC connection pool are shown in Table 16-10.
JMS/Connector Service Statistics
The statistics available for the connector connection pool are shown in Table 16-11. Statistics for Connector Work Management are shown in Table 16-12.
Statistics available for Connector Work Management are listed in Table 16-12,
Statistics for Connection Managers in an ORB
The statistics available for the connection manager in an ORB are listed in Table 16-13.
Thread Pools Statistics
The statistics available for the thread pool are shown in Table 16-14.
Transaction Service Statistics
The transaction service allows the client 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. The statistics available for the transaction service are shown in Table 16-15.
Java Virtual Machine (JVM) Statistics
The JVM has monitorable attributes that are always enabled. The statistics available for the JVM are shown in Table 16-16.
JVM Statistics in J2SE 5.0
If the Application Server is configured to run on J2SE version 5.0 or higher, additional monitoring information can be obtained from the JVM. Set the monitoring level to LOW to enable the display of this additional information. Set the monitoring level to HIGH to also view information pertaining to each live thread in the system. More information on the additional monitoring features available in J2SE 5.0 is available in a document titled Monitoring and Management for the Java Platform, which is available from the following URL:
http://java.sun.com/j2se/1.5.0/docs/guide/management/
The J2SE 5.0 monitoring tools are discussed at:
http://java.sun.com/j2se/1.5.0/docs/tooldocs/#manage
The statistics available for class loading in the JVM in J2SE 5.0 are shown in Table 16-17.
The statistics available for compilation in the JVM in J2SE 5.0 are shown in Table 16-18.
Table 16-18 JVM Statistics for J2SE 5.0 - Compilation
Statistic
Data Type
Description
totalcompilationtime
CountStatistic
Accumulated time (in milliseconds) spent in compilation.
The statistics available for garbage collection in the JVM in J2SE 5.0 are shown in Table 16-19.
The statistics available for memory in the JVM in J2SE 5.0 are shown in Table 16-20.
The statistics available for the operating system in the JVM in J2SE 5.0 are shown in Table 16-21.
The statistics available for the runtime in the JVM in J2SE 5.0 are shown in Table 16-22.
The statistics available for
ThreadInfo
in the JVM in J2SE 5.0 are shown in Table 16-23.
The statistics available for threads in the JVM in J2SE 5.0 are shown in Table 16-24.
Production Web Container (PWC) Statistics
Statistics are available for the following PWC components and services on the Enterprise Edition (EE) of the Application Server:
- Table 16-25, PWC Virtual Server
- Table 16-26, PWC Request
- Table 16-27, PWC File Cache
- Table 16-28, PWC Keep Alive
- Table 16-29, PWC DNS
- Table 16-30, PWC Thread Pool
- Table 16-31, PWC Connection Queue
- Table 16-32, PWC HTTP Service
Statistics for PWC virtual servers are listed in Table 16-25.
The statistics available for PWC requests are listed in Table 16-26.
The cache information section provides information on how the file cache is being used. Statistics for PWC file caches are listed in Table 16-27.
This section provides information about the server's HTTP-level keep-alive system. The statistics available for PWC Keep Alive are listed in Table 16-28.
The DNS Cache caches IP addresses and DNS names. The server’s DNS cache is disabled by default. A single cache entry represents a singular IP address or DNS name lookup. The statistics available for PWC DNS are listed in Table 16-29.
Statistics for PWC thread pools are listed in Table 16-30.
The Connection Queue is the queue in which requests are held prior to being serviced. Statistics for the connection queue show the number of sessions in the queue and the average delay before the connection is accepted. Statistics for PWC connection queues are listed in Table 16-31.
Statistics for PWC HTTP service are listed in Table 16-32.
Admin Console Tasks for Enabling and Disabling MonitoringConfiguring Monitoring Levels Using the Admin Console
- Access the Monitoring Service page. To do this,
- On the Monitoring Service page, choose the appropriate value from the combo box opposite the component(s) or service(s) whose monitoring level is changing.
By default, monitoring is turned off for all components and services except for the Java Virtual Machine (JVM), which is always monitorable. To turn monitoring on, select LOW or HIGH from the combo box. To turn monitoring off, select OFF from the combo box. It is possible to turn monitoring on or off for the following components and services:
- JVM - Set the monitoring level to LOW for this option to monitor the Java Virtual Machine.
- HTTP Service - Set the monitoring level to LOW for this option to monitor all HTTP listeners and virtual servers.
- Transaction Service - Set the monitoring level to LOW for this option to monitor any transaction subsystem.
- JMS/Connector Service - Set the monitoring level to LOW for this option to monitor any Java Message Service (JMS).
- ORB - Set the monitoring level to LOW for this option to monitor the system ORB used by the Application Server core and its connection managers.
- Web Container - Set the monitoring level to LOW for this option to monitor all deployed servlets.
- EJB Container - Set the monitoring level to LOW for this option to monitor all deployed EJBs, EJB pools, and EJB caches. Set this method to HIGH to also monitor EJB business methods.
- JDBC Connection Pool - Set the monitoring level to LOW for this option to monitor all JDBC connection pools.
- Thread Pool - Set the monitoring level to LOW for this option to monitor all thread pools.
- Click Save.
There are no Additional Monitoring Service Properties in this release, therefore ignore the Additional Properties table.
Equivalent
asadmin
command:set
, for example, to turn on monitoring for the HTTP Service, use the followingasadmin
command:asadmin> set --user admin_user server.monitoring-service.module-monitoring-levels.http-service=LOW
Configuring Monitoring Using the asadmin Tool
To turn monitoring off, or to set a level for monitoring a component or service, you can use the Admin Console as described in "Configuring Monitoring Levels Using the Admin Console", or use the
asadmin
tool as described in this section.
- Use the
get
command to find out what services and components currently have monitoring enabled:asadmin> get --user admin_user server.monitoring-service.module-monitoring-levels.*
Returns:
server.monitoring-service.module-monitoring-levels.
connector-connection-pool = OFF
server.monitoring-service.module-monitoring-levels.
connector-service = OFF
server.monitoring-service.module-monitoring-levels.ejb-container = OFF
server.monitoring-service.module-monitoring-levels.http-service = OFF
server.monitoring-service.module-monitoring-levels.jdbc-connection-pool = OFF
server.monitoring-service.module-monitoring-levels.jms-service = OFF
server.monitoring-service.module-monitoring-levels.jvm = OFF
server.monitoring-service.module-monitoring-levels.orb = OFF
server.monitoring-service.module-monitoring-levels.thread-pool = OFF
server.monitoring-service.module-monitoring-levels.transaction-service = OFF
server.monitoring-service.module-monitoring-levels.web-container = OFF- Use the
set
command to enable monitoring.For example, to enable monitoring for the HTTP service:
asadmin> set --user admin_user server.monitoring-service.module-monitoring-levels.http-service=LOW
To disable monitoring, use the
set
command and specifyOFF
for the monitoring level.
Admin Console Tasks for Viewing Monitoring DataViewing Monitoring Data in the Admin Console
To view monitoring data for a component or service deployed in a server instance using the Application Server Admin Console, follow these steps. For more description on the attributes for each component or service, refer to "About Statistics for Monitored Components and Services".
- Access the Monitoring page. To do this:
- 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 "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".
- If you do not see the component or service you wish to monitor in this list, 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 "Configuring Monitoring Levels Using the Admin Console" or "Configuring Monitoring Using the asadmin Tool".
- 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 "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".
- 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 "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".
- 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. 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 followingasadmin
command:asadmin> get --monitor server.jvm.*
Viewing Monitoring Data With the asadmin Tool
Using the asadmin Tool to View Monitoring Data
To view monitoring data using the
asadmin
tool, use theasadmin
list
andasadmin
get
commands followed by the dotted name of a monitorable object. As a general approach to using theasadmin
tool to view monitoring data, follow these steps:
- 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 --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-poolsSun Java System Application Server Platform Edition 8.1 2005Q1For 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 thelist
command, refer to "Understanding and Specifying Dotted Names".- 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 theasadmin
get
command in a terminal window, specifying a name displayed by thelist
command in the preceding step. The following example attempts to get all attributes from a subsystem for a specific object:asadmin> get --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 = millisecondsSun Java System Application Server Platform Edition 8.1 2005Q1For 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 theget
command, refer to "Understanding and Specifying Dotted Names".Understanding and Specifying Dotted Names
In the
asadmin
list
andget
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 formtype.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 thehttp-service
of instanceserver
, 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 calledbytesreceived-lastsampletime
. The following name addresses thebytesreceived
attribute:server.http-service.server.http-listener-1.
bytesreceived-lastsampletime
The administrator is not expected to know the valid dotted names for
asadmin
list
andget
commands. Thelist
command displays available monitorable objects, while theget
command used with a wildcard parameter allows the inspection of all available attributes on any monitorable object.The underlying assumptions for using the
list
andget
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
--monitor
server
lists all immediate children belonging to theserver
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 --monitor server.applications.*
lists all children ofapplications
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 --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 sub-components for a server instance. For a more complete listing oflist
examples, see "Expected Output for list and get Commands at All Levels".Example 1
asadmin> list --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-poolsIt 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 --monitor server.applications
Returns:
server.applications.adminapp
server.applications.admingui
server.applications.myAppFor a more comprehensive example, see "Petstore Example".
Examples for the get --monitor Command
This command retrieves the following monitored information:
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 --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 = millisecondsExample 2
Attempt to get all attributes from a J2EE application:
asadmin> get --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 --monitor
server.jvm.uptime-lastsampletimeReturns:
server.jvm.uptime-lastsampletime = 1093215374813
Example 4
Attempt to get an unknown attribute from within a subsystem attribute:
asadmin> get --monitor server.jvm.badname
Returns:
No such attribute found from reflecting the corresponding Stats interface: [badname]
CLI137 Command get failed.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 thelist
andget
commands are used to access desired statistics on a method.
- Start the Application Server and the
asadmin
tool.- 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=4848
- List monitorable components for instance
server
:
asadmin>list --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-poolsThe list of monitorable components includes
thread-pools
,http-service
,resources
, and all deployed (and enabled)applications
.- 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- 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- List the monitorable subcomponents in the entity bean
UserEJB
for the EJB modulesignon-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- List the monitorable subcomponents in the method
getUserName
for the entity beanUserEJB
in the EJB modulesignon-ejb_jar
of the Petstore application:asadmin>list
-m server.applications.petstore.signon-ejb_jar.
UserEJB.bean-methods.getUserNameReturns:
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*”.- 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- 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-countReturns:
server.applications.petstore.signon-ejb_jar.UserEJB.bean-methods.
getUserName.executiontime-count = 1Expected 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-34 shows the command, dotted name, and corresponding output for the applications level.
Table 16-35 shows the command, dotted name, and corresponding output for stand-alone modules and enterprise applications at the applications level.
Table 16-36 shows the command, dotted name, and corresponding output for the HTTP Service level.
Table 16-37 shows the command, dotted name, and corresponding output for the thread pools level.
Table 16-38 shows the command, dotted name, and corresponding output for the resources level.
Table 16-39 shows the command, dotted name, and corresponding output for the transaction service level.
Table 16-40 shows the command, dotted name, and corresponding output for the ORB level.
Table 16-34 shows the command, dotted name, and corresponding output for the JVM level.
Using JConsoleFor JConsole to work with the Application Server, security has to be disabled for the JMX connector. The current version of the Application Server (SE/EE edition) has security enabled by default.
To disable security for the JMX Connector, use one of these techniques:
For the PE version, the JMX Connector is disabled by default, therefore there is no need to change any configuration for PE.