ARTEMIS-2449 limit size of producer details #272
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The core server session tracks details about producers like what addresses have had messages sent to them, the most recent message ID sent to each address, and the number of messages sent to each address. This information is made available to users via the listProducersInfoAsJSON method on the various management interfaces (JMX, web console, etc.). However, in situations where a server session is long lived (e.g. in a pool) and is used to send to many different addresses (e.g. randomly named temporary JMS queues) this info can accumulate to a problematic degree. Therefore, we should limit the amount of producer details saved by the session. (cherry picked from commit 9d44c40) downstream: ENTMQBR-2711
franz1981
added
QE Review Needed
Engineering Ack
TEST-ADDED
|
It is the same PR of #271 but with right commit message and downstream jira reference |
|
thanks for the PR Tests run: 7, Failures: 0, Errors: 0, Skipped: 0 QE Ack. |
franz1981
added a commit
that referenced
this pull request
Aug 9, 2019
michalxo
added
Customer Issue
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The core server session tracks details about producers like what
addresses have had messages sent to them, the most recent message ID
sent to each address, and the number of messages sent to each address.
This information is made available to users via the
listProducersInfoAsJSON method on the various management interfaces
(JMX, web console, etc.). However, in situations where a server session
is long lived (e.g. in a pool) and is used to send to many different
addresses (e.g. randomly named temporary JMS queues) this info can
accumulate to a problematic degree. Therefore, we should limit the
amount of producer details saved by the session.
(cherry picked from commit 9d44c40)
downstream: ENTMQBR-2711
test: org.apache.activemq.artemis.tests.integration.jms.client.TemporaryDestinationTest#testForTempQueueTargetInfosSizeLimit
component: jms-client
subcomponent: queuing
level: integration
importance: medium
type: functional
subtype: compliance
verifies: AMQ-90