[Issue] Allow queue-specific configuration to exceed the default max-messages value

[m2-assistant]

This issue is automatically created based on existing pull request: #40110: Allow queue-specific configuration to exceed the default max-messages value

---

Description (*)

Allow queue-specific configuration to exceed the default max-messages value

Currently, when configuring a specific max-messages value in queue_consumer.xml (e.g., 400000), the consumer command still uses the lower global default (e.g., 10000), because the logic applies min($consumer->getMaxMessages(), $maxMessages).

This change updates the behavior so that, if a queue has a specific max-messages configuration, it takes precedence over the default value.

Example:
Configured in queue_consumer.xml: max-messages = 400000

Default value: 10000

Before: the command uses --max-messages=10000

After: the command correctly uses --max-messages=400000

Related Pull Requests

Fixed Issues (if relevant)

1. Fixes magento/magento2#<issue_number>

Manual testing scenarios (*)

Create queue with max message higter default value

Questions or comments

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
• All automated tests passed successfully (all builds are green)

[m2-assistant]

Hi @engcom-Hotel. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Hotel]

Hello @baudeval,

Thanks for the report and contribution!

We have tried to reproduce this issue via making a custom module in the latest development branch i.e. 2.4-develop. The issue seems reproducible to us.

Hence confirming the issue.

Thanks