LatencyUtils | Utilities for latency measurement and reporting | Monitoring library

Acording to this answer: https://stackoverflow.com/a/51236918/16651073 tomcat falls back to default logging if it can resolve the location

Can you try to save the properties without the spaces.

Like this: logging.file.name=application.logs

You have annotated your application with @EnableWebFlux. This indicates that you want to take complete control of WebFlux's configuration. This causes Spring Boot's auto-configuration of WebFlux to back off. Among other things, this means that it won't configure WebFlux to use the context's ObjectMapper.

You should either remove @EnableWebFlux to allow Spring Boot to auto-configure WebFlux or you should configure its codecs manually so that they use your ObjectMapper.

I think no Datasource in this app.

I feel really silly about this now. It turns out someone uploaded something to our internal artifactory for commons-lang that was not really commons-lang. No idea how that happened, but it was a never-ending source of frustration for me. If anyone else ever sees something that doesn't make sense like this, compare the size of the jar in your .m2 folder with one downloaded directly from maven central. That would have saved me a lot of time.

Do you explicitly need version 2.12.2 of jackson-dataformat-xml?

Problem

jackson-dataformat-xml:2.12.2 is not compatible with jackson dependencies 2.11.4. Spring Boot overwrites Jackson dependencies that are not specified other way in dependencies block or in dependencyManagement.

Solution

If you don't need 2.12.2 then just define the jackson-dataformat-xml as following:

As mentioned here https://github.com/spring-projects/spring-boot/issues/25049#event-4265028906

The issue appears to have been the spring-boot-email-core

In your dependency declaration for org.apache.activemq:artemis-jms-client you can exclude org.apache.geronimo.specs:geronimo-jms_2.0_spec, e.g.:

Well the correct term is that @EnableAuthorizationServer is in maintenance mode which basically means deprecated. As in there will be no added features or updates.

The story goes basically as follows.

During Spring 4 i believe there was a single person that maintained the oauth2 part of spring security. When Spring security 5 was launched the team at pivotal decided to do a major overhaul of spring security and the oauth2 parts. So what they did was to drop Authorisation server support, and instead focus on the Resource server support at first.

Spring announcement of dropping Authorisation server support

You have pulled in spring-cloud-starter-oauth2 which in turn har a peer dependency on spring-security-oauth2-autoconfigure which in turn pulls in spring-security-oauth2.

Here Spring clearly states that if you wish to use spring-security-oauth2 they will help you out, but it is in maintenance mode.

The choice to not support it was made because an authorization server is like owning a product. Spring doesn't maintain their own database, or own Ldap server etc. There are plenty of auth servers out there that can be used, okta, curity, github, fb, google, etc, etc.

But Spring has actually reevaluated that choice and decided to start a community developed open source authorisation server

So you have 3 choices:

• use the old, that is in maintenance mode
• use a 3rd party vendor, github, fb, google, okta, curity etc.
• try out the new open source authorisation server