Network Deployment (Distributed operating systems), v8.0 > Troubleshoot and support > Work with Diagnostic Providers

Diagnostic Providers

Diagnostic Providers view configuration and state of components within an application server environment.

WAS components set in diagnostic domains, with larger components having multiple diagnostic domains. For example, the Connection Manager logically consists of multiple data sources and connection factories that each have separate diagnostic domains.

Diagnostic Provider MBeans

A diagnostic domain receives services from a Diagnostic Provider MBean that queries...

• startup configuration
• current configuration
• current state of the diagnostic domain

Characteristics...

• JMX MBeans
• Implement configuration dumps, state dumps, and self diagnostic tests
• Expose info about running components

They can be accessed from JMX client code, or through wsadmin.sh.

Diagnostic Provider Infrastructure

Diagnostic Service MBean	Enable use of wsadmin.sh to query Diagnostic Provider MBeans.
Diagnostic Provider utility	Administration console interface to Diagnostic Provider MBeans. Execute and view the results of configuration dumps, state dumps, and diagnostic self tests.

Diagnostic Provider ID (DPID)

For components with a registered Diagnostic Provider ID (DPID)...

1. A log entry containing a DPID indicates an exception in a specific component.

2. The administrator clicks a button on the runtime message panel to...
   • Execute a state dump
   • Execute a configuration dump
   • Be taken to the list of component self tests

3. From the self test, the administrator is warned that the component is configured in a way that could lead to poor performance or failures.

When the administrator works with a component with a Diagnostic Provider, and the DPID is not registered with the component's logger, the situation might unfold like this:

1. A log entry which doesn’t contain a DPID indicates that something has gone wrong in a component.

2. The system administrator sees the log entry through the runtime messages panel.

3. The system administrator uses the admin console to navigate through the available set of Diagnostic Providers and selects one that sounds appropriate.

4. He runs a configuration dump, a state dump, or a self diagnostic test against the Diagnostic Provider to collect information about the component.

5. From the state dump, the administrator is able to notice that the component state is not what would be expected for its workload.

6. The administrator works with the test team to determine which of the flows is causing the state of the component to diverge from what is expected (as evidenced by repeated execution of the state dump).

Related

Diagnostic Provider IDs
Diagnostic Provider configuration dumps, state dumps, and self tests
Diagnostic Provider registered attributes and registered tests
Diagnostic Provider names
The simpler interfaces provided by the Diagnostic Service MBean
Work with Diagnostic Providers
wsadmin scripting tool

+

Search Tips   |   Advanced Search