You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Jean-Baptiste Onofré (Jira)" <ji...@apache.org> on 2023/06/19 13:08:00 UTC

[jira] [Updated] (AMQ-8975) Add config option to send Max Connections exceeded exception to client

     [ https://issues.apache.org/jira/browse/AMQ-8975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré updated AMQ-8975:
--------------------------------------
    Fix Version/s: 5.19.0
                   5.18.3
                       (was: 5.18.2)

> 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
>             Fix For: 5.19.0, 5.18.3
>
>
> 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)