2b5d8f3b80
- Split protocols into individual chapters - Reorganize summary to flow more logically - Fill in missing parameters in configuration index - Normalize spaces for ordered and unordered lists - Re-wrap lots of text for readability - Fix incorrect XML snippets - Normalize table formatting - Improve internal links with anchors - Update content to reflect new address model - Resized architecture images to avoid excessive white-space - Update some JavaDoc - Update some schema elements - Disambiguate AIO & ASYNCIO where necessary - Use URIs instead of Objects in code examples
1.0 KiB
Resource Limits
Sometimes it's helpful to set particular limits on what certain users can do beyond the normal security settings related to authorization and authentication. For example, limiting how many connections a user can create or how many queues a user can create. This chapter will explain how to configure such limits.
Configuring Limits Via Resource Limit Settings
Here is an example of the XML used to set resource limits:
<resource-limit-settings>
<resource-limit-setting match="myUser">
<max-connections>5</max-connections>
<max-queues>3</max-queues>
</resource-limit-setting>
</resource-limit-settings>
Unlike the match from address-setting, this match does not use
any wild-card syntax. It's a simple 1:1 mapping of the limits to a user.
-
max-connectionsdefines how many connections the matched user can make to the broker. The default is -1 which means there is no limit. -
max-queuesdefines how many queues the matched user can create. The default is -1 which means there is no limit.