[
https://issues.redhat.com/browse/AG-153?page=com.atlassian.jira.plugin.sy...
]
Luis Barreiro commented on AG-153:
----------------------------------
Thanks for the report [~whitingjr]
More info is needed in order to understand this issue. At least a thread dump including
the Agroal thread(s) and would be very nice if you could provide pool statistics as well.
With the info provided, is just not clear if there are connections on the pool or not, and
if they are, what state they are in.
The configuration of the pool is required too. It's wise to run with a non-zero value
of `acquisitionTimeout`.
Leak detection is also advisable, even though Agroal does not remove leaking connections
automatically,
Application blocked getting Connection from shared handler cache.
-----------------------------------------------------------------
Key: AG-153
URL:
https://issues.redhat.com/browse/AG-153
Project: Agroal
Issue Type: Bug
Components: pool
Affects Versions: 1.8
Reporter: Jeremy Whiting
Assignee: Luis Barreiro
Priority: Major
Attachments: jstack-tree.txt, summary-of-getConnection-method-calls.txt
I am inspecting an application that stopped nearly all processing.
A jstack dump reveals one of the thread pools (40 threads) has all threads blocked
waiting for a database Connection. See the
"summary-of-getConnection-method-calls.txt" file.
-There are no other threads that already have a connection leased out.-
--
This message was sent by Atlassian Jira
(v7.13.8#713008)