aws / aws/serverless-java-container

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

未關閉
#622 3 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
question
主要語言
Java
星號
1.6k
分支
574
PR 合併指標
30 天內沒有已合併 PR

描述

*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
```

貢獻指南

開啟貢獻指南

研究方向

從 `SpringBootLambdaContainerHandler.getAwsProxyHandler(...)` 進入點開始,並使用包含 WebFlux 且排除 Netty 的 Spring Boot 3 應用程式重現此行為。追蹤程式庫如何選擇 reactive 模式或 servlet 模式;當存在 Spring web 相依性時,應用程式會被視為 servlet 應用程式,即表示完成。

由索引模型根據 Issue 內容生成。

評估

技術堆疊
aws, java, spring-boot
領域
api, backend, cloud
Issue 類型
缺陷
難度
4/5
預估耗時
3-5 天
活躍度
停滯
描述清晰度
需要釐清
新手友好度
25/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。