[
https://issues.apache.org/jira/browse/AMQ-8975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573879#comment-17573879
]
Lucas Tétreault commented on AMQ-8975:
--------------------------------------
I think this would address this issue as well:
https://issues.apache.org/jira/browse/AMQ-8255
[~mattrpav] have you already started on this?
> Add config option to send Max Connections exceeded exception to client
> ----------------------------------------------------------------------
>
> Key: AMQ-8975
> URL: https://issues.apache.org/jira/browse/AMQ-8975
> Project: ActiveMQ
> Issue Type: New Feature
> Reporter: Matt Pavlovich
> Assignee: Matt Pavlovich
> Priority: Major
>
> Currently, when max connections is exceeded, the client side gets closed
> without receiving a well-formed message. This change would improve
> client-side visibility to the max connections exceeded scenario.
> Implementation notes:
> 1. Add config flag to enable (default: false to keep current behavior)
> 2. Send down a ConnectionError command to client
> 3. Add unit tests
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
