Spring cloud function on aws getting connection refused exception from netty #367
Comments
|
I noticed this only happens when the cloud function actually throws exception |
|
After generating from the Spring Initializr and taking a look at the cloud-function-aws-samples I get the same error. Haven't been able to get a working version up yet. |
|
I cannot reproduce this problem. Functional Bean Registration is working for me and decreasing the startup time on AWS with around 50%. Do you have a class eg. |
|
My example can be found here, tried a few different things already: https://github.com/drissamri/aws-lambda-runtime-coldstart/tree/master/5-java8-spring I didn't get the exception locally anymore but I still did when deployed on AWS |
|
I got the same exception. For me it was fixed with the following steps. |
|
@kleung Does the above help you out? If not, can you show us your code? |
|
My code is as follows: Application: @SpringBootConfiguration
public class TestAwsLambdaAuthorizerApplication implements ApplicationContextInitializer<GenericApplicationContext> {
private static final Logger LOG = LoggerFactory.getLogger(TestAwsLambdaAuthorizerApplication.class);
private Context context;
@Autowired
public void setContext(Context context) {
LOG.info("Context: {}", context);
this.context = context;
}
public static void main(String[] args) {
FunctionalSpringApplication.run(TestAwsLambdaAuthorizerApplication.class, args);
}
public AuthorizerFunction authorizer() {
return new AuthorizerFunction();
}
public TestFunction testFunction() {
return new TestFunction();
}
@Override
public void initialize(GenericApplicationContext context) {
context.registerBean("authorizer", FunctionRegistration.class,
() ->
new FunctionRegistration<>(authorizer())
.type(FunctionType.from(APIGatewayProxyRequestEvent.class).to(AuthPolicy.class))
);
context.registerBean("testFunction", FunctionRegistration.class,
() ->
new FunctionRegistration<>(testFunction())
.type(FunctionType.from(String.class).to(String.class))
);
}
}Request Handler public class AuthorizerEventHandler extends SpringBootRequestHandler<APIGatewayProxyRequestEvent, AuthPolicy> {
}Function public class AuthorizerFunction implements Function<APIGatewayProxyRequestEvent, AuthPolicy> {
private static final Logger LOG = LoggerFactory.getLogger(AuthorizerFunction.class);
private Context context;
public AuthorizerFunction() {
super();
}
@Autowired
@Qualifier("targetExecutionContext")
public void setContext(Context context) {
LOG.info("Context: {}", context);
this.context = context;
}
@Override
public AuthPolicy apply(APIGatewayProxyRequestEvent event) {
String functionArn = context.getInvokedFunctionArn();
LOG.info("ARN: {}", functionArn);
String[] arnPartials = functionArn.split(":");
String region = arnPartials[3];
APIGatewayProxyRequestEvent.ProxyRequestContext requestContext = event.getRequestContext();
String awsAccountId = requestContext.getAccountId();
String restApiId = requestContext.getApiId();
String stage = requestContext.getStage();
AuthPolicy result = new AuthPolicy("fake-principal",
AuthPolicy.PolicyDocument.getDenyAllPolicy(region,
awsAccountId,
restApiId,
stage));
Map<String, String> headers = event.getHeaders();
String apiKey = headers.get("x-api-key");
LOG.info("api key: {}", apiKey);
if((!StringUtils.isEmpty(apiKey)) && ("abcd1234".equalsIgnoreCase(apiKey))) {
result = new AuthPolicy("fake-principal",
AuthPolicy.PolicyDocument.getAllowAllPolicy(region,
awsAccountId,
restApiId,
stage));
}
return result;
}
}And another function (skipped here), then I point the bean with FUNCTION_NAME environment variable, I did exactly the same as you mentioned but that error happened. |
|
I took a look at the code in your repository. These are the changes: kleung/SpringCloudFunctionAwsAuthorizerTest#1 After these changes I get an expected NullPointerException from your logic since I am not invoking the function with your correct event. |
|
I don't think this is an issue anymore. That said, there were also some enhancements. One of them is that you no longer need to specify an empty AWS request handler as we provide generic one that handles everything from API gateway, to stream, to Kinesis. We have updated user guide, so feedback is welcome |
|
I have the same error but i fixed when add an profile in my pom.xml for the aws dependencies and run the test without aws profile. mvn testThis is the part of aws profile dependencies <profiles>
<profile>
<id>aws</id>
<dependencies>
<dependency>
<groupId>org.springframework.cloud</groupId>
<artifactId>spring-cloud-function-adapter-aws</artifactId>
</dependency>
<dependency>
<groupId>com.amazonaws</groupId>
<artifactId>aws-lambda-java-events</artifactId>
<version>2.0.2</version>
</dependency>
<dependency>
<groupId>com.amazonaws</groupId>
<artifactId>aws-lambda-java-core</artifactId>
<version>1.1.0</version>
<scope>provided</scope>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-deploy-plugin</artifactId>
<configuration>
<skip>true</skip>
</configuration>
</plugin>
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<dependencies>
<dependency>
<groupId>org.springframework.boot.experimental</groupId>
<artifactId>spring-boot-thin-layout</artifactId>
<version>1.0.17.RELEASE</version>
</dependency>
</dependencies>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-shade-plugin</artifactId>
<version>3.2.4</version>
<configuration>
<createDependencyReducedPom>false</createDependencyReducedPom>
<shadedArtifactAttached>true</shadedArtifactAttached>
<shadedClassifierName>aws</shadedClassifierName>
</configuration>
</plugin>
</plugins>
</build>
</profile>
</profiles>This is the pom.xml , ignore rekognition libraries.<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-parent</artifactId>
<version>2.3.4.RELEASE</version>
<relativePath/> <!-- lookup parent from repository -->
</parent>
<groupId>com.some</groupId>
<artifactId>x</artifactId>
<version>0.0.1-SNAPSHOT</version>
<name>x</name>
<description>Demo project for Spring Boot</description>
<properties>
<java.version>1.8</java.version>
<spring-cloud.version>Hoxton.SR8</spring-cloud.version>
</properties>
<dependencies>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter</artifactId>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-web</artifactId>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.springframework.cloud</groupId>
<artifactId>spring-cloud-starter-function-webflux</artifactId>
</dependency>
<dependency>
<groupId>org.springframework.cloud</groupId>
<artifactId>spring-cloud-function-compiler</artifactId>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-configuration-processor</artifactId>
<optional>true</optional>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-devtools</artifactId>
<scope>runtime</scope>
<optional>true</optional>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-test</artifactId>
<scope>test</scope>
<exclusions>
<exclusion>
<groupId>org.junit.vintage</groupId>
<artifactId>junit-vintage-engine</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>com.amazonaws</groupId>
<artifactId>aws-java-sdk-rekognition</artifactId>
<version>1.11.860</version>
</dependency>
<dependency>
<groupId>com.amazonaws</groupId>
<artifactId>aws-java-sdk-transcribe</artifactId>
<version>1.11.864</version>
</dependency>
<dependency>
<groupId>org.projectlombok</groupId>
<artifactId>lombok</artifactId>
<optional>true</optional>
</dependency>
<dependency>
<groupId>com.amazonaws</groupId>
<artifactId>aws-java-sdk-sns</artifactId>
<version>1.11.860</version>
</dependency>
</dependencies>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.springframework.cloud</groupId>
<artifactId>spring-cloud-dependencies</artifactId>
<version>${spring-cloud.version}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
<profiles>
<profile>
<id>aws</id>
<dependencies>
<dependency>
<groupId>org.springframework.cloud</groupId>
<artifactId>spring-cloud-function-adapter-aws</artifactId>
</dependency>
<dependency>
<groupId>com.amazonaws</groupId>
<artifactId>aws-lambda-java-events</artifactId>
<version>2.0.2</version>
</dependency>
<dependency>
<groupId>com.amazonaws</groupId>
<artifactId>aws-lambda-java-core</artifactId>
<version>1.1.0</version>
<scope>provided</scope>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-deploy-plugin</artifactId>
<configuration>
<skip>true</skip>
</configuration>
</plugin>
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<dependencies>
<dependency>
<groupId>org.springframework.boot.experimental</groupId>
<artifactId>spring-boot-thin-layout</artifactId>
<version>1.0.17.RELEASE</version>
</dependency>
</dependencies>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-shade-plugin</artifactId>
<version>3.2.4</version>
<configuration>
<createDependencyReducedPom>false</createDependencyReducedPom>
<shadedArtifactAttached>true</shadedArtifactAttached>
<shadedClassifierName>aws</shadedClassifierName>
</configuration>
</plugin>
</plugins>
</build>
</profile>
</profiles>
<build>
<plugins>
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
</plugin>
</plugins>
</build>
</project>
|
|
There have been many improvements, updates and enhancements to AWS recently, so given the age of this issue I will close it with no action, but feel free to give it try and raise new issues as you discover them |
Using version 2.1.0.RELEASE of spring-cloud-function-(core, context, adapter-aws, webflux and web) cause the following stack trace when deployed on aws:
NOTE: I tried both functional and non-function bean registration still ends up the same error.
I think this is the same issue as stackoverflow post: https://stackoverflow.com/questions/56138363/why-is-my-spring-cloud-function-attempting-to-open-local-http-connections
The text was updated successfully, but these errors were encountered: