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. To avoid this issue, configure a common class loader for use by the Web application and the components that it calls. To do this, configure 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. |
|
|
