Monitoring the WebLogic Persistent Store

7 Monitoring the WebLogic Persistent Store

This chapter explains how to monitor the WebLogic Server persistent store.

Monitoring a Persistent Store
You can monitor statistics for each existing persistent store and for each open store connection.
Monitoring Stores
Each persistent store is represented at run time by an instance of the PersistentStoreRuntimeMBean.
Monitoring Store Connections
For each open persistent store connection, the persistent store also registers a PersistentStoreConnectionRuntimemMBean.

You can monitor statistics for each existing persistent store and for each open store connection.

Parent topic: Monitoring the WebLogic Persistent Store

Each persistent store is represented at run time by an instance of the PersistentStoreRuntimeMBean.

The PersistentStoreRuntimeMBean provides the following options.

Table 7-1 Persistent Store Run-time Options

Option	What It Does
CreateCount	Number of create requests issued to this persistent store.
ReadCount	Number of read requests issued to this persistent store.
UpdateCount	Number of update requests issued by this persistent store.
DeleteCount	Number of delete requests issued by this persistent store.
ObjectCount	Number of objects contained in the persistent store.
Connections	Number of active connections in the persistent store.
PhysicalWriteCount	Number of times the persistent store flushes its data to durable storage.

Parent topic: Monitoring the WebLogic Persistent Store

For each open persistent store connection, the persistent store also registers a PersistentStoreConnectionRuntimemMBean.

Table 7-2 Persistent Store Connection Runtime Options

Option	What It Does
CreateCount	Number of create requests issued to this connection.
ReadCount	Number of read requests issued to this connection.
UpdateCount	Number of update requests issued by this connection.
DeleteCount	Number of delete requests issued by this connection.
ObjectCount	Number of objects contained in the connection.

Table 7-3 defines most of the run-time prefix names of the WebLogic services and subsystems that can create a connection to the persistent store.

Table 7-3 Persistent Store Run-Time Prefix Names

Subsystem/Service	Run-Time Prefix Name
Deployment	`weblogic.deploy.internal` where `internal` is the name of the deployment connection
Diagnostic Service	`weblogic.diagnostics.internal` where `internal` is the logical name of the diagnostic archive connection
EJB Timer Services	`weblogic.ejb.timer.internal` where `internal` uniquely identifies EJB deployments in a server instance
JMS Service	JMS server: `weblogic.messaging.jmsServer.internal` where `internal` is the name of the JMS server connection JMS durable subscriber: `weblogic.messaging.jmsServer.durablesubs.internal` where `internal` is the name of the durable subscriber connection
JTA Transaction Log (TLOG)	`weblogic.transaction.internal` where `internal` is the name of the TLOG connection
Path Service	`weblogic.messaging.PathService.internal` where `internal` is the name of the path service connection
SAF Service	SAF agent `weblogic.messaging.SAFAgent@server1.internal` where `internal` is the name of the SAF agent's connection SAF durable subscriber: `weblogic.messaging.SAFAgent@server1.durablesubs.internal` where `internal` is the name of the durable subscriber connection
Web Services	`weblogic.wsee.server.store.internal` where `internal` is the name of the Web Service's connection

Parent topic: Monitoring the WebLogic Persistent Store