这样的警告最终会导致微服务崩溃吗？
"负重"，（不如）赌一把!）（不是警告本身，而是抱怨的事实）
如何应对这一警告？

• • 当（我们认为）"负载"不成问题时，我们 * 可以 * 忽略警告。**但解决方案并不昂贵：

参见：Asynchronous REST API generating warning
引用：

@Configuration
@EnableAsync
public class AsyncConfig  implements AsyncConfigurer {

  @Bean
  protected WebMvcConfigurer webMvcConfigurer() {
    return new WebMvcConfigurerAdapter() {
        @Override
        public void configureAsyncSupport(AsyncSupportConfigurer configurer) {
            configurer.setTaskExecutor(getTaskExecutor());
        }
    };
  }

  @Bean
  protected ConcurrentTaskExecutor getTaskExecutor() {
    return new ConcurrentTaskExecutor(Executors.newFixedThreadPool(5));
  }
}

或者，我们可以配置任意（警告消失：非平凡的）TaskExecutor实现。
另见：

• https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/core/task/TaskExecutor.html
• https://docs.spring.io/spring-framework/docs/current/reference/html/integration.html#scheduling

我通过使用2个@Configuration bean修复了这个问题，如下所示：

@Configuration
@EnableAsync
public class MyApplicationConfiguration {
}

以及

@Configuration
public class WebMvcConfiguration implements WebMvcConfigurer {
    @Override
    public void configureAsyncSupport(AsyncSupportConfigurer configurer) {
        configurer.setTaskExecutor(asyncTaskExecutor());
    }

    @Bean
    public AsyncTaskExecutor asyncTaskExecutor() {
        return new ConcurrentTaskExecutor(Executors.newFixedThreadPool(5));
    }
}