Appendix B.2 Class loader configuration for local call optimization

When you use the local call optimization functionality, the class loader configuration differs from the default class loader. The local call optimization functionality enables the invocation of the Enterprise Beans of other applications at a high speed.

To use the local call optimization functionality, specify the following settings in the user-defined file for the J2EE servers (Cosminexus-installation-directory\CC\server\usrconf\ejb\server-name\usrconf.properties):

ejbserver.rmi.localinvocation.scope=all

The class loader configuration for local call optimization is as follows:

Figure B-2 Class loader configuration for local call optimization

[Figure]

The contents of the class loaders are as follows:

For the notes on the destruction of a class loader, see Appendix B.1 Default class loader configuration.

Hint
Loading a resource adapter
A resource adapter deployed as a J2EE resource adapter is loaded using the connector class loader. A resource adapter that is included and used in a J2EE application is loaded using the application class loader.

Note
Note the following points when you set ejbserver.rmi.localinvocation.scope=all in the property:
  • The EJB-JARs and library JARs of the J2EE application are loaded using the same class loader, so the classes with the same name are shared between the J2EE applications. If the classes with the same name, but different contents exist, only the class loaded first is enabled as per the Java specifications. Note that the classes in a WAR file are loaded using the class loaders existing for the WAR files, so these classes are not shared.
  • To replace the EJB-JARs and library JARs of a J2EE application, stop the J2EE application and then restart the J2EE server. The settings will be enabled after restart.