WebLogic Server
monitoring |
- Is the WebLogic server process running?
- Is the memory usage of the server increasing over time?
- Is the server's request processing rate unusually high?
|
| JVM monitoring |
- Is the JVM heap size adequate?
- Is the garbage collection tuned well or is the JVM spending too much time in garbage collection?
- What is the average CPU utilization of the JVM?
- Which threads are responsible for the CPU usage and what lines of code is each thread executing?
- Are there any deadlocks happening in the JVM?
- Which threads are responsible for a deadlock and which lines of code (which modules, classes, files) were they executing prior to the deadlock?
- Are there any blocked threads?
- Which threads are blocking them and which lines of code are responsible for this?
|
| Thread monitoring |
- Are the WebLogic server's execute queues adequately sized?
- Are there too many threads waiting to be serviced, thereby causing slow response time?
|
| Security monitoring |
- How many invalid login attempts have been made to the WebLogic server?
- Are these attempts recurring?
|
| JMS monitoring |
- Are there many pending messages in the messaging server?
- Is the message traffic unusually high?
|
| Connector monitoring |
- What is the usage pattern of connections in a connector pool?
|
| Cluster monitoring |
- Are all the WebLogic servers in the cluster currently available?
- Is the load being balanced across the cluster?
|
| Transaction monitoring |
- How many user transactions are happening?
- Are there too many rollbacks occurring?
|
| Servlet monitoring |
- Which servlet(s) are being extensively accessed?
- What is the average invocation time for each servlet?
|
| EJB Pool monitoring |
- Are there adequate numbers of beans in a bean pool?
- How many beans are in use?
- Are there any clients waiting for a bean?
|
| EJB Cache monitoring |
- Is the cache adequately sized or are there too many cache misses?
- What is the rate of EJB activations and passivations?
|
| EJB Lock monitoring |
- Is there contention for locks?
- How many beans are locked?
- How many attempts have been made to acquire a lock for each bean?
|
JDBC Connection
monitoring |
- Are all the JDBC connection pools available?
- Is each connection pool adequately sized?
- What are the peak usage times and values?
- How many connection leaks have occurred?
|
| JDBC call monitoring |
- How many JDBC calls have been made?
- What was average response time of those calls?
- What are the queries that take a long time to execute?
|
Get Your Free Trial
