Java 带Spring引导的侦听消息队列SQS不适用于标准配置

Java 带Spring引导的侦听消息队列SQS不适用于标准配置,java,spring-boot,amazon-sqs,spring-messaging,spring-cloud-aws,Java,Spring Boot,Amazon Sqs,Spring Messaging,Spring Cloud Aws,我无法使用Spring Boot和SQS创建works队列侦听器 (消息已发送并显示在SQS ui中) @MessageMapping或@SqsListener不起作用 爪哇:11 弹簧靴:2.1.7 Dependencie:spring云aws消息传递 这是我的配置 @Configuration @EnableSqs public class SqsConfig { @Value("#{'${env.name:DEV}'}") private String envName;

我无法使用Spring Boot和SQS创建works队列侦听器 (消息已发送并显示在SQS ui中)

@MessageMapping
@SqsListener
不起作用

爪哇:11
弹簧靴:2.1.7
Dependencie:spring云aws消息传递

这是我的配置

@Configuration
@EnableSqs
public class SqsConfig {

    @Value("#{'${env.name:DEV}'}")
    private String envName;

    @Value("${cloud.aws.region.static}")
    private String region;

    @Value("${cloud.aws.credentials.access-key}")
    private String awsAccessKey;

    @Value("${cloud.aws.credentials.secret-key}")
    private String awsSecretKey;

    @Bean
    public Headers headers() {
        return new Headers();
    }

    @Bean
    public MessageQueue queueMessagingSqs(Headers headers,
                                          QueueMessagingTemplate queueMessagingTemplate) {
        Sqs queue = new Sqs();
        queue.setQueueMessagingTemplate(queueMessagingTemplate);
        queue.setHeaders(headers);
        return queue;
    }

    private ResourceIdResolver getResourceIdResolver() {
        return queueName -> envName + "-" + queueName;
    }

    @Bean
    public DestinationResolver destinationResolver(AmazonSQSAsync amazonSQSAsync) {
        DynamicQueueUrlDestinationResolver destinationResolver = new DynamicQueueUrlDestinationResolver(
                amazonSQSAsync,
                getResourceIdResolver());
        destinationResolver.setAutoCreate(true);
        return destinationResolver;
    }

    @Bean
    public QueueMessagingTemplate queueMessagingTemplate(AmazonSQSAsync amazonSQSAsync,
                                                         DestinationResolver destinationResolver) {
        return new QueueMessagingTemplate(amazonSQSAsync, destinationResolver, null);
    }

    @Bean
    public QueueMessageHandlerFactory queueMessageHandlerFactory() {
        QueueMessageHandlerFactory factory = new QueueMessageHandlerFactory();
        MappingJackson2MessageConverter messageConverter = new MappingJackson2MessageConverter();
        messageConverter.setStrictContentTypeMatch(false);
        factory.setArgumentResolvers(Collections.singletonList(new PayloadArgumentResolver(messageConverter)));
        return factory;
    }

    @Bean
    public SimpleMessageListenerContainerFactory simpleMessageListenerContainerFactory(AmazonSQSAsync amazonSqs) {
        SimpleMessageListenerContainerFactory factory = new SimpleMessageListenerContainerFactory();
        factory.setAmazonSqs(amazonSqs);
        factory.setMaxNumberOfMessages(10);
        factory.setWaitTimeOut(2);
        return factory;
    }

}
我还注意到,
org.springframework.cloud.aws.messaging.config.SimpleMessageListenerContainerFactory
org.springframework.cloud.aws.messaging.config.annotation.SqsConfiguration
在启动时运行

还有我的测试

@RunWith(SpringJUnit4ClassRunner.class)
public class ListenTest {

    @Autowired
    private MessageQueue queue;

    private final String queueName = "test-queue-receive";

    private String result = null;

    @Test
    public void test_listen() {
        // given
        String data = "abc";

        // when
        queue.send(queueName, data).join();

        // then
        Awaitility.await()
                .atMost(10, TimeUnit.SECONDS)
                .until(() -> Objects.nonNull(result));

        Assertions.assertThat(result).equals(data);
    }

    @MessageMapping(value = queueName)
    public void receive(String data) {
        this.result = data;
    }
}

你觉得有什么不对劲吗

我创建了一个回购协议,例如:()
在测试文件夹中,在“application.yml”中更改aws凭据

然后运行测试

我在使用spring cloud aws消息传递包时遇到了同样的问题,但后来我在@SqsListener注释中使用了队列URL,而不是队列名称,结果成功了

@SqsListener(value = { "https://full-queue-URL" }, deletionPolicy = SqsMessageDeletionPolicy.ON_SUCCESS)
public void receive(String message) {
     // do something
}
在使用SpringCloudStarter aws消息传递包时,似乎可以使用队列名称。我相信如果您不想使用starter包,有一些配置允许使用队列名称而不是URL


编辑:我注意到,尽管我在属性文件中列出了us-east-1,但该地区被默认为us-west-2。然后我创建了一个RegionProvider bean,并在其中将区域设置为us-east-1,现在当我在@SqsMessaging中使用队列名称时,它被找到并正确解析为框架代码中的URL。

您需要利用@Primary注释,这对我来说是有效的:

@Autowired(required = false)
private AWSCredentialsProvider awsCredentialsProvider;

@Autowired
private AppConfig appConfig;

@Bean
public QueueMessagingTemplate getQueueMessagingTemplate() {
    return new QueueMessagingTemplate(sqsClient());
}

@Primary
@Bean
public AmazonSQSAsync sqsClient() {
    AmazonSQSAsyncClientBuilder builder = AmazonSQSAsyncClientBuilder.standard();

    if (this.awsCredentialsProvider != null) {
        builder.withCredentials(this.awsCredentialsProvider);
    }

    if (appConfig.getSqsRegion() != null) {
        builder.withRegion(appConfig.getSqsRegion());
    } else {
        builder.withRegion(Regions.DEFAULT_REGION);
    }

    return builder.build();
}
build.gradle需要这些dep:

implementation("org.springframework.cloud:spring-cloud-starter-aws:2.2.0.RELEASE")
implementation("org.springframework.cloud:spring-cloud-aws-messaging:2.2.0.RELEASE")

请比“不起作用”更具体。具体发生了什么?在任何地方是否有错误消息,或者SQS错误队列中是否有消息?SQS队列中的消息保持在队列中,并且receive()方法从不运行。似乎
@MessageMapping(value=queueName)
没有侦听队列?我不确定这个工具。我只在QueueMessageHandler中使用了
@SqsListener
@SqsListener不太有效:/SqsListener sqslisteneranotation=AnnotationUtils.findAnnotation(方法,SqsListener.class)始终为空。因此Spring dot不会在@SpringBootTest中扫描@Sqs,也不会在@CompentTest中扫描。您可以发布RegionProvider@Bean方法的代码片段吗?@heug
@Bean public RegionProvider RegionProvider(){return()->Region.getRegion(Regions.fromName(queueRegion));}
什么是AppConfig?@EvanGertis对保存env变量的bean的引用