[
https://issues.redhat.com/browse/AG-154?page=com.atlassian.jira.plugin.sy...
]
Wojciech Kopciewicz commented on AG-154:
----------------------------------------
Hi [~lbarreiro],
Yes, we are confident the connections are leaking as after the problem occurred further
attempts to acquire a connection failed with acquisition timeout. Only service restart
allowed us to recover from this state. It looks like those connections are never returned
to the pool.
We have also enabled leak detection and max lifetime for the connections but it changed
nothing.
Connection leak when DB connection closed during transaction
rollback
---------------------------------------------------------------------
Key: AG-154
URL:
https://issues.redhat.com/browse/AG-154
Project: Agroal
Issue Type: Bug
Components: narayana, pool
Affects Versions: 1.9
Reporter: Wojciech Kopciewicz
Assignee: Luis Barreiro
Priority: Major
We are using Quarkus 1.9.2 with Hibernate and Agroal to access PostgreSQL DB.
It looks like Agroal is leaking connections when connection is closed (somewhere) on the
server side during transaction rollback.
The following log was observed:
Error trying to transactionRollback local transaction: This connection has been closed.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)