New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JMS topic subscription #408

christophd opened this Issue Jun 6, 2018 · 0 comments


None yet
1 participant

christophd commented Jun 6, 2018

Citrus starts the JMS topic subscription when the first receive action is asking for messages to consume. In fact Citrus starts/stops the subscription per receive action. This leads to loosing messages that were sent to the topic before the receive action in the test is performed.

Citrus should provide a topic subscription per endpoint that is started/stopped with the endpoint lifecylce. This would ensure that incoming message events are cached until the receive action in the test case is performed for consuming the messages.

@christophd christophd added this to the v2.7.6 milestone Jun 6, 2018

christophd added a commit that referenced this issue Jun 6, 2018

@christophd christophd closed this Jun 6, 2018

@christophd christophd removed the READY label Jun 13, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment