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

Posted to issues@activemq.apache.org by "Justin Bertram (Jira)" <ji...@apache.org> on 2022/02/07 04:27:00 UTC

[jira] [Commented] (ARTEMIS-3672) DisconnectReason needs to be expandable

    [ https://issues.apache.org/jira/browse/ARTEMIS-3672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17487862#comment-17487862 ] 

Justin Bertram commented on ARTEMIS-3672:
-----------------------------------------

Can you outline your use-case? Are you, for example, using a remoting interceptor to change the {{DisconnectMessage}} implementation which is being sent back to clients?

> DisconnectReason needs to be expandable
> ---------------------------------------
>
>                 Key: ARTEMIS-3672
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3672
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: Broker
>            Reporter: Dmitriy Nozdrya
>            Priority: Major
>
> There are times when a client may be disconnected for a specific reason that is not included in DisconnectReason enum. It is currently not possible to specify a custom disconnect reason. It would be convenient to pass a custom reason to DisconnectReason.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)