So you've been told to diagnose a performance problem in a WebLogic J2EE
application. Because Java systems are so complex, this can be a bit like
diagnosing a rare illness.
To pinpoint the problem accurately you need to have a thorough understanding
of the symptoms, be prepared to do a fair amount of investigative work, and
then you must determine the proper remedy. This article offers a discussion
of some of the most common types of J2EE application performance issues and
their causes, followed by suggested guidelines for properly diagnosing and
eliminating them.
The Symptoms
What are the symptoms of a WebLogic application performance problem? The
symptoms you see guide your search through all possible illnesses. Get a
notebook and start asking people for data. Try to separate speculation and
theory about the root cause of the problem from hard evidence about the ... (more)