Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

Receiving ClassNotFoundException:JspTagHandlerPool in traces

Written By

Anushka Tiwari

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 starting the server, receiving the ClassNotFoundException:JspTagHandlerPool in the gowroot traces:

    Steps to reproduce:
    1. Start the server by giving this command: ./catalina.sh glowroot run.
    2. Now navigate to this URL: localhost:8080/o/glowroot
    3. In the slow traces graph, observe the slow traces.
    4. Clicked on that trace > Trace entries. You will be able to find the following errors: 
    java.lang.ClassNotFoundException: com.liferay.portal.osgi.web.servlet.jsp.compiler.internal.JspTagHandlerPool
    atorg.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1349)
    atorg.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1158)
    atcom.liferay.shielded.container.internal.ShieldedContainerClassLoader.findClass(ShieldedContainerClassLoader.java:70)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:592)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:525)

Environment

  • Liferay 2025.Q1.2

Resolution

  • The observed behaviour is a known bug addressed by the LPD-55062 

Additional Information

  • If a hotfix is required, please create a support ticket requesting the hotfix by attaching the patch details.
  • Applying a Hotfix will guide you to install the Hotfix in your environment.
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?