WHY YOU SHOULD READ THIS

    If you are delving into or entrenched in J2EE applications you will need to read this white paper because it will save you hundreds of hours spent in support of J2EE application performance management. The white paper highlights some of the key J2EE performance management considerations as you develop and deploy applications. Specific tips and recommendations are provided to help reduce risks and ensure overall project success.

    J2SE PERFORMANCE MONITORING AND TUNING

    Most J2EE projects will have one or more developers with some J2SE (Java 2 standard edition) performance tuning experience, and it is expected that they will be able to carry this experience over to J2EE (Java 2 enterprise edition) projects. Unfortunately this is not necessarily the case since J2EE performance management is significantly different from J2SE performance management. Being aware of the differences between J2SE and J2EE performance management will enable your J2EE performance management to be more productive and run more smoothly.

    J2SE profilers

     Let’s take a look at what J2SE performance tuning involves. The typical J2SE application runs in one JVM (Java virtual machine) and can be tuned by running the application in the JVM with a profiler attached to find the performance problems (also known as bottlenecks or hot spots). Profilers are applications that monitor the JVM while the application is running. Profilers typically record: Which methods are running