Class loader settings

Configure a class loader for applications that reside on an application server.

From the admin console, click...

        Servers > Server Types > WebSphere application servers > server > Java and Process Management > Class loader > class_loader_ID.

Class loader ID

Specifies a string that is unique to the server identifying the class-loader instance. The product assigns the identifier.

Information	Value
Data type	String

Class loader order

Specifies whether the class loader searches in the parent class loader or in the application class loader first to load a class. The standard for development kit class loaders and WebSphere Application Server class loaders is Classes loaded with parent class loader first. By specifying Classes loaded with local class loader first (parent last), the application can override classes contained in the parent class loader, but this action can potentially result in ClassCastException or LinkageErrors if we have mixed use of overridden classes and non-overridden classes.

The options are Classes loaded with parent class loader first and Classes loaded with local class loader first (parent last). The default is to search in the parent class loader before searching in the application class loader to load a class.

For the application to use the default configuration of Jakarta Commons Logging in this product, set this application class loader order to Classes loaded with parent class loader first. For the application to override the default configuration of Jakarta Commons Logging, the application must provide the configuration in a form supported by Jakarta Commons Logging and this class loader order must be set to Classes loaded with local class loader first (parent last). Also, to override the default configuration, set the class loader order for each web module in the application so that the correct logger factory loads.

Information	Value
Data type	String
Default	Parent first

Class loading

Troubleshoot class loaders

Library reference collection