Closed coffee-squirrel closed 6 months ago
Same. Our customers are experience similar errors. Experiencing the same even with JBP_CONFIG_SPRING_AUTO_RECONFIGURATION='{enabled: false}'
set
They're currently checking for conflicting dependencies in their poms. Apps push successfully when using v4.63.1
v4.64.0
has upgraded the version of the Client Certificate Mapper library to 2.0.0 with the aim of supporting Boot 3.x and the change to jakarta.*
packages as well as maintaining support for 2.x and the javax.*
naming.
It's possible a bug has been been introduced - can you please share more details about the affected apps while we investigate? e.g.
pom.xml
if possible may be helpful also Looks spring-boot-starter-parent related. Apps with 1.5.2.RELEASE
or 1.5.9.RELEASE
have encountered issues. I know, soooo old. Apps with 2.0.x appear to work ok.
Java 8 only so far
Yep, looks like our apps that were impacted were on 1.5.12.RELEASE
or 1.5.22.RELEASE
. Other apps on 2.x
deployed successfully.
Looks like a new version of the client-certificate-mapper has been cut which should re-enable customers to use 1.5.x again.
https://github.com/cloudfoundry/java-buildpack-client-certificate-mapper/commits/v2.0.1/
Are there any plans for a teeny/minor java-buildpack release to incorporate this? It'll get our customers over this hump then early in the new year, they can complete the fun job of updating their dependencies
@coffee-squirrel @thelangley We plan to release a new version this week, however we strongly recommend users update to at least the latest supported Spring Boot 2.x, as commercial support for 1.5 ended in 2020 and the Java Buildpack cannot guarantee compatibility with such outdated configurations.
Totally behind that. We're pushing them to do the right thing and update to a more modern version, maybe even one from this decade.
Hopefully this'll focus minds on why you should care about your dependencies :)
Yep, completely understand and appreciate you all putting in any time on this. We'll use this to keep trying to get teams to update their stuff.
After the new version hits PivNet I'll get some apps redeployed and post back with results.
We've used v4.65.0
to successfully deploy the apps that were having issues under v4.64.0
. Thanks again!
After moving from
v4.63.1
tov4.64.0
we found multiple (TBD if all) app deployments started failing with the stack traces shown below.Common things found so far:
JBP_CONFIG_METRIC_WRITER='{enabled: false}'
v4.0.14
(cflinuxfs4
)We've reverted to
v4.63.1
and verified subsequent deployments were successful and the instances started cleanly.I'll try to add more info next week.
2023-12-16 edit: One app had the Auto Reconfiguration-related JARs added due to use of Spring Cloud Connectors (we've been on teams about eliminating this since last year). Disabling that (
JBP_CONFIG_SPRING_AUTO_RECONFIGURATION='{enabled: false}'
) appears to have cleared up the issue under4.64.0
for this app, but the owning team probably has some work to do. I believe another app that was impacted doesn't use Auto Reconfiguration, Spring Cloud Connectors, or java-cfenv, though, so I'll look into that next.