Enhanced configuration class fails to call package-visible superclass constructor on WebSphere #34950
Labels
in: core
Issues in core modules (aop, beans, core, context, expression)
status: backported
An issue that has been backported to maintenance branches
type: regression
A bug that is also a regression
Milestone
Uh oh!
There was an error while loading. Please reload this page.
Encountering exception during application context initialization in IBM WebSphere Liberty executing on IBM J9 VM after upgrade of Spring Boot and corresponding supported Spring Framework version.
Initially we encountered an exception when trying to upgrade from Spring Boot 3.3.5 to 3.3.11 and associated Spring Framework version from 6.1.14 to 6.1.19.
Last version where we are not able to reproduce is Spring Boot 3.3.8 and Spring Framework 6.1.16.
Minimal version where we are able to reproduce is Spring Boot 3.3.9 and Spring Framework 6.1.17.
Upgrading to Spring Framework 6.1.19 has not fixed the issue. Neither has 6.1.20.
Reproduction only happens on WebSphere Liberty Profile
(Liberty Dev Use 24.0.0.9/wlp-1.0.93.cl241020240827-1743)
on IBM J9 VM JavaIBM Semeru Runtime Certified Edition for z/OS (build 17.0.12+7) IBM J9 VM (build z/OS-Release-17.0.12.1-b01, JRE 17 z/OS s390x-64-Bit Compressed References 20240904_69 (JIT enabled, AOT enabled)
. Does not happen with otherwise identical dependencies on Tomcat 10.1.31, also using the same IBM J9 VM.This looks like a variant or continuation of #34684 (no affiliation with the original submitter).
(company-specific path/package/application names redacted and replaced with
redacted
placeholder, can provide additional information if relevant to the issue)So far unable to provide a minimal reproduction scenario as I can't identify what is the approximate cause of the issue, and the application is nontrivial. The main application servlet uses Spring Framework, but not Spring Boot. Spring Boot is only used as a dependency for Swagger UI, where we override 3.3.X patch version to avoid shipping versions with known CVEs (see above for exact tested versions), corresponding snippet from maven dependency tree:
Redacted outline of the configuration classes (can provide additional details privately if relevant to the issue).
The text was updated successfully, but these errors were encountered: