[jboss-jira] [JBoss JIRA] (WFLY-3552) Updated implementation of StrictMaxPool

[John O'Hara (JIRA)]

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

John O'Hara updated WFLY-3552:
------------------------------

    Description: To eliminate contention in the EJB StrictMaxPool, can we change the underlying data structure to use ConcurrentLinkedQueue, instead of the LinkedList with synchronization that is in the implementation currently?  (was: To eliminate contention in the EJB StrictMaxPool, we have changed the underlying data structure to use ConcurrentLinkedQueue, instead of the LinkedList with synchronization that is in the implementation currently.)


> Updated implementation of StrictMaxPool
> ---------------------------------------
>
>                 Key: WFLY-3552
>                 URL: https://issues.jboss.org/browse/WFLY-3552
>             Project: WildFly
>          Issue Type: Requirement
>      Security Level: Public(Everyone can see) 
>            Reporter: John O'Hara
>            Assignee: Jason Greene
>
> To eliminate contention in the EJB StrictMaxPool, can we change the underlying data structure to use ConcurrentLinkedQueue, instead of the LinkedList with synchronization that is in the implementation currently?



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)