[jboss-jira] [JBoss JIRA] (JGRP-1462) TCPConnectionMap: move socket establishment out of common path

[Bela Ban (JIRA)]

     [ https://issues.jboss.org/browse/JGRP-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bela Ban resolved JGRP-1462.
----------------------------

    Resolution: Done

    
> TCPConnectionMap: move socket establishment out of common path
> --------------------------------------------------------------
>
>                 Key: JGRP-1462
>                 URL: https://issues.jboss.org/browse/JGRP-1462
>             Project: JGroups
>          Issue Type: Enhancement
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>             Fix For: 3.0.10, 3.1
>
>
> TCPConnectionMap$Mapper.getConnection() acquires a lock and returns the an existing connection, or creates a new one if needed. The problem is that - while we try to establish a new connection - *existing* connections will have to wait before being returned until connection establishment has completed (or failed).
> For instance, if we have valid connections to members B, C and D, and try to establish a connection to (failed) member E, all threads will try to send data to A, B and C will be blocked until they can acquire the lock !
> SOLUTION: move socket creation under a different lock.
> {Suggested by S. Simeonoff)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira