BeanSpy

Summary

The deep availability health monitor adds additional monitoring capabilities in addition to basic availability monitoring. The deep monitor verifies that the application server accepts and responds to HTTP requests. This is done by verifying that the agent can make a call to BeanSpy's Stats page.

Causes

An unhealthy state indicates that the deep monitor failed to establish a connection to BeanSpy. Possible causes for this behavior include the following:

• BeanSpy is not deployed.

• BeanSpy is not started.

• A firewall is blocking the port.

• The credentials supplied to access BeanSpy are invalid.

Resolutions

Verify that BeanSpy has been deployed and is started by using the application server's administration console. Next, verify that there is no firewall blocking the port and the appropriate user credentials have been supplied to the Run As account.

To manually verify the connection to BeanSpy, open a browser and connect to the Stats page:

• http(s)://<hostname>:<port>/BeanSpy/Stats