java.lang.NoSuchMethodError: after upgrading to OpenAM 11.x or 12.x deployed on an Oracle WebLogic 11g server

Last updated Jan 5, 2021

The purpose of this article is to provide assistance if you encounter a ServletException, java.lang.NoSuchMethodError: after upgrading to OpenAM 11.x or 12.x deployed on an Oracle® WebLogic 11g server.


This article has been archived and is no longer maintained by ForgeRock.


An Upgrade is available page is shown with the following error when you navigate to the OpenAM console after performing the upgrade:

Transaction id: 0 HTTP Status: 500 Status code message: Internal Server error

Clicking the Upgrade to OpenAM link does nothing.

An error similar to the following is shown in the server log:

####<Jan 14, 2014 11:36:42 AM CET> <Error> <HTTP> <svvuoam01> <OAMServer1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1389695802486> <BEA-101017> <[ServletContext@1225998403[app:openam module:openam.war path:/openam spec-version:2.5]] Root cause of ServletException. java.lang.NoSuchMethodError: org.apache.commons.lang.StringUtils.join(Ljava/util/Collection;Ljava/lang/String;)Ljava/lang/String; at org.forgerock.openam.upgrade.steps.UpgradeServiceSchemaStep.getShortReport( at org.forgerock.openam.upgrade.UpgradeServices.generateShortUpgradeReport( at com.sun.identity.config.upgrade.Upgrade.onRender( at at at at at at javax.servlet.http.HttpServlet.service( at javax.servlet.http.HttpServlet.service( at weblogic.servlet.internal.StubSecurityHelper$ at weblogic.servlet.internal.StubSecurityHelper.invokeServlet( at weblogic.servlet.internal.ServletStubImpl.execute( at weblogic.servlet.internal.TailFilter.doFilter( at weblogic.servlet.internal.FilterChainImpl.doFilter( at org.forgerock.openam.validation.ResponseValidationFilter.doFilter( at weblogic.servlet.internal.FilterChainImpl.doFilter( at com.sun.identity.setup.AMSetupFilter.doFilter( at weblogic.servlet.internal.FilterChainImpl.doFilter( at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun( at weblogic.servlet.internal.WebAppServletContext$ at at at weblogic.servlet.internal.WebAppServletContext.securedExecute( at weblogic.servlet.internal.WebAppServletContext.execute( at at at

Recent Changes

Upgraded to OpenAM 11.x or 12.x


The com.bea.core.apache.commons.lang_2.1.0.jar file that is included in the WebLogic installation also includes the class: org.apache.commons.lang.StringUtils. This version of the class file conflicts with the version supplied by OpenAM.


This issue can be resolved by changing the <prefer-web-inf-classes> element to true so that the classes in the WEB-INF directory of OpenAM are loaded in preference to the classes in the WebLogic server.

This can be achieved by creating a weblogic.xml file that contains the following text:

<?xml version="1.0" encoding="UTF-8"?> <weblogic-web-app xmlns="" xmlns:xsi="" xsi:schemaLocation=""> <context-root>/openam</context-root> <container-descriptor> <prefer-web-inf-classes>false</prefer-web-inf-classes> <prefer-application-packages> <package-name>org.apache.commons.lang.*</package-name> </prefer-application-packages> </container-descriptor> </weblogic-web-app>

And then including this file in the openam.war/WEB-INF directory before you deploy the openam.war file


You must restart the WebLogic application container in which OpenAM runs to apply these configuration changes. 

See Also

java.lang.LinkageError: after upgrading to OpenAM 11.x or 12.x deployed on an Oracle® WebLogic 12c server

OpenAM Installation Guide › Preparing For Installation › Preparing Oracle WebLogic

Related Training


Related Issue Tracker IDs

OPENAM-3529 (Class loading error in Weblogic deploy)

Copyright and Trademarks Copyright © 2021 ForgeRock, all rights reserved.