AWS lambda : Spring boot 3 Servlet application having webflux dependency for web client

未关闭
#622 3 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
25/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
停滞
技术栈
aws, java, spring-boot
领域
api, backend, cloud

调研方向

从 SpringBootLambdaContainerHandler.getAwsProxyHandler(...) 入口点开始,并使用包含 WebFlux 且排除 Netty 的 Spring Boot 3 应用程序复现该行为。跟踪库如何选择 reactive 模式或 servlet 模式;当存在 Spring web 依赖时,应用程序被视为 servlet 应用程序,即表示完成。

由索引模型根据 Issue 内容生成。

描述

question

To help us debug your issue fill in the basic information below using the options provided

Serverless Java Container version: `2.0.0.M2

Implementations: `Spring Boot 3

Framework version: eg SpringBoot 3.1.2

Frontend service: REST API /ALB

Deployment method: eg SAM, Serverless Framework, Console

Scenario

Describe what you are trying to accomplish
I am having Spring boot 3 Microservice deployed as AWS lambda. This microservice contains Webflux dependnecy for Spring Reactive WebClient. I have excluded Netty dependency from WebFlux. AWS Java Serverless library considering AWS lambda as Reactibe but I want it to be Servlet.

Expected behavior

Describe how you would expect the application to behave
Please provide way to set up servlet web application type even it contains web flux dependency.
or
Check if spring web dependency is available, it should be servlet application

Spring is considering Reactive WebClient as synchronous in case spring web dependency is available

Actual behavior

Describe what you are seeing instead

Reactive web application type is considered by library

Steps to reproduce

Provide code samples we can use to reproduce the issue as part of our integration tests. If there is a public repository for the misbehaving application link to it here

handler = SpringBootLambdaContainerHandler.getAwsProxyHandler(Class.forName(System.getenv(APPLICATION)));

Full log output

Paste the full log output from the Lambda function's CloudWatch logs

logs
主要语言
Java
星标
1.6k
派生
575
平均合并
1 天 15 小时
30 天内合并 PR
12

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

aws/serverless-java-container 的其他 Issue

查看 aws/serverless-java-container 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。