Ever wondered what’s happening inside the application server? Ever had a fight with your developers about performance of a J2EE (tomcat/jboss/oc4j/iAS/jrun/…)? Or had a fight with developers who blame the database while you think (or know) it is not causing the problems?
There is a solution for that: Glassbox.
Glassbox is an application which can be deployed in a J2EE (java) application server, which uses AOP (aspect oriented programming) to monitor behavior of the J2EE server, and outputs operations ordered by average response time (total responsetime / number of executions). Besides that (which on itself is a godsend for application server administrators), it highlights operations which exceed the threshold (default 1 second) and it highlights operations which throw an error.
The operation can be selected (conveniently using a browser), so specifications of this operation can be investigated. like:
– stack trace of the code executed
– input URL
– number of times it ran within the threshold, exceeded the threshold and failed
This is how the glassbox application looks like:
Even more interesting, it can diagnose a slow database operation (as seen in the screen above), and display the SQL which is responsible:
The installation of glassbox is very straightforward for jboss, the procedure for installing it in the OC4J in iAS version 10.1.3 requires some tweaking of xml files. Contact me if you are interested in the installation procedure.
You can find glassbox, including the free download (and forums for support) here