[jboss-jira] [JBoss JIRA] (JBJCA-1358) Container is not cleaning up container-managed JMSContext

[Jiri Ondrusek (JIRA)]

     [ https://issues.jboss.org/browse/JBJCA-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jiri Ondrusek moved JBEAP-13747 to JBJCA-1358:
----------------------------------------------

              Project: IronJacamar  (was: JBoss Enterprise Application Platform)
                  Key: JBJCA-1358  (was: JBEAP-13747)
             Workflow: classic default workflow  (was: CDW with loose statuses v1)
          Component/s:     (was: EE)
                           (was: EJB)
                           (was: JMS)
    Affects Version/s: 	 WildFly/IronJacamar 1.4.3.Final
                           (was: 7.0.0.GA)


> Container is not cleaning up container-managed JMSContext
> ---------------------------------------------------------
>
>                 Key: JBJCA-1358
>                 URL: https://issues.jboss.org/browse/JBJCA-1358
>             Project: IronJacamar
>          Issue Type: Bug
>    Affects Versions: 	 WildFly/IronJacamar 1.4.3.Final
>         Environment: JBoss-EAP-7.0.0
> JDK 1.8
>            Reporter: Jiri Ondrusek
>            Assignee: Jiri Ondrusek
>
> 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



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)