[
https://issues.apache.org/jira/browse/QPID-6825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16423658#comment-16423658
]
Keith Wall commented on QPID-6825:
----------------------------------
I think my original analysis was flawed. I was under the impression that when
a port reached its maximum connections, it would still allocate a network
buffer only then to decide the port was full and needed to be closed. I see
this is not the case. I think the code's current behaviour, accepting the
socket then closing it after logging a PRT-1005 is reasonable. Marking invalid.
> AmqPorts should stop performing a TCP accept once the port has reached
> maximum concurrent connections
> -----------------------------------------------------------------------------------------------------
>
> Key: QPID-6825
> URL: https://issues.apache.org/jira/browse/QPID-6825
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
> Reporter: Keith Wall
> Priority: Major
>
> The Java Broker's AmqPort model object has the concept of maximum number of
> concurrent connections, however, this check is enforce only after the socket
> accept has been performed. This means that system resources are already
> consumed. The check should be changed so that before the port accepts a
> connection, it checks first to ensure that the port has capacity for the new
> connection.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
