Sun Java™ System Application Server Platform Edition 8 Administration Guide |
Chapter 15
MonitoringThis chapter contains information about monitoring components in the Sun Java System Application Server Platform Edition 8. This chapter contains the following sections:
About MonitoringMonitoring the Application Server
You use monitoring to observe the runtime state of various components of the Application Server. With the information on the state of runtime components and processes, you can 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.
General Steps for Monitoring
To monitor the Application Server, you perform these steps:
- Using either the Admin Console or the
asadmin
tool, enable the monitoring of specific services and components. See Enabling and Disabling Monitoring.- In a terminal window, type the
asadmin
list
--monitor “server.*”
command to view the names of the objects that can be monitored.- Type the
asadmin
get --monitor
command and specify a name displayed by thelist
command in the preceding step. Theget
command displays the monitoring statistics.For more information on the
get
andset
commands, see Viewing Monitoring Data With the asadmin Tool.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 this release, just one server instance is permitted.)The following command displays the top level of the tree:
asadmin> list --monitor server
password>
server.applications
server.http-service
server.jvm
server.orb
server.resources
server.thread-pools
server.transaction-serviceThe 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 (*). See EJB Container Statistics and Web Container Statistics.
Figure 15-1 Applications Node Tree Structure
applications
|--- application1
| |--- ejb-module-1
| | |--- ejb1 *
| | |--- cache (for entity/sfsb) *
| | |--- pool (for slsb/mdb/entity) *
| | |--- method
| | |---method1 *
| | |---method2 *
| |--- web-module-1
| | |--- virtual-server-1
| | |---servlet1 *
| | |---servlet2 *
|--- standalone-web-module-1
| | |----- virtual-server-1
| | |---servlet3 *
| | |---servlet4 *
| | |----- virtual-server-2
| | |---servlet3 *(same servlet on different vs)
| | |---servlet5 *
|--- standalone-ejb-module-1
| | |--- ejb2 *
| | |--- cache (for entity/sfsb) *
| | |--- pool (for slsb/mdb/entity) *
| | |--- method
| | |--- method1 *
| | |--- method2 *
|--- application2
The 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 15-2 HTTP Service Schematic
http-service
| |--- virtual-server-1
| | |--- http-listener-1 *
| | |--- http-listener-2 *
| |--- virtual-server-2
| | |--- http-listener-1 *
| | |--- http-listener-2 *
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 Connector Connection Pools Statistics.
Figure 15-3 Resources Schematic
resources
| |---connection-pool1(either connector-coonection-pool or jdbc)*
| |---connection-pool2(either connector-coonection-pool or jdbc)*
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 ORB Statistics.
Figure 15-4 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 15-5 Thread Pool Schematic
thread-pools
| |--- thread-pool-1 *
| |--- thread-pool-2 *
Statistics for Monitored Components and Services
This section describes the monitoring statistics that are available:
EJB Container Statistics
The statistics that are available for the EJB container are described in Table 15-1.
The statistics available for EJB method invocations are listed in Table 15-2.
The statistics available for EJB pools are listed in Table 15-3.
The statistics available for EJB caches are listed in Table 15-4.
Web Container Statistics
The Web container fits into the tree of objects as shown in Figure 15-1. Web container statistics are displayed for each individual web application.
HTTP Service Statistics
The statistics available for the HTTP service are shown in Table 15-6.
JDBC Connection Pools Statistics
You can 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 15-7.
Connector Connection Pools Statistics
The statistics available for the connector connection pool are shown in Table 15-8.
ORB Statistics
The statistics available for the ORB are shown in Table 15-9.
Thread Pools Statistics
The statistics available for the thread pool are shown in Table 15-10.
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 15-11.
Java Virtual Machine (JVM) Statistics
The JVM has monitorable attributes that are always enabled. The statistics available for the JVM are shown in Table 15-12.
Enabling and Disabling MonitoringEnabling and Disabling Monitoring With the Admin Console
- In the tree component, select the Application Server node.
- Click the Monitoring tab.
- On the Monitoring Service page, choose the appropriate value from the combo box opposite the component(s) or service(s) whose monitoring level you wish to change.
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. You can turn monitoring on or off for the following components and services:
- JDBC Connection Pool - set the monitoring level to LOW for this option to monitor all JDBC connection pools.
- 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.
- Thread Pool - set the monitoring level to LOW for this option to monitor all thread pools.
- Web Container - set the monitoring level to LOW for this option to monitor all deployed servlets.
- HTTP Service - set the monitoring level to LOW for this option to monitor all HTTP listeners and virtual servers.
- Connector Connection Pool - set the monitoring level to LOW for this option to monitor all created connector connection pools.
- 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.
- Transaction Service - set the monitoring level to LOW for this option to monitor any transaction subsystem.
- Click Save.
There are no Additional Monitoring Service Properties in this release, so you can ignore the Additional Properties table.
Enabling and Disabling Monitoring With the asadmin Tool
- Use the
get
command to find out what services and components currently have monitoring enabled:asadmin> get server.monitoring-service.module-monitoring-levels.*
Returns:
server.monitoring-service.module-monitoring-levels.
connector-connection-pool = 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.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 --password admin_password server.monitoring-service.module-monitoring-levels.http-service=HIGH
- To disable monitoring, use the
set
command and specifyOFF
for the monitoring level.
Viewing Monitoring Data With the asadmin ToolDotted Names
In the
asadmin
list
andget
commands, you 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 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
You are not expected to know the valid dotted names for
asadmin
list
andget
commands. Thelist
command lets you inspect available monitorable objects, while theget
command used with a wildcard parameter allows you to inspect 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 (*
) will get as its result the current node’s immediate children. For example,list
--monitor
server
will list all immediate children belonging to theserver
node.- Any
list
command that has a dotted name followed by a wildcard of the form.*
will get as its result a hierarchical tree of children nodes from the current node. For example,list --monitor server.applications.*
will list 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 * will get 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*
will get as its result the set of attributes and their values belonging to the current node whose name is sought 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
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.applications
server.http-service
server.thread-pools
server.transaction-serviceYou can also list applications that are currently monitored in the specified server instance. This can be useful when particular monitoring statistics are sought from an application using the
get
command.Example
asadmin> list --monitor server.applications
Returns:
server.applications.MEjbApp
server.applications._ebj_container_timer_app
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
Attempt to get all attributes from a subsystem for a specific object:
asadmin> get --monitor server.jvm.*
Returns:
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
Attempt to get all attributes from a J2EE application:
asadmin> get --monitor server.applications.converter.*
Returns:
No matches resulted from the wildcard expression.
CLI137 Command get failed.There are no monitorable attributes exposed at the J2EE-application level, therefore the command notifies you of this.
Example
Attempt to get a specific attribute from a subsystem:
asadmin> get --monitor server.transaction-service.activecount-count
Returns:
server.transaction-service.activecount-count = 0
Example
Attempt to get an unknown attribute from within a subsystem attribute:
asadmin> get --monitor server.transaction-service.badname
Returns:
No such attribute found from reflecting the corresponding Stats interface: [badname]
CLI137 Command get failed.Petstore Example
The following example illustrates how you might use the
asadmin
tool 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 Sun Java System Application Server Platform Edition 8. 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- You can also get a specific statistic, such as execution time.
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 15-15 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. Not applicable is only a standalone module is deployed.
ejb-module1_jar
web-module2_war
ejb-module3_jar
web-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, but 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
bean1
bean2
bean3
...
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, but 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-pool
bean-cache
bean-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) will not appear.
The following attributes and their associated values:
CreateCount_Count
CreateCount_Description
CreateCount_LastSampleTime
CreateCount_Name
CreateCount_StartTime
CreateCount_Unit
MethodReadyCount_Current
MethodReadyCount_Description
MethodReadyCount_HighWaterMark
MethodReadyCount_LastSampleTime
MethodReadyCount_LowWaterMark
MethodReadyCount_Name
MethodReadyCount_StartTime
MethodReadyCount_Unit
RemoveCount_Count
RemoveCount_Description
RemoveCount_LastSampleTime
RemoveCount_Name
RemoveCount_StartTime
Attribute 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 “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-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 15-3.
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) will not appear.
List of attributes and values corresponding to EJB Cache attributes as described in Table 15-4.
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 15-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, but a message saying there are no attributes at this node.
list -m
server.applications.app1.web-module1_war.
virtual_serverDisplays list of servlets registered.
get -m
server.applications.app1.web-module1_war.
virtual_server.*No output, but a message saying there are no attributes at this node.
list -m
server.applications.app1.web-module1_war.
virtual_server.servlet1No 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 15-5.
Table 15-16 HTTP-Service Level
Command
Dotted Name
Output
list -m
server.http-service
List of virtual servers.
get -m
server.http-service.*
No output, but 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, but message saying there are no attributes at this node.
list -m
server.http-service.server.
http-listener1No 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 15-6.
Table 15-17 Thread-Pools Level
Command
Dotted Name
Output
list -m
server.thread-pools
List of thread-pool names.
get -m
server.thread-pools.*
No output, but message saying there are no attributes at this node.
list -m
server.thread-pools.orb\.threadpool\
.thread-pool-1No 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 15-10.
Table 15-18 Resources Level
Command
Dotted Name
Output
list -m
server.resources
List of pool names.
get -m
server.resources.*
No output, but 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 15-7.
Table 15-19 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 15-11.
Table 15-20 ORB Level
Command
Dotted Name
Output
list -m
server.orb
server-orb.connection-managers
get -m
server.orb.*
No output, but 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, but message saying there are no attributes at this node.
list -m
server.orb.connection-managers.
orb\.Connections\.Inbound\
.AcceptedConnectionsNo 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 15-9.
Table 15-21 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 15-12.