Container is not cleaning up container-managed JMSContext --------------------------------------------------------- Key: WFLY-9501 URL: https://issues.jboss.org/browse/WFLY-9501 Project: WildFly Issue Type: Bug Components: EE, EJB, JMS Affects Versions: 12.0.0.Beta1 Environment: JBoss-EAP-7.0.0 JDK 1.8 Reporter: Jiri Ondrusek Assignee: Jiri Ondrusek Fix For: 13.0.0.Beta1 The container is not cleaning up container managed JMSContext, causing a connection leak. The JMS 2.0 API doc[1] states the following : <quote> Applications running in the Java EE web and EJB containers may alternatively inject a JMSContext into their application using the @Inject annotation. A JMSContext that is created in this way is described as being container-managed. A container-managed JMSContext will be closed automatically by the container. </quote> However the JCA's CacheConnectionManager (CCM) complains a connection leak if the application didn't explicitly close the JMSContext, which is not required for container managed JMSContext. [1] http://docs.oracle.com/javaee/7/api/javax/jms/JMSContext.html