[
https://issues.apache.org/jira/browse/QPID-8573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17496068#comment-17496068
]
ASF subversion and git services commented on QPID-8573:
-------------------------------------------------------
Commit d7fc06b67ff8e417e228e81932fe9960a304cf3b in qpid-broker-j's branch
refs/heads/main from Marek Laca
[ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=d7fc06b ]
QPID-8573: [Broker-J] Logging enhancement of Sole Connection Enforcement Policy
events
This closes #114
> [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
>
> 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.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
