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

Fixes for AMQP/OpenWire scalabitlity #331

Closed

Conversation

clebertsuconic
Copy link
Contributor

These fixes are all related to the same inner issue...

michaelandrepearce and others added 6 commits April 6, 2020 16:37
(cherry picked from commit f1fdfc6)

downstream: ENTMQBR-3381, ENTMQBR-3380
Some of them may throw queue already existed exception

(cherry picked from commit 559fa20)

downstream: ENTMQBR-3381, ENTMQBR-3380
The drain control has to immediately flush
otherwise a next flow control event may remove the previous status from Proton.
So, this really cannot wait the next executor, and it has to be done immediately.

(cherry picked from commit c3128aa)

downstream: ENTMQBR-3356, ENTMQBR-3437
& ARTEMIS-2674 AMQP should use a separate executor for IO

(cherry picked from commit f874a02)

downstream: ENTMQBR-3356, ENTMQBR-3437
(cherry picked from commit bd77a53)

downstream: ENTMQBR-3432, ENTMQBR-3438
(cherry picked from commit af796d5)

downstream: ENTMQBR-3432, ENTMQBR-3438
@brusdev brusdev added the LTS Long term support label Apr 7, 2020
…Settling

(cherry picked from commit 858a824)

downstream: ENTMQBR-3356, ENTMQBR-3437
@clebertsuconic clebertsuconic added the Customer Issue Whether this issue originates from customer (higher importance) label Apr 17, 2020
brusdev added a commit that referenced this pull request Apr 24, 2020
@brusdev
Copy link
Contributor

brusdev commented Apr 24, 2020

merged it

@brusdev brusdev closed this Apr 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Customer Issue Whether this issue originates from customer (higher importance) LTS Long term support
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants