WebLogic Filtering Classloader Fails After Upgrade

(Doc ID 2269375.1)

Last updated on MAY 30, 2017

Applies to:

Oracle WebLogic Server - Version and later
Information in this document applies to any platform.


A filtering classloader is being used to separate the application build of a library from the build of the same library in WebLogic Server (WLS) itself. In the sample case, this was the OpenSAML library, but it could be any other library as well. After a WLS upgrade, the filtering classloader stopped working, and ClassNotFoundExceptions were seen. For example:

In this example, the classname used by the application is org.opensaml.ws.soap.soap11.impl.BodyBuilder (note the ws segment), so the filtering classloader is trying to load the wrong class.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms