[Red Hat JIRA] (AG-154) Connection leak when DB connection closed during transaction rollback
by Wojciech Kopciewicz (Jira)
[ https://issues.redhat.com/browse/AG-154?page=com.atlassian.jira.plugin.sy... ]
Wojciech Kopciewicz commented on AG-154:
----------------------------------------
I changed the priority of the issue as it results in application not being able to connect to DB.
> 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: Critical
>
> 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)
5 years, 2 months
[Red Hat JIRA] (AG-154) Connection leak when DB connection closed during transaction rollback
by Wojciech Kopciewicz (Jira)
[ https://issues.redhat.com/browse/AG-154?page=com.atlassian.jira.plugin.sy... ]
Wojciech Kopciewicz updated AG-154:
-----------------------------------
Priority: Critical (was: Major)
> 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: Critical
>
> 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)
5 years, 2 months
[Red Hat JIRA] (WFLY-14348) Unhelpful failure message 'WFLYJCA0032: Unable to start the ds because it generated more than one cf'
by Bartosz Baranowski (Jira)
[ https://issues.redhat.com/browse/WFLY-14348?page=com.atlassian.jira.plugi... ]
Bartosz Baranowski commented on WFLY-14348:
-------------------------------------------
[~brian.stansberry] It would be good if you could recreate your tinkering efforts. I can change message to provide reasonable information, but I wont be able to provide any hints as to what went wrong. Im going to play a bit with it, maybe I will be able to make it fail, though with:
{quote}[standalone@localhost:9990 /] module add --name=org.postgresql --resources=/home/baranowb/Downloads/postgresql-42.2.18.jar --dependencies=javax.api,javax.transaction.api
[standalone@localhost:9990 /] /subsystem=datasources/jdbc-driver=postgres:add(driver-name="postgres",driver-module-name="org.postgresql",driver-class-name=org.postgresql.Driver)
Unknown macro: \{"outcome" => "success"}
[standalone@localhost:9990 /] data-source add --jndi-name=java:jboss/datasources/DemoDS --name=DemoDS --connection-url=jdbc:postgresql://localhost:5432/Demo --driver-name=postgres --user-name=postgres --password=admin
[standalone@localhost:9990 /]
{quote}
just does not fail.
> Unhelpful failure message 'WFLYJCA0032: Unable to start the ds because it generated more than one cf'
> -----------------------------------------------------------------------------------------------------
>
> Key: WFLY-14348
> URL: https://issues.redhat.com/browse/WFLY-14348
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Reporter: Brian Stansberry
> Assignee: Bartosz Baranowski
> Priority: Major
>
> Playing with driver and DS installation I ended up with this in the server log:
> {code}
> 10:54:11,424 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "datasources"),
> ("data-source" => "Postgres")
> ]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.data-source.Postgres" => "WFLYJCA0033: Error during the deployment of Postgres
> Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf"}}
> {code}
> That was quite cryptic.
> 1) The 'ds' and 'cf' abbreviations should be replaced with full words. To me this is the minimum resolution of this issue.
> 2) If it is possible to make a reasonably likely guess at what would lead to this situation and provide that info in the message, that would be nice.
> Context:
> I tried deploying a JDBC driver and then adding a datasource using a CLI command:
> {code}
> data-source add --name=Postgres --driver-name=postgresql-42.2.18.jar --jndi-name=java:jboss/datasources/Postgres
> {code}
> The 3 params are the required ones. I wasn't surprised that wasn't sufficient and I understand that what's required beyond that can vary from driver to driver. But those are the required ones, so users experimenting with WildFly are liable to do what I did. (If any other params *should be* required, someone please file a separate issue.)
> Adding a connection-url param allowed the command to work. If that param shouldn't be required, but not providing it is a likely cause of this problem, perhaps the WFLYJCA0032 message should note that as a hint?
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months