[
https://issues.redhat.com/browse/JBJCA-1399?page=com.atlassian.jira.plugi...
]
Flavia Rainone commented on JBJCA-1399:
---------------------------------------
As a result, the pool could end up empty. Every connection that is returned to the pool is
destroyed, since the pool appears to be bigger than maximum capacity. At some point, the
pool will point to a big size (such as 10), and have zero connections inside of it. Due to
this consequence, I'm raising the priority of this issue.
Race condition between JCA Capacity Filler and new connections
creation
-----------------------------------------------------------------------
Key: JBJCA-1399
URL:
https://issues.redhat.com/browse/JBJCA-1399
Project: IronJacamar
Issue Type: Feature Request
Components: Core
Reporter: Flavia Rainone
Assignee: Flavia Rainone
Priority: Major
JCA Capacity Filler is unaware of connections being created in a separate thread, which
can lead to unexpected behavior, such as the pool being filled with too many connections.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)