-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
7.2.0.CD14
-
None
-
None
-
Regression
-
-
-
-
-
-
-
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@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.
- clones
-
WFLY-10531 Wildfly leaks ActiveMQ connections
- Closed
- duplicates
-
JBEAP-15517 [GSS](7.2.z) Leaking connections when multiple EJBs are injecting a JMSContext
- Closed
- is cloned by
-
JBEAP-15566 [GSS](7.1.z) Wildfly leaks ActiveMQ connections - regression caused by JBEAP-7503
- Closed
- relates to
-
JBEAP-7503 [GSS](7.1.z) JBJCA-1358 - Container is not cleaning up container-managed JMSContext
- Closed