IdP fails to start after upgrading to Jetty12

[Grüter, Philip]

Hi all,

I'm currently working on the upgrade from Shib v4 and Jetty9 to Shib v5 and Jetty12.
At this point the setup is working with Jetty11 and Shibv5:
jdk_version: 17.0.15
idp_version: 5.1.4
jetty version: 11.0.25

After I've upgraded to Jetty12, I know get these errors in the jetty.log:

2025-05-22 17:27:56,240 - WARN [org.eclipse.jetty.ee9.annotations.AnnotationParser:665] - org.apache.taglibs.standard.lang.jstl.BinaryOperator scanned from multiple locations: jar:file:///opt/jetty-home-12.0.21/lib/ee9-glassfish-jstl/org.glassfish.web.jakarta.servlet.jsp.jstl-2.0.0.jar!/org/apache/taglibs/standard/lang/jstl/BinaryOperator.class, jar:file:///opt/jetty-base-12/tmp/jetty-127_0_0_1-80-idp_war-_idp-any-13251502949287076639/webinf/WEB-INF/lib/jakarta.servlet.jsp.jstl-3.0.1.jar!/org/apache/taglibs/standard/lang/jstl/BinaryOperator.class
2025-05-22 17:27:56,240 - WARN [org.eclipse.jetty.ee9.annotations.AnnotationParser:665] - org.apache.taglibs.standard.lang.jstl.ModulusOperator scanned from multiple locations: jar:file:///opt/jetty-home-12.0.21/lib/ee9-glassfish-jstl/org.glassfish.web.jakarta.servlet.jsp.jstl-2.0.0.jar!/org/apache/taglibs/standard/lang/jstl/ModulusOperator.class, jar:file:///opt/jetty-base-12/tmp/jetty-127_0_0_1-80-idp_war-_idp-any-13251502949287076639/webinf/WEB-INF/lib/jakarta.servlet.jsp.jstl-3.0.1.jar!/org/apache/taglibs/standard/lang/jstl/ModulusOperator.class
2025-05-22 17:27:56,687 - INFO [org.eclipse.jetty.ee9.nested.ContextHandler.idp:2040] - No Spring WebApplicationInitializer types detected on classpath
2025-05-22 17:27:56,708 - INFO [org.eclipse.jetty.ee9.nested.ContextHandler.idp:2040] - Initializing Spring root WebApplicationContext
2025-05-22 17:28:01,592 - WARN [org.eclipse.jetty.util.DeprecationWarning:38] - Using @Deprecated Class net.shibboleth.idp.log.SLF4JMDCServletFilter
2025-05-22 17:28:01,610 - WARN [org.eclipse.jetty.ee9.servlet.BaseHolder:103] - Unable to load class org.eclipse.jetty.servlet.DefaultServlet
java.lang.ClassNotFoundException: org.eclipse.jetty.servlet.DefaultServlet
...
2025-05-22 17:28:01,626 - INFO [org.eclipse.jetty.ee9.nested.ContextHandler.idp:2040] - Initializing Spring DispatcherServlet 'idp'
2025-05-22 17:28:02,096 - WARN [org.eclipse.jetty.ee9.webapp.WebAppContext:538] - Failed startup of context oeje9w.WebAppContext at 2ed3b1f5{Shibboleth Identity Provider,/idp,[file:///opt/jetty-base-12/tmp/jetty-127_0_0_1-80-idp_war-_idp-any-13251502949287076639/webinf/, jar:file:///opt/shibboleth-idp/war/idp.war!/],false}{/opt/shibboleth-idp/war/idp.war}
jakarta.servlet.UnavailableException: Class loading error for holder default==org.eclipse.jetty.servlet.DefaultServlet at 5c13d641{jsp=null,order=0,inst=false,async=false,src=DESCRIPTOR:file:///opt/jetty-home-12.0.21/etc/webdefault-ee9.xml,STARTING}
    at org.eclipse.jetty.ee9.servlet.BaseHolder.doStart(BaseHolder.java:104)

I've checked that idp.properties exists and I set the idp.home directory in the jetty start.ini. Permissions shouldn't matter too much, because I start the jetty server as root, at least for now.
After starting, the Shibboleth IdP only throws 503 errors:
# bin/status.sh
(http://localhost/idp/status) Server returned HTTP response code: 503 for URL: http://localhost/idp/status

The output of the start.jar includes these lines:
2025-05-22 17:56:40.819 [ WARN] : DEPRECATED: Java class 'net.shibboleth.ext.spring.context.DelimiterAwareApplicationContext', (web.xml): This will be removed in the next major version of this software; replacement is auto-registration via updated web.xml
Loading class `com.mysql.jdbc.Driver'. This is deprecated. The new driver class is `com.mysql.cj.jdbc.Driver'. The driver is automatically registered via the SPI and manual loading of the driver class is generally unnecessary.
2025-05-22 17:56:41.886 [ WARN] : com.zaxxer.hikari.util.DriverDataSource: Registered driver with driverClassName=com.mysql.jdbc.Driver was not found, trying direct instantiation.

I don't really get how these warnings  occur. Our MySQL Config uses HikariCP as the class, which should be loaded correctly. The same warnings also occur on jetty11 and that does start correctly.

What can I do to debug this further?

Greetings
Philip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20250522/6cccdfe9/attachment.htm>