Timed Operation is a newly added feature to V8.5.5 which would help WebSphere Application Server administrators to see if any events in their application servers are operating either slower than expected. Currently Timed Operation have been added to track the duration for the JDBC operations which are been executed in the application server. In future this could be enhanced by adding the track for EJB, Servlets and many more operations. Timed operation feature operates by logging messages along with generating timely reports.
In order to enable timed operations, we need to add timedOperations-1.0 feature to server.xml.
Figure 1 : To enable timed operation.
When we enable timed operations it will log a warning message into conosle.log and messages.log where messages.log contains more detailed information by including the timestamps, thread ID and component names which will not be present in console.log file.
Figure 2: snapshot of messages.log when timed operations feature is enabled.
A log message have been created by timed operation in messages.log, where it's logging a warning message for a SQL query in which the execution time has been grown from 0.169 ms to 0.091 ms. This feature is driven by setting the expected time for operation ( eg SQL query) in the configuration file which will be used by Timed operations to analyze whether the operations is faster or slower than expected.
Timed operation feature reports
In addition to logging warning messages for JDBC operations, timed operations feature has the ability to create report in messages.log file, listing the applications that took the longest time for execution, the frequency of the report is once per day (24 hours).
Configuring the generation of timed operation report
We can disable timed operations report feature by explicitly setting enableReport to false, by default this property is enabled providing logging details for 10 longest timed operation, grouped by type, and sorted within each group by expected duration. We can even change the frequency of report generation by setting the reportFrequency attribute.
Figure 3: Setting the time operations property in server.xml
[ Figure 3: This configuration will lead to warning messaged to be logged when number of timed operations exceeds 15000. ]
You can also use the server dump command to get a full report of all timed operations in the messages.log file, grouped by type, and sorted within each group by expected duration.
Timed operations feature eases the life of Webshpere Application Server administrators by reporting when operations are not functioning as per their expectations.