[jboss-jira] [JBoss JIRA] (WFLY-10531) Wildfly leaks ActiveMQ connections

[Jiri Ondrusek (Jira)]

    [ https://issues.jboss.org/browse/WFLY-10531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13642583#comment-13642583 ] 

Jiri Ondrusek commented on WFLY-10531:
--------------------------------------

Hi [~jwgmeligmeyling] I'm still working on a test, here is a simple rewritten test from reproducer based on [~gunterze] - https://github.com/JiriOndrusek/wildfly/commit/c928f11f27cac46a18c7c1a9e7e2832a92546e97
But it s not optimal, I would like to rewrite it (as failuret will exhaust server) and I would like to add test for original fix as well. Hopefully I'll manage it tomorrow.

> Wildfly leaks ActiveMQ connections
> ----------------------------------
>
>                 Key: WFLY-10531
>                 URL: https://issues.jboss.org/browse/WFLY-10531
>             Project: WildFly
>          Issue Type: Bug
>    Affects Versions: 13.0.0.Final
>         Environment: openjdk 8 / openjdk 9, Linux
>            Reporter: Marcel Šebek
>            Assignee: Jeff Mesnil
>            Priority: Major
>         Attachments: WFLY-10531-ear-1.0.ear, WFLY10531.zip
>
>
> After upgrading our application from wildfly 12 to 13, the app started to crash after a while (hours, days, depending on circumstances). It crashes on
> IJ000453: Unable to get managed connection for java:/JmsXA
> and other errors (it simply cannot perform all the jobs it contains). I found that when shutting down the server which has been running for a while, I can see a bunch of these messages in the log:
> WARN  [org.jboss.jca.core.connectionmanager.pool.strategy.PoolByCri] (ServerService Thread Pool -- 117) [:::] IJ000615: Destroying active connection in pool: ActiveMQConnectionDefinition (org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection at 2f37f69)
> Bascially, the longer the server was running, more of these messages are shown. I cannot find a way how to reproduce the issue. When the server runs for short time but with some load, no connection is leaked (or just one, rarely). On the other side, it leaks connections even without any particularly high load (just a few requests and @Schedule jobs) when running for longer time.
> It may also be a bug in our application, which just happen to have more serious impact with the new wildfly version.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)