Unexpected startup of web server with RabbitMQ starter

[nithia]

Since 2.0.1, Spring Boot creates a AnnotationConfigReactiveWebServerApplicationContext as the application context instead of, as in 2.0.0, AnnotationConfigApplicationContext. This happens even if there is no web functionality in the project. This leads to the application trying to start a Netty web server on port 8080 for no apparent reason.

The attached project was generated from start.spring.io and includes only a RabbitMQ starter. On startup it creates handlers for URLs /webjars/** and /** for no apparent reason. This is both surprising and inconvenient as there doesn't seem to be any easy way to turn it off.

demo.zip

[snicoll]

@nithia very nice, thank you for the sample. The AMQP client now brings reactor-netty and a bunch of other libraries that I wonder if they are legit. So your report is specific to AMQP only and looking at what is on the classpath, I think it's legit for Spring Boot to attempt to start a web server (in other words, something that the RabbitMQ starter brings is broken).

This is both surprising and inconvenient as there doesn't seem to be any easy way to turn it off.

If you have a web environment and you want to disable it, add this to application.properties:

spring.main.web-application-type=none

I thought this was documented explicitly but it isn't so we should fix that as well.

[snicoll]

I've added a section in the doc in 31441a7

[nithia]

Thanks for the speedy response @snicoll 👍 Adding the property solves my immediate problem. Now I can get those Ops people off my back :)

[snicoll]

If we want to fix in 2.0.x, we'll have to exclude that dependency in Spring Boot as Spring AMQP has no plan to do this short term