[jboss-jira] [JBoss JIRA] (AG-69) Pool-less mode

[Jesper Pedersen (JIRA)]

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

Jesper Pedersen commented on AG-69:
-----------------------------------

It is more for scenarios where services are kept warm in order to lower their startup penalty. Think 400 warm services against a data source that only supports 100 connections. Of course 300 will run into the blocking timeout issue once activated, but that is another problem.

> Pool-less mode
> --------------
>
>                 Key: AG-69
>                 URL: https://issues.jboss.org/browse/AG-69
>             Project: Agroal
>          Issue Type: Feature Request
>          Components: pool
>            Reporter: Jesper Pedersen
>            Assignee: Luis Barreiro
>
> In scenarios where multiple pools access the same data source instance you may end up in a situation where the combined number of max-pool-size is greater than the maximum number of connections in the data source.
> Introduce a pool-less mode, where the underlying connection is closed upon return to the pool if the pool size is greater than min-pool-size.
> This will allow you to configure Agroal to 
> {{.mode("pool-less").minSize(0).maxSize(1)}}
> that only use 1 connection that is returned upon close. This is especially useful for service-mesh scenarios where each service is short-lived, and process one transaction.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)