A class loader policy in WebSphere Application Server controls how many application class loaders are created for the applications on a server. The product recognises two values, Multiple and Single, so options A and C are correct. With the Multiple policy, each application receives its own class loader, which isolates applications from one another and allows each to carry its own versions of libraries without conflict. With the Single policy, one class loader is shared by all applications on that server, so classes are visible across applications. That reduces memory consumption in some cases but removes the isolation, and a library version required by one application becomes visible to all of them.
The remaining options are not defined by the product. Sequential, Compact, and Ordered do not describe a class loader policy. The term "ordered" might be confused with the class loading order setting, which is a separate attribute choosing between parent first and parent last delegation; it is not a policy value for application class loaders.
Administrators set the policy on the application server's configuration, and it works together with the class loading mode, which determines the search order. Most deployments retain Multiple because isolation prevents version collisions between applications that share a server.
[Reference: Class loaders; Class loader policy (Single and Multiple); Class loading mode (parent first, parent last).]
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit