Back to newsletter 075 contents

This month we announce the opening of our sister site, fasterj.com, and continue with the Java 6 theme we started last month. Fasterj opens in style with a fabulous article on how to hotpatch a Java 6 application. The techniques needed to hotpatch, also allow you to investigate a running application in ways that were previously much more difficult to do - this is a must read article for anyone interested in advanced Java capabilities.

A note from this newsletter's sponsor

On top of that excellent hotpatching article, here at JavaPerformanceTuning.com we do another of our focus newsletters, this time on the Java 6 troubleshooting guide. Each recent major release of Java has seen a troubleshooting guide supplied by Sun - and the Java 6 troubleshooting guide is far and away the best one of these we've seen. In fact it is so comprehensive that it's actually more useful for troubleshooting even if you are using a Java version prior to Java 6 - yes, we think the Java 6 guide is more useful for troubleshooting Java 5 applications than the Java 5 guide is!

In addition, although Javva the Hutt is on holiday, he's asked a colleague to stand in for him, and Javva's colleague (who prefers to remain anonymous under the pen name Hutt5) relates his Java 5 upgrade woes - ones of his own making, but probably quite useful reading for anyone else making the upgrade to Java 5.

A note from this newsletter's sponsor

Now read on for the links and extracted tips to those fascinating articles, as well as our newly listed news and tools. And, of course we have extracted all the tips from that troubleshooting guide and the fasterj hotpatching as well as the Hutt5 article.

News

Java performance tuning related news.

• Java more efficient than Ajax for advanced web apps
• Java more efficient than Ajax for advanced web apps (discussion)
• Yourkit Java Profiler 6.0 Released
• How Early Should You Test for Performance?

Tools

Java performance tuning related tools.

• Real-Time Class Analysis Tool for Java: scans the Java bytecode of the user's application as well as the classes that it uses, then generates a Java source file containing a static method that can be called by the application to preload and, optionally, pre-compile all these classes.
• JBoss Profiler: log based profiler using JVMPI and JVMTI.
• AppSight application monitoring and problem resolution technology

A note from this newsletter's sponsor

Articles

• Hotpatching A Java 6 Application (Jack Shirazi/Fasterj.com)
• Troubleshooting Guide for Java SE 6 (Sun/Sun)
• Java 5 Upgrade Woes (Hutt5/JavaPerformanceTuning.com)

Jack Shirazi

Back to newsletter 075 contents