1. Home
  2. Programming
  3. Java performance tuning

18.4 More Suggestions for Tuning EJBs

A few additional tuning suggestions for EJBs are listed here:

  • Beans.instantiate( ) incurs a filesystem check to create new bean instances in some application servers. You can use the Factory pattern with new to avoid the filesystem check.

  • Tune the message-driven beans' pool size to optimize the concurrent processing of messages.

  • Use initialization and finalization methods to cache bean-specific resources. Good initialization locations are setSessionContext( ) , ejbCreate( ), setEntityContext( ), and setMesssageDrivenContext( ); good finalization locations are ejbRemove( ) and unSetEntityContext( ). Failures to allocate or deallocate resources need to be handled.



    		Chapter 1. Introduction
    		Chapter 2. Profiling Tools
    		Chapter 3. Underlying JDK Improvements
    		Chapter 4. Object Creation
    		Chapter 5. Strings
    		Chapter 6. Exceptions, Assertions, Casts, and Variables
    		Chapter 7. Loops, Switches, and Recursion
    		Chapter 8. I/O, Logging, and Console Output
    		Chapter 9. Sorting
    		Chapter 10. Threading
    		Chapter 11. Appropriate Data Structures and Algorithms
    		Chapter 12. Distributed Computing
    		Chapter 13. When to Optimize
    		Chapter 14. Underlying Operating System and Network Improvements
    		Chapter 15. J2EE Performance Tuning
    		Chapter 16. Tuning JDBC
    		Chapter 17. Tuning Servlets and JSPs
    		Chapter 18. Tuning EJBs
    		18.1 Primary Design Guidelines
    		18.2 Performance-Optimizing Design Patterns
    		18.3 The Application Server
    		18.4 More Suggestions for Tuning EJBs
    		18.5 Case Study: The Pet Store
    		18.6 Case Study: Elite.com
    		18.7 Performance Checklist
    		Chapter 19. Further Resources