[
https://issues.apache.org/jira/browse/QPID-8573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17496067#comment-17496067
]
ASF GitHub Bot commented on QPID-8573:
--------------------------------------
vavrtom merged pull request #114:
URL: https://github.com/apache/qpid-broker-j/pull/114
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
> [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]
