k-wall commented on issue #2568: ARTEMIS-2262: Correlate management response messages with the request URL: https://github.com/apache/activemq-artemis/pull/2568#issuecomment-467790082 > There's a checkstyle issue on your change. (easy to fix) > > Can you provide a use case for why this is needed? is that for enMass? The context for this request is captured by https://issues.apache.org/jira/browse/ARTEMIS-2261. In EnMasse's case, we programmatically control the Broker using Management over AMQP. We currently rely on AMQP's dynamic node feature to create the reply-to queues. Management responses are currently being lost when the Broker is full (global-max-size exceeded) because messages on the dynamically created nodes are subjected to paging which fails when the Broker is full (`[errorType=ADDRESS_FULL message=AMQ229102: Address "54111434-5686-4dbb-8a94-dd0182dbe7eb" is full.]`) Switching to non-dynamically created response queue named named in such a way to be excluded from the store (`org.apache.activemq.artemis.core.paging.impl.PagingManagerImpl#getPageStore`) is possible but the life cycling is tricky. We have many applications collaborating in the management of the Broker and each currently needs a separate response queue in order to avoid cross-talk. Lifecycling of these response queues ourselves is tricky. You need to consider cases of abnormal shutdown etc. If this enhancement existed, we could share a single static management response queue amongst all the applications. Correlation of requests and responses would avoid the cross-talk between applications or application instances.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
