Weblogic Server Availability Monitoring Best Examples



Weblogic Server Availability Monitoring Best Examples

Availability Monitoring:

The following adverse conditions with the Weblogic environment can cause the Weblogic Servers to become unavailable. 
  1. Weblogic Server Instance Unavailable
  2. Weblogic Server Internal Errors
  3. Critical File Systems Full
  4. Capacity Limits Reached
  5. Weblogic Session-Replication Issues

 Weblogic Server Instance Unavailable:

Weblogic Server Instances run as processes on the system. Occasionally they may terminate abnormally causing Weblogic Server to become unavailable. Partial outages also exist when Weblogic Server is functioning normally for the currently connected users but will not allow any new connections. Therefore, Weblogic Server must be monitored from both the process and connection perspectives.
 If an instance is, down and is 24/ 7, alarm the Weblogic Administrators through email or SMS.

Weblogic Server Internal Errors:

Weblogic Server writes internal errors to the Standard Output Log file for the Instance. Although many of the errors are not critical, all errors should be addressed in a timely manner. Errors containing critical error codes must be detected and addressed immediately.

Critical File Systems Full:

One of the most critical Weblogic Server availability issues occurs when the Weblogic Server is unable to process transactions because the file system allocated for log space is full. Log space is used by transactions to store Weblogic Server updates and it is sized by the Weblogic Administrator according to the number and size of the transactions for that Serevr. Weblogic Server writes error and dump information to file systems designated by the Weblogic Administrator. The error and dump files systems are important because Weblogic Server will not be able to log critical internal errors when error and dump file systems become full. Internal errors usually lead to unavailability of the Weblogic Server.

Weblogic Session-Replication Issues:

Weblogic Server has the capability to replicate all Sessions from one Instance to another. Although Weblogic Server functions correctly when it is unable to replicate data, applications using the replicated data may become unavailable. To a user, application unavailability and database unavailability are the same.