WebLogic: monitoring
On WebLogic, you should monitor work manager thread utilization, garbage collection, and connection pool usage regularly.
- Work Manager Thread Utilization
- Track the average and maximum number of active execute threads through third-party tools or custom-developed JMX-based programs.
- Correlate that number to the workload level issued to the application servers.
- Either using mathematical projections or system tests, estimate the number of concurrent threads expected during your peak operational periods. As a general rule, you should plan to keep the average active threads to 15 or less.
- Garbage Collection
- Monitor the frequency and health of the JVM's heap management. Please see the section relevant to your JVM in General JVM recommendations.
- Connection Pool Usage
- Check if Connection High is equal to the JDBC pool size - the Connection High is the highest number of connections ever reached. The JDBC pool is equal to the maximum possible transaction concurrency level plus a safety buffer of two. The Connection High should not be the same as the JDBC pool size.