-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Possible conflicts with azure-spring-boot-bom and spring-boot-starter-actuator #25553
Comments
@backwind1233 could u take a look of this? |
Hi, @TcarrollJH you can follow the link: #24988 for our updates |
Hello @backwind1233 thank you for looking into it. I have to say it must have been something different or maybe there was an update? I have zero issues today when I booted it up and all the security functions as well in 2.5.6. I didn't change the version or anything really. Sorry, I wish I had more information on what is different now. |
@TcarrollJH |
Here is the pom. Still no issues anymore even on 2.5.6.
` |
Thank you @TcarrollJH, I have just tested in my machine, no issues on my side, if you find any issues again, please provide the error infos and reopen the issue. |
-Spring boot 2.5.6
-Maven
error: java.lang.NoSuchFieldError: ERROR_ATTRIBUTE
ANY request made to the API works but throws a 500 as a response and kicks up the error on spring.
When removing actuator from the application pom.xml there are no errors at all. Everything works perfectly
The addition of actuator, despite if it's secured or not by spring security, introduces the error.
I've removed all bits of security configuration from the application and just having the two dependencies in the pom, not being used, will still replicate the error.
I've cleaned the project, tried to manually override the dependencies versions for both actuator and spring security but all to no avail.
Dependencies:
The text was updated successfully, but these errors were encountered: