Java/CORBA and EJB components benefit from most of the settings described in “Common component performance issues”.
You can improve the performance of Java and EJB components by configuring common class loaders for the application’s components (including Web components). EAServer uses custom class loaders to allow you to refresh implementation classes without restarting the server. Loading multiple copies of the same class uses memory unnecessarily. You can eliminate redundant class loading by configuring an application-level or server-level class list, as described in Chapter 30, “Configuring Custom Java Class Lists,” in the EAServer Programmer’s Guide.
Minimize Refresh in production servers
Refreshing components loads additional copies of all implementation
classes. EAServer leaves the previous implementation in memory for
use by existing client sessions. In effect, refresh introduces a
controlled memory leak. For this reason, it is best to restart your
production server after deploying a large number of new implementation
classes.
Copyright © 2003. Sybase Inc. All rights reserved. |
![]() |