[jboss-jira] [JBoss JIRA] (JBJCA-722) Too eager shutdown of pools through idle timeout

[Alexander Vinnik (JIRA)]

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

Alexander Vinnik commented on JBJCA-722:
----------------------------------------

We are experiencing this problem in JBoss 6.1. The workaround is not working for us: The pool is not closed now, but when a 3rd party application is trying to access the idle connection, it fails. Is it possible to make a patch addressing this problem in 6.1?
                
> Too eager shutdown of pools through idle timeout
> ------------------------------------------------
>
>                 Key: JBJCA-722
>                 URL: https://issues.jboss.org/browse/JBJCA-722
>             Project: IronJacamar
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0.6.Final, 1.1.0.Alpha4
>            Reporter: Jesper Pedersen
>            Assignee: Jesper Pedersen
>            Priority: Critical
>             Fix For: 1.0.7.Final, 1.1.0.Alpha5
>
>
> In order to cleanup pools with a sparse Subject/CRI coverage we shutdown the pool if it is empty.
> However, there is no reason to do so if it is the only pool available. Furthermore we should always try and allocate a connection in order to kick the allocation mechanism into effect.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira