Jiri Ondrusek created WFLY-11102:
------------------------------------
Summary: Wildfly leaks ActiveMQ connections
Key: WFLY-11102
URL:
https://issues.jboss.org/browse/WFLY-11102
Project: WildFly
Issue Type: Bug
Affects Versions: 13.0.0.Final
Environment: openjdk 8 / openjdk 9, Linux
Reporter: Jiri Ondrusek
Assignee: Jeff Mesnil
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.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)