[jboss-jira] [JBoss JIRA] (JBJCA-1005) SemaphoreArrayListManagedConnectionPool should FIFO

[None None (JIRA)]

    [ https://issues.jboss.org/browse/JBJCA-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13043527#comment-13043527 ] 

None None commented on JBJCA-1005:
----------------------------------

Hi,

could someone explain to me why this change has been made, please? I see a major problem with this because idle connections are hardly closed.

We updated from JBoss 4 to Wildfly 8.2. JBoss 4 had a LIFO strategy and Wildfly has a FIFO strategy now. Our db pool size is configured to work well with a high server load. On low to medium load only a small amount of db connections are needed. Unfortunately db pool connections are now used in a round robin manner. This means that very few connections can be closed due to reaching the idle time limit because they are used regularly.

Is there a way to get back the old behavior? Are there any different connection pool managers that utilize a LIFO strategy?

> SemaphoreArrayListManagedConnectionPool should FIFO
> ---------------------------------------------------
>
>                 Key: JBJCA-1005
>                 URL: https://issues.jboss.org/browse/JBJCA-1005
>             Project: IronJacamar
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0.15.Final, 1.1.0.Beta4
>            Reporter: Jesper Pedersen
>            Assignee: Jesper Pedersen
>            Priority: Critical
>             Fix For: 1.0.16.Final, 1.1.0.Beta5
>
>
> Currently behaving in FILO manner



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)