Your J2EE application is up and running, but you've got problems. The response time is slow, the batch-processing throughput is woeful, and the users are complaining. Learn how the application of a few key design strategies can alleviate your performance problems.
by Lara D'Abreo
December 15, 2003
J2EE takes the hassle out of distributed programming, but there's a catch. Although you no longer have to contend with such low-level issues as threading, synchronization, or persistence, you also relinquish control of key architectural considerations such as load balancing and scaling. Leaving these tasks—which strongly impact performance—to the EJB container can lead to performance problems, because ultimately no third-party software can know your application as well as you do.
Performance problems manifest themselves in many ways:
JSPs take too long to load.
Search screens take minutes to show results or never return at all.
The user interface does not respond, and users click furiously but to no discernible effect.
At peak times, the server fails unexpectedly due to "out of memory" errors, locked database tables, and connection timeouts.
Your previously reliable nightly batch processes become strangely fragile and take longer to run.
It's quick, easy and you get access to all the articles on DevX.
This registration/login is to allow you to read articles on devx.com. Already a member?
To become a member of DevX.com create your Member Profile by completing the form below. Membership is free!
