Chad Scott 110000E1UB Visits (9423)
While stack traces in WebSphere logs can be invaluable for tracking down the root cause of exceptions, I frequently find that I'm seeing the same exception flooding the logs, and it has nothing to do with the problem I'm trying to track down. Some stacks may end up being useful, but they prevent me from effectively finding the problem I'm interested in. To work around this problem, you can use the following one-liner to remove all of the trace from your logs, leaving just the final error statement:
? grep -v -P "\tat" SystemOut.log > nostacks.log
Review the stackless log to find the errors you're interested in diving on, then refer back to the full log to investigate them.
Karen Gallo - IBM 100000FG9T Visits (9912)
We have a new video uploaded on our Coll
This 7-min demo overview by Tony Payne is an excerpt of a Sametime Open Mic session titled "SSL and Sametime: POODLE Training 101" (held in March 2015). It demonstrates using the Sametime System Console -- showing some default settings, key stores, and cell vs. node ideas within the concept of the WebSphere Application Server (WAS). The full playback recording of this entire Open Mic event, along with the presentation used, can be found here.
For additional Sametime support resources, visit the IBM