[
https://issues.apache.org/jira/browse/AMQ-2643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-2643.
-------------------------------
Resolution: Fixed
Fix Version/s: 5.6.0
Assignee: Timothy Bish
Fix applied in trunk.
> 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
> Assignee: Timothy Bish
> Fix For: 5.6.0
>
> Attachments: PooledSessionExhaustionTest.java, SimpleTest.java
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
