Early queue connection and message consumption causes issues on application startup #125
Closed
3 tasks done
Comments
|
I was able to take the test in your repo https://github.com/micronaut-projects/micronaut-jms/blob/master/tests/tasks-sqs/src/test/groovy/example/TasksSpec.groovy For others with the same problem: @MicronautTest(transactional = false, environments = {"local", "test"})
@TestInstance(TestInstance.Lifecycle.PER_CLASS)// When using TestPropertyProvider you test must be declared with JUnit’s @TestInstance(TestInstance.Lifecycle.PER_CLASS) annotation
@Slf4j
public class TransactionEventPipelineIntegrationTest {
@Container
public static LocalStackContainer localstack = new LocalStackContainer(DockerImageName.parse("localstack/localstack"), false)
.withServices(LocalStackContainer.Service.SQS);
@Inject
private TransactionEventProducer eventProducer;
@Test
void test() {
String payload = "some message";
eventProducer.send(payload);
}
@Override
public Map<String, String> getProperties() {
localstack.start();
return Map.of(
"aws.sqs.endpoint", localstack.getEndpointOverride(LocalStackContainer.Service.SQS).toString(),
"aws.region", localstack.getRegion()
);
}Next thing is, I'll have to create the queue before the Listener starts. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there a way to delay the listener to consume messages?
In our environments the listener starts consuming messages while the application itself hasn't fully initialised itself, e.g. not all beans have been created, this can delay the overall application startup while message consumption takes place.
Another issue is, when trying to write tests with TestContainers the Listener is instantiated before TestContainers brings up the localstack.
Task List
Steps to Reproduce
Expected Behaviour
Delay connection to queue and message consumption until certain criteria are met, e.g. startup checks have been performed or TestContainers has been initialised.
Actual Behaviour
Test application startup fails
Environment Information
The text was updated successfully, but these errors were encountered: