Skip to content
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

concurrency attribute is not needed at this stage #8

Open
ozangunalp opened this issue Dec 20, 2023 · 4 comments
Open

concurrency attribute is not needed at this stage #8

ozangunalp opened this issue Dec 20, 2023 · 4 comments

Comments

@ozangunalp
Copy link
Collaborator

https://github.com/SolaceCoEExt/solace-quarkus/blob/76d9f4fe7052f2c4e5eff06ed9077de93036ca6f/pubsub-plus-connector/src/main/java/io/quarkiverse/solace/SolaceConnector.java#L53-L54

The concurrent processing of messages on worker threads using Reactive Messaging is configurable using the @Blocking(ordered=false) annotation on the processor method : https://smallrye.io/smallrye-reactive-messaging/latest/concepts/blocking/

For processing messages concurrently on event loop threads concurrency attribute is made available on Reactive Messaging 4.12.0 release.

@SravanThotakura05
Copy link
Collaborator

@ozangunalp shall we leave this issue open till we migrate to 4.12.0. release?

@ozangunalp
Copy link
Collaborator Author

Sure, It is useful for tracking

@tqvarnst
Copy link

tqvarnst commented Jan 5, 2024

Keep in mind that 4.12 is not part of any LTS/product release yet and to be in the next product release, it should be in 3.7. @ozangunalp will reactive messaging 4.12 be in Quarkus 3.7?

@ozangunalp
Copy link
Collaborator Author

Yes, on Quarkus 3.7 we will be targeting at least the reactive messaging 4.14.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants