[jboss-jira] [JBoss JIRA] (JBJCA-1401) Avoid flushing pooled connections when matchManagedConnections returns no match

[Stephen Fikes (Jira)]

    [ https://issues.redhat.com/browse/JBJCA-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13942008#comment-13942008 ] 

Stephen Fikes commented on JBJCA-1401:
--------------------------------------

[~maeste], can you verify if there is a workaround to have pooling when using different credentials with a resource adapter? Would the workaround be to define different connection-definitions for each distinct credential?

> Avoid flushing pooled connections when matchManagedConnections returns no match
> -------------------------------------------------------------------------------
>
>                 Key: JBJCA-1401
>                 URL: https://issues.redhat.com/browse/JBJCA-1401
>             Project: IronJacamar
>          Issue Type: Feature Request
>          Components: Core
>    Affects Versions: 1.4.10
>            Reporter: Stephen Fikes
>            Priority: Major
>
> When no match is returned by the resource adapter implementation of [ManagedConnectionFactory.matchManagedConnections|https://docs.oracle.com/javaee/7/api/javax/resource/spi/ManagedConnectionFactory.html#matchManagedConnections-java.util.Set-javax.security.auth.Subject-javax.resource.spi.ConnectionRequestInfo-], the IronJacamar pool implementation [terminates non-matching connections|https://github.com/ironjacamar/ironjacamar/blob/ironjacamar-1.4.18.Final/core/src/main/java/org/jboss/jca/core/connectionmanager/pool/mcp/SemaphoreConcurrentLinkedDequeManagedConnectionPool.java#L425-L438].
> There may be cases where resource adapters return {{null}} for cases where no connection matches but where the connections in the match set are not invalid though a different connection needs to be created based on the calling context ({{ConnectionRequestInfo}}).
> A mechanism to avoid the termination of non-matching connections is needed to support such cases.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)