[jira] Updated: (AMQ-2643) Closing a PooledConnection does not seem to return associated sessions to the SessionPool

["Dejan Bosanac (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMQ-2643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dejan Bosanac updated AMQ-2643:
-------------------------------

    Fix Version/s:     (was: 5.4.2)
                   5.5.0

> Closing a PooledConnection does not seem to return associated sessions to the SessionPool
> -----------------------------------------------------------------------------------------
>
>                 Key: AMQ-2643
>                 URL: https://issues.apache.org/jira/browse/AMQ-2643
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.2.0
>            Reporter: Henrik Olsson
>             Fix For: 5.5.0
>
>
> Reading the documentation at http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Connection.html#close() one would assume the associated session(s) would be closed/returned to the SessionPool when closing a connection: "There is no need to close the sessions, producers, and consumers of a closed connection."
> But it seems if you don't also explicitly call close() on the session you will run out of Session objects in the SessionPool. 
> Looking at http://www.google.com/codesearch/p?hl=en#coOE0tRomSs/trunk/activemq-core/src/main/java/org/apache/activemq/pool/PooledConnection.java&d=9&l=69 trunk seems to have the same behaviour.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.