SAP Knowledge Base Article - Preview

3794024 - Runtime JAR Conflicts After JDK 21 / Tomcat 10 Upgrade

Symptom

When upgrading SAP Commerce to JDK 21 (which bundles Tomcat 10), certain JAR conflicts in your custom extensions can cause HTTP 500 errors at runtime even though:

- build completes successfully with no errors
- The server starts without error
- The error only appears when a specific JSP page is accessed for the first time
- The issue may not reproduce in your stage environment even with the same Docker image

Sample exception may look like:

java.lang.NoClassDefFoundError: javax/servlet/jsp/tagext/TagLibraryValidator
  Caused by: java.lang.ClassNotFoundException:
    javax.servlet.jsp.tagext.TagLibraryValidator
      at org.apache.catalina.loader.WebappClassLoaderBase.loadClass

We recommend performing the manual checks below before going live with the upgrade.


Read more...

Environment

SAP Commerce Cloud

Product

SAP Commerce Cloud 2211 ; SAP Commerce Cloud 2211 for JDK21

Keywords

Framework update, javax, jarkata , KBA , CEC-SCC-PLA-PL , Platform , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.