Skip to main content
Mitratech Success Center

Client Support Center

Need help? Click a product group below to select your application and get access to knowledge articles, webinars, training content, and release notes or to contact our support team.

Authorized users - log in to create a ticket, view tickets status and check your success plan details.


IBM WebSphere - Setting Classloader Settings (parent last)

This is step by step guide which shows how to work with IBM WebSphere Classloader Settings.


Issue:  NoClassDefFoundError exception occurring during any action where class indeed exists. 

Cause: Class is present but class loader does not "see" the class.  Setting Classloader to "parent_last" configuration resolves this issue in most cases.


This on-premise solution requires a team member with access to the IBM console, preferably with administration experience.

Note, Solution is for latest supported WebSphere (8.5.5) as of writing of this article.  Consult WebSphere documentation for guidance if the below steps do not take you to the appropriate sections

First Step

Set Classloader Policy at Server level

  1. Log into IBM WebSphere console
  2. Click Servers > Server Types > WebSphere application servers > server_name to access an application server settings page.
  3. Select Classloader Policy: Single
  4. Select Class loading mode: Classes loaded with local class loader first (parent last)
  5. Save changes to master configurationTeamConnect-Websphere-classloader001.png

Second Step

Set Classloader Policy at Manage Modules level

  1. Log into IBM WebSphere console (if not logged in already)
  2. Click Applications > Application Types > WebSphere applications > application_name
  3. Click Manage Modules link
  4. Select module_nameTeamConnect-Websphere-classloader002.png
  5. Select Class Loader Order "Classes loaded with class loader first (parent last)TeamConnect-Websphere-classloader003.png
  6. Click Apply
  7. Save changes to master configuration