[
https://issues.redhat.com/browse/AG-153?page=com.atlassian.jira.plugin.sy...
]
Jeremy Whiting commented on AG-153:
-----------------------------------
Thanks for the recommendations [~lbarreiro].
I've investigated further the configuration of the pool. The pool was exhausted. In
this situation I've recommended reducing the number of JVM threads that use
connections.
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)