• Share
  • ?
  • Profiles ▼
  • Communities ▼
  • Apps ▼

Blogs

  • My Blogs
  • Public Blogs
  • My Updates

Kevin Grigorenko's IBM WebSphere SWAT Blog

  • Log in to participate

About this blog

  • Facebook
  • Twitter
  • Google
  • LinkedIn
  • RSS

Archive

  • December 2016
  • September 2016
  • June 2016
  • February 2016
  • January 2016
  • December 2015
  • October 2015
  • September 2015
  • July 2015
  • April 2015
  • February 2015
  • December 2014
  • October 2014
  • August 2014
  • July 2014
  • June 2014
  • May 2014
  • April 2014
  • January 2014
  • December 2013
  • November 2013
  • August 2013
  • July 2013
  • May 2013
  • April 2013
  • March 2013
  • February 2013
  • January 2013
  • November 2012
  • October 2012
  • September 2012
  • August 2012
  • July 2012
  • June 2012
  • May 2012
  • April 2012
  • March 2012
  • February 2012
  • January 2012
  • December 2011
  • November 2011
  • October 2011
  • September 2011
  • August 2011
  • July 2011

Tags

Posts by date
  • Sort by:
  • Date
  • Title
  • Likes
  • Comments ▼
  • Views

New: Customizable Access Log Format in WAS 8.0.0.2

kgibm 0600027VAP | | Comments (2) | Visits (11918)

Tweet
In a previous post , I covered some of the ways to log per-HTTP response time information in WAS. Good news -- a new and more standard approach has been added in WAS 8.0.0.2 through PM46717 . WAS has had NCSA logging -- which is most commonly know through the LogFormat that httpd/IHS uses by default in its access/error logs -- but the format in WAS was not customizable, and did not have response times. WAS 8.0.0.2 introduces a customizable format which includes %D: "The elapsed time of the request. Millisecond accuracy, microsecond... [More]

New: System dump produced on first OOM in WAS 8.0.0.2

kgibm 0600027VAP | | Visits (1903)

Tweet
Starting in WAS 8.0.0.2 running on IBM JVMs, the default artifacts produced on an OutOfMemoryError have changed. In addition to the old defaults (first four OOMs create a PHD, javacore, and snapdump), a system dump will be produced on the first OOM: http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.base.doc/info/aes/ae/ctrb_java626.html . Some customers have become used to system dumps meaning crashes, so don't be worried. System dumps are a richer and alternative artifact to understand OOMs using the Memory Analyzer... [More]

Native (C/C++) Eye-catcher

kgibm 0600027VAP | | Visits (4464)

Tweet
Someone asked for a quick reference on native eye catchers, and I had a hard time finding a comprehensive reference through the search engines, so here's a quick rundown. Eye-catchers are generally used to aid in tracking down native memory leaks or native OutOfMemoryErrors. After you've checked all the obvious culprits, at some point you may have to manually page through a hexdump. An eye-catcher, as its name suggests, is some sequence of bytes that has a low probability of randomly appearing in memory. If you see one of your eye-catchers,... [More]

JVM Late Attach Capabilities

kgibm 0600027VAP | | Visits (2333)

Tweet
Recent versions of both the IBM and Oracle JVMs support late attach functionality. This allows you to "inject" either a native JVMTI or Java agent into a running JVM which can run arbitrary code without having to restart the JVM. For IBM Java, the versions are Java 5 >= SR10 (disabled by default) [WAS >= 6.1.0.27], Java 6 >= SR6 (enabled by default on non-z/OS platforms) [WAS >= 7.0.0.7], Java 6 R26 [WAS 8], and Java 7. If you're in a really sticky situation where you can't restart a server, but you need to do something to... [More]

Linux gcore Timestamp

kgibm 0600027VAP | | Visits (4010)

Tweet
Update (May 30, 2013) : Note that it is preferable to use IBM Java's capabilities to produce system dumps instead of gcore. See why . The Linux gcore command (also part of gdb) is a very useful command to create a coredump of a running process without killing the process. This is particularly useful starting with WAS 6.1.0.33 and 7.0.0.15 as a core dump can be read directly by the Memory Analyzer Tool, without running jextract, so that core dumps become as easy to use as PHD heapdumps, while providing much more information . usage:... [More]

Reparsing heap dump file due to out of date index file

kgibm 0600027VAP | | Visits (2033)

Tweet
The Memory Analyzer Tool (MAT) creates index files after parsing a dump the first time so that reloading a dump is much faster. These index files are saved to the same directory as the dump file. In fact, you can load a dump on a beefier machine and then copy over the index files to your slower machine and get the benefits of loading a dump faster. One issue I recently hit was that every time I would reload a dump, I would get the message "Reparsing heap dump file due to out of date index file," and the dump would be completely reloaded.... [More]
  • Show:
  • 10
  • 20
  • 30
  • Previous
  • Next
1