WXS 7.1.1 brings xscmd and a log analyzer tool?
If you’re up-to-date with the happenings of the WebSphere eXtreme Scale (WXS) world you might already know about the changes that brought about a new log analysis tool and a replacement for the sample xsadmin tooling..
Do you know what makes WebSphere Application Server v8 stand above others when it comes to serviceability and problem determination?
Heard of HPEL (High Performance Extensible Logging) ? If not, check out this link on IBM Education Assistant! You can read a ton more information about HPEL from this link to the WebSphere v8 InfoCenter as well. In short HPEL can be described as :
HPEL provides a convenient mechanism for storing and accessing log, trace, System.err, and System.out information produced by the application server or your applications. It is an alternative to the basic log and trace facility, which provided the JVM logs, diagnostic trace, and service log files commonly named SystemOut.log/SystemErr.log, trace.log, and activity.log
Exposing your WebSphere logs as ATOM feeds
Have you ever thought, “I’d like to access my WebSphere Application Server logs as an RSS/ATOM feed”? Well, good! Because I’m going to show you how. The end result is going to be a web application that can be deployed onto an WebSphere Application Server v6.x server or higher. This tutorial is written for the experienced Java web developer. So, without delay, lets dive right in.
Verbose GC logging in the IBM SDK - a better wayDid you know that the IBM JDK allows for the logging of verbose garbage collection (verbose GC) output to a file other than native_stderr.log? Ever wished that you could use a circular logging approach to your verbose GC output? Well, you can!
Consider this excerpt from the IBM Java 1.5 Diagnostic Guide:
Several times in my tenure as a member of the WebSphere Application Server SWAT team have I encountered customer applications that are logging copious amounts of seemingly debug level output to the application server logs (i.e. SystemOut.log). And all too frequently, I see that they do this by using simple Java sysout commands like : System.out.println(). Besides being maddening, it’s plainly an anti-practice for multiple reasons. If you’re guilty of logging with System.out.println() in your enterprise Java applications, let me give a you few reasons to discontinue that practice.