You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Tomas Vavricka (Jira)" <ji...@apache.org> on 2022/11/11 12:24:00 UTC

[jira] [Closed] (QPID-8573) [Broker-J] Logging enhancement of Sole Connection Enforcement Policy events

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

Tomas Vavricka closed QPID-8573.
--------------------------------

> [Broker-J] Logging enhancement of Sole Connection Enforcement Policy events
> ---------------------------------------------------------------------------
>
>                 Key: QPID-8573
>                 URL: https://issues.apache.org/jira/browse/QPID-8573
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Broker-J
>            Reporter: Marek Laca
>            Priority: Minor
>              Labels: Broker, Connection, Java, Logging
>             Fix For: qpid-java-broker-9.0.0
>
>
> When a connection is rejected or dropped due to Sole Connection Enforcement Policy there is not any specific log message in the broker's log file that is informing us about the reason of the connection close.
> We should see a message/event in the log file that clearly states that the connection is closed due to Sole Connection Enforcement Policy.
> The message could be logged as the resource limit message 'RL-1002 : Rejected' when the new connection is closed, or it could be logged as the  'RL-1003 : INFO' when the new connection is closing the previous connection.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org