サポートと今すぐチャット
サポートとのチャット

Foglight for Microsoft DOT NET 5.9.13 - Application Servers User Guide

Monitoring Application Servers Monitoring Systems Monitoring Servers Monitoring Deployed Applications Monitoring Requests Managing Traces Using Object Tracking to Locate Memory Leaks Monitoring Methods Application Servers Monitor Views
JVM view Method Groups view Request Types view Entity EJBs view Message Driven EJBs view Stateful Session EJBs view Stateless Session EJBs view Deployed Applications view JSPs/Servlets components view Resource Adapters components view Web Applications components view Web Services components view .NET views JBoss Services views Oracle Services views Tomcat Services views WebLogic Services views WebSphere Services views JMX Administration dashboard JMX Explorer dashboard
Appendix: Regular Expressions

WebLogic Services views

This section describes the Services views that are specific to WebLogic application servers:

•
WebLogic Execute Queues view
•
WebLogic JDBC Data Sources view
•
WebLogic JMS Servers view
•
WebLogic Security view
•
WebLogic Self-Tuning Thread Pool view
•
WebLogic Store and Forward view
•
WebLogic Work Managers view

WebLogic Execute Queues view

Purpose

Use this view to examine runtime information for all the execute queues in the selected WebLogic server.

 
Table 54. Execute Queues table
Description

Lists all the queues and thread pools for the selected WebLogic server and summarizes the current state of each queue or pool, including its health, thread usage, and information on requests. The graphs below the table display data for the selected queue or pool.

WebLogic JDBC Data Sources view

Purpose

Use this view to monitor the health of the connection pools that the selected WebLogic server uses.

An important indicator of the performance of a JDBC connection pool is the presence or lack of waiters. Especially important to observe is the presence of failed waiters (in the Connection Failures After Waiting column) as these are waiters that were unable to successfully obtain a database connection.

Table 55. JDBC Data Sources table
Description

Lists all the JDBC data sources in the selected WebLogic server and summarizes the state of each data source, including whether it is active, its health status, as well as information on connections, waiters, and the prepared statement cache.

The graphs below the table display historical data related to connection delays, capacities, number of requests, requests forced to wait, and the occurrence of leaked connections.

WebLogic JTA Runtime view

Purpose

Use this view to examine runtime transactions the selected WebLogic server handles. Specifically, it displays transactions that are processing successfully (committing), transactions that cause errors (rollbacks), and transactions that time out (abandoned).

There are four types of rollbacks:

•
Application rollback is expected to occur during the running of an application. High occurrences of application rollbacks may point to a problem in the application.
•
Resource rollbacks can represent problems in the WebLogic resource, such as an unavailable database.
•
System rollbacks can represent serious problems in the WebLogic server.
•
Timeout rollbacks can occur when a transaction cannot complete within the configured timeout interval. This indicates either that you have to increase the interval to allow more time for transactions to complete or that there is a problem in the application or environment that is causing transactions to take too long to complete.
 
Table 56. JTA table
Description

Displays the current JTA runtime statics, including the number of active transactions, the number of named transactions by server, total transactions, cumulative transaction counts, and rollback data. The graphs below the table reflect the historical data in the table.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択