Technical data

Monitoring Servers
Administration Guide 5-3
You can access monitoring data for each WebLogic server from the monitoring tabs
for that server. The Logging tab provides access to the local log for the server (that is,
the log on the machine where the server is running).
The Monitoring
→General tab page indicates the current status and provides access to
the Active Queues table, the Active Sockets table, and the Connections table. The
Active Execute Queues table provides performance information such as the oldest
pending request and the queue throughput.
Performance
The Monitoring→Performance tab graphs real-time data on JVM memory heap usage
and request throughput. This tab page also enables you to force the JVM to perform
garbage collection on the memory heap.
The Java heap is a repository for Java objects (live and dead). Normally you do not
need to perform garbage collection manually because the JVM does this automatically.
When the JVM begins to run out of memory, it halts all execution and uses a garbage
collection algorithm to free up space no longer used by Java applications.
On the other hand, developers debugging applications may have occasion to force
garbage collection manually. Manual garbage collection may be useful, for example,
if they are testing for memory leaks that rapidly consume JVM memory.
Server Security
The Monitoring→Security tab provides statistics about invalid login attempts and
locked and unlocked users.
JMS
The Monitoring→JMS tab provides statistics on JMS servers and connections. This
page also provides links to the tables of active JMS connections and active JMS
servers, which monitor such attributes as total current sessions.
JTA
The Monitoring→JTA tab provides statistics on the Java Transactions subsystem such
as total transactions and total rollbacks. The page provides links to tables that list
transactions by resource and name, and a table of in-flight transactions.