reactor-core | Non-Blocking Reactive Foundation for the JVM | Reactive Programming library

You have configured the wrong option on the driver. METADATA_SCHEMA_REQUEST_TIMEOUT is the timeout for the requests to retrieve the schema.

The default request timeout for the Java driver is basic.request.timeout (see reference configuration):

The main point here i think is the way you are organizing the code, it seems to me that you are using a reactive framework, but thinking and coding in an imperative way.

If you change the generateToken and doGenerateToken to return a Mono, you can do something like the following:

Please check the below steps if they help to workaround -

• java.lang.NoSuchMethodError majorly occurs due to version conflicts of dependencies.
• There may be few methods or libraries not compatible or missing in the project.
• To resolve this, try upgrading or even downgrading the dependent versions.
• In some cases, removing the unnecessary dependencies also works.
• Please check this official java doc of SilentParameter class and its related methods.
• In general, NoSuchMethodError error happens if class A expects a method in class B which was compiled but at run time the other classes does not have that method. Here the method can be a third party jar library or normal method in the classes.
• Sometimes it might be, you have complied the code against a version of some library that can also be the JDK itself, but your runtime is having other versions and it might be the case of one of the modules where you have added a method, forgot to compile, so at runtime it is using the old version.

It looks like some other thread called MongoClient.close()

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

Actually the behaviour is by design because @NonNullApi which is applied to a package from where you are calling the method (map), doesn't have type use default qualifier, but only METHOD and PARAMETER. In particular, it means that the Kotlin compiler doesn't enhance types inside type argument positions, but only whole types in return type and value parameter positions.

It can be proved with the following code:

It got resolved. There were two issues - 1) with the graphQL schema ad 2) with the WebClient.

I corrected the schema and using the HttpClient instead of WebClient.

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.

You have specified a redirect-uri for your client of /login. The page that says "Login with OAuth 2.0" is an auto-generated login page that Spring Security makes available by default under the /login endpoint. I don't think you intended to redirect there, but you currently have configured your client to do so.

The docs for OAuth 2.0 Login with WebFlux (Reactive) have recently been rewritten to align with the Servlet version, and are worth reading in their entirety.

Read the section of the docs on the Redirection Endpoint. Until you have a basic flow working, I'd recommend setting your redirect-uri to the default value of "{baseUrl}/login/oauth2/code/{registrationId}". Once things work, you can begin exploring how to customize this value. As the docs state, keep in mind that changing your redirect-uri property for a client also requires customizing the Redirection Endpoint in Spring Security to match.

If you also wish to customize the default Login Page, see the previous section of the docs, OAuth 2.0 Login Page.