EAServer uses custom Java class loaders to allow refreshing the Web application classes and Java components, and to load classes from directories and JAR files that are not specified in the CLASSPATH environment variable. During the development cycle, this feature allows you to add or modify classes without restarting the server. However, duplicate in the custom class list for different components can waste memory by loading duplicate class instances. Chapter 30, “Configuring Custom Java Class Lists,” in the EAServer Programmer’s Guide describes how to configure common class lists for components and Web applications.
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. For this reason, it is best to
restart your production server after deploying a large number of
new implementation classes, ensuring that the memory required to
load new classes is not reallocated.
