BMC Software, Inc., Confidential and Proprietary Information
Managing the BEA WebLogic Environment 4-3
• ConnectionStatus (LOCAL_MANAGED, page B-14; MANAGED,
page B-16; SERVER, page B-18):
Indicates that the PATROL collector cannot communicate with the
server. You may need to restart the WebLogic server.
•
ClusteredServerStatus (CLUSTER, page B-4):
Indicates whether a clustered server is up or down.
•
HealthStatus (JMSSERVER, page B-12; LOCAL_MANAGED, page
B-14; MANAGED, page B-16; SERVER, page B-18):
There are four of these parameters for different types of servers.
Each indicates an assessment of the health of the server. These
parameters are shown only for BEA WebLogic Server 7.0 and 8.1.
•
TransactionTimeoutRate (EJB_HOME, page B-7):
Set alarm values to flag abnormally high numbers of timeouts, which
may indicate a problem with your EJB pool or may indicate another
problem that is preventing EJBs from completing fast enough to free
up connections.
•
ExecuteQueueLength (EXEC_QUEUE, page B-8):
Set alarm values to flag abnormally long queues.
•
PoolState (JDBC, page B-10):
Indicates whether pool is available, or has been shutdown or
suspended.
Working with Events
Some features in PATROL for BEA WebLogic (such as log file sniffing
and JMX MBean monitoring) are intended to be used in conjunction with
PATROL events. This section provides a brief look at how events can be
managed using the PATROL Event Manager. See the PATROL Event
Manager Help in your PATROL Console for more information.
