Legacy Knowledge Base
Published Sep. 10, 2025

Error in Logs When Accessing "OAuth 2 Administration" in Control Panel

Written By

Koustuv Dhani

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • When clicking on the "OAuth 2 Administration" option in the Control Panel, the following error is logged, and the UI displays an unresolved Velocity variable (${processor.processMax()}):
    Unable to execute method processMax {exception=com.liferay.portal.kernel.portlet.PortletContainerException: javax.servlet.ServletException: java.lang.NoClassDefFoundError: Could not initialize class com.sun.proxy.$Proxy12536, className=com.liferay.portal.layoutconfiguration.util.velocity.TemplateProcessor}
    com.liferay.portal.kernel.portlet.PortletContainerException: javax.servlet.ServletException: java.lang.NoClassDefFoundError: Could not initialize class com.sun.proxy.$Proxy12536

 Environment

  • Liferay DXP 7.4 +

Resolution

  • The issue was traced to an overridden bootdelegation configuration in the portal-ext.properties file.
  • This configuration interferes with the OSGi class loading mechanism, resulting in a NoClassDefFoundError and failure to initialize the TemplateProcessor proxy class.
  • To fix the issue, remove the following property from your portal-ext.properties file:

    ## For AppD
    module.framework.properties.org.osgi.framework.bootdelegation=\
    __redirected,\
    com.liferay.aspectj,\
    com.liferay.aspectj.*,\
    com.liferay.portal.servlet.delegate,\
    com.liferay.portal.servlet.delegate*,\
    com.sun.ccpp,\
    com.sun.ccpp.*,\
    com.sun.crypto.*,\
    com.sun.image.*,\
    com.sun.jmx.*,\
    com.sun.jna,\
    com.sun.jndi.*,\
    com.sun.mail.*,\
    com.sun.management.*,\
    com.sun.media.*,\
    com.sun.msv.*,\
    com.sun.org.*,\
    com.sun.syndication,\
    com.sun.tools.*,\
    com.sun.xml.*,\
    com.yourkit.*,\
    sun.*,\
    org.apache.poi,\
    org.apache.poi.*,\
    net.sf.jasperreports,\
    net.sf.jasperreports.*,\
    com.lowagie,\
    com.lowagie.*,\
    org.apache.commons.logging,\
    org.apache.commons.logging.*,\
    org.apache.commons.digester,\
    org.apache.commons.digester.*,\
    org.apache.commons.collections4,\
    org.apache.commons.collections4.*,\
    org.apache.commons.collections,\
    org.apache.commons.collections.*,\
    org.apache.commons.codec,\
    org.apache.commons.codec.*,\
    org.apache.commons.beanutils,\
    org.apache.commons.beanutils.*,\
    org.bouncycastle,\
    org.bouncycastle.*,\
    com.singularity.*
  • After removing the property, perform a clean server restart to ensure all changes take effect.

 

Did this article resolve your issue ?

Legacy Knowledge Base