[
https://issues.apache.org/jira/browse/QPID-6816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14996346#comment-14996346
]
Rob Godfrey commented on QPID-6816:
-----------------------------------
So, I'm not really fond of this change... sure currently there is no other
reason for the port to reject the connection - but there is no reason to expect
that that will always be the case (the code in MVPEFactory can't know this)
If anything I'd move the rejection message into the canAceptNewConnection
method on the port, and then add the connection limit into the message as well.
> [Java Broker] Add warning when a port reaches its maximum connection count
> --------------------------------------------------------------------------
>
> Key: QPID-6816
> URL: https://issues.apache.org/jira/browse/QPID-6816
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Rob Godfrey
> Assignee: Keith Wall
> Priority: Minor
> Fix For: qpid-java-6.0
>
>
> QPID-6165 introduced the ability to limit the number of connections which can
> be open on a server side port, and warns when the limit is near to being
> breached - however when the limit has been reached no further warning is
> given... and the connections that are rejected do not have information as to
> why they were rejected making it potentially difficult to work out from the
> log message as to why they have been rejected.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
