ArnauAregall
commented
1 year ago Adding a bit more info if it helps:
The error is also somehow reproducible when serializing the return type POJOs.
Managed to reproduce it by invoking the lambda using aws lambda invoke cli command.
aws lambda invoke \
--function-name aws-lambda-spring-cloud-f-SpringCloudFunctionLambd-.... \
--cli-binary-format raw-in-base64-out \
--payload '[{"latitude": 42.99, "longitude": 2.83 }, {"latitude": 43.01, "longitude": 2.21 } ]' output.txtResponse:
{
"StatusCode": 200,
"FunctionError": "Unhandled",
"ExecutedVersion": "$LATEST"
}output.txt:
{
"errorType": "IllegalArgumentException",
"errorMessage": "Payload must not be null",
"stackTrace": "java.lang.IllegalArgumentException: Payload must not be null\n\tat org.springframework.util.Assert.notNull(Assert.java:204)\n\tat org.springframework.messaging.support.MessageBuilder.<init>(MessageBuilder.java:58)\n\tat org.springframework.messaging.support.MessageBuilder.withPayload(MessageBuilder.java:190)\n\tat org.springframework.cloud.function.adapter.aws.AWSLambdaUtils.generateOutputFromObject(AWSLambdaUtils.java:176)\n\tat org.springframework.cloud.function.adapter.aws.CustomRuntimeEventLoop.eventLoop(CustomRuntimeEventLoop.java:166)\n\tat org.springframework.cloud.function.adapter.aws.CustomRuntimeEventLoop.lambda$run$0(CustomRuntimeEventLoop.java:90)\n\tat java.base@17.0.5/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)\n\tat java.base@17.0.5/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)\n\tat java.base@17.0.5/java.lang.Thread.run(Thread.java:833)\n\tat org.graalvm.nativeimage.builder/com.oracle.svm.core.thread.PlatformThreads.threadStartRoutine(PlatformThreads.java:775)\n\tat org.graalvm.nativeimage.builder/com.oracle.svm.core.posix.thread.PosixPlatformThreads.pthreadStartRoutine(PosixPlatformThreads.java:203)\n"
}Logs:
2023-06-25T19:00:36.111Z DEBUG 9 --- [pool-5-thread-1] c.f.c.c.BeanFactoryAwareFunctionRegistry : Invoking function forecast<reactor.core.publisher.Flux<tech.aaregall.lab.function.weather.domain.GeoLocation>, reactor.core.publisher.Flux<tech.aaregall.lab.function.weather.domain.Forecast>>
2023-06-25T19:00:36.111000 2023-06-25T19:00:36.111Z DEBUG 9 --- [pool-5-thread-1] c.f.c.c.BeanFactoryAwareFunctionRegistry : Converting JSON string representing collection to a list of Messages. Function 'forecast<reactor.core.publisher.Flux<tech.aaregall.lab.function.weather.domain.GeoLocation>, reactor.core.publisher.Flux<tech.aaregall.lab.function.weather.domain.Forecast>>' will be invoked iteratively
2023-06-25T19:00:36.112000 2023-06-25T19:00:36.112Z DEBUG 9 --- [pool-5-thread-1] c.f.c.c.BeanFactoryAwareFunctionRegistry : Invoking function: forecast<reactor.core.publisher.Flux<tech.aaregall.lab.function.weather.domain.GeoLocation>, reactor.core.publisher.Flux<tech.aaregall.lab.function.weather.domain.Forecast>>with input type: reactor.core.publisher.Flux<tech.aaregall.lab.function.weather.domain.GeoLocation>
2023-06-25T19:00:36.112000 2023-06-25T19:00:36.112Z DEBUG 9 --- [pool-5-thread-1] o.s.c.f.a.aws.CustomRuntimeEventLoop : Reply from function: FluxMap
2023-06-25T19:00:36.112000 2023-06-25T19:00:36.112Z DEBUG 9 --- [pool-5-thread-1] c.f.c.c.BeanFactoryAwareFunctionRegistry : Converted Message: GenericMessage [payload={latitude=42.99, longitude=2.83}, headers={id=540951aa-c67b-22e2-56a7-6ed76137007a, timestamp=1687719636111}] to: class tech.aaregall.lab.function.weather.domain.GeoLocation
2023-06-25T19:00:36.112000 2023-06-25T19:00:36.112Z DEBUG 9 --- [pool-5-thread-1] c.f.c.c.BeanFactoryAwareFunctionRegistry : Converted Message: GenericMessage [payload={latitude=43.01, longitude=2.21}, headers={id=ab6b39c9-f56f-5d19-2512-22fbca5f7820, timestamp=1687719636111}] to: class tech.aaregall.lab.function.weather.domain.GeoLocation
2023-06-25T19:00:36.145000 2023-06-25T19:00:36.145Z DEBUG 9 --- [pool-5-thread-1] o.s.c.f.adapter.aws.AWSLambdaUtils : Response value: GenericMessage [payload=byte[11831], headers={contentType=application/json, id=7025cb06-5e20-7770-6884-90ca27b037ae, timestamp=1687719636145}]
2023-06-25T19:00:36.148000 2023-06-25T19:00:36.148Z DEBUG 9 --- [pool-5-thread-1] o.s.c.f.adapter.aws.AWSLambdaUtils : Response value: GenericMessage [payload=byte[11835], headers={contentType=application/json, id=0c1ca3d6-8c58-438e-d5a6-c0b8cdc8ddda, timestamp=1687719636148}]
2023-06-25T19:00:36.148000 2023-06-25T19:00:36.148Z DEBUG 9 --- [pool-5-thread-1] o.s.c.f.adapter.aws.AWSLambdaUtils : OUTPUT: [GenericMessage [payload=byte[11831], headers={contentType=application/json, id=7025cb06-5e20-7770-6884-90ca27b037ae, timestamp=1687719636145}], GenericMessage [payload=byte[11835], headers={contentType=application/json, id=0c1ca3d6-8c58-438e-d5a6-c0b8cdc8ddda, timestamp=1687719636148}]] - java.util.ArrayList
2023-06-25T19:00:36.151000 2023-06-25T19:00:36.150Z INFO 9 --- [pool-5-thread-1] o.s.c.f.a.aws.CustomRuntimeEventLoop : Result ERROR status: 202 ACCEPTEDReading the logs it can be appreciated that the two JSON objects in the array of the payload were successfully converted to GeoLocation POJOs.
But apparently it also failed on when converting the return type: org.springframework.cloud.function.adapter.aws.AWSLambdaUtils.generateOutputFromObject(AWSLambdaUtils.java:176)
OUTPUT ... log produced by AWSLambdaUtils also indicates the return class is an java.uti.ArrayList whereas the function is defined with a return type of Flux<Forecast>.
olegz
jeusdi
Describe the bug
Using:
3.1.12022.0.3(SCF4.0.3)Related to
org.springframework.cloud:spring-cloud-function-adapter-aws:When running a Spring Cloud Function application on an AWS Lambda,
AWSTypesMessageConverterseems to not be capable to correctly convert a JSON array body when the functions consume aFlux<T>, whereTis a regular application domain class/POJO.The domain class:
The function definition:
When invoking the AWS Lambda function with a body such as
It fails with the following Jackson conversion error:
Nevertheless it works perfectly when the application is not running on AWS (locally, or on a Docker Image) being able to take more "geolocations" in the payload, which is the intention.
Sample
I built a sample application to demonstrate the issue: https://github.com/ArnauAregall/aws-lambda-spring-cloud-function-reactive-java
If you clone and run the application locally:
The
response.jsonfile will be a JSON array containing a single object representing the weather forecast for those coordinates.But when running in AWS:
The same command against the lambda URL will result in "Internal Server Error" with the mentioned stacktrace above.