[
https://issues.apache.org/jira/browse/QPIDJMS-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16719242#comment-16719242
]
ASF subversion and git services commented on QPIDJMS-438:
---------------------------------------------------------
Commit 26ec26863410ddf11097054987764b93567a4663 in qpid-jms's branch
refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=26ec268 ]
QPIDJMS-438 Ensure that closed sessions are removed from tracking
When a session is remotely closed it can be left in the Connection
tracking map which can lead to large leaks of remotely closed sessions
over time. Ensure it is removed on shutdown calls.
> Remotely closed session are not removed from the connection
> -----------------------------------------------------------
>
> Key: QPIDJMS-438
> URL: https://issues.apache.org/jira/browse/QPIDJMS-438
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Affects Versions: 0.39.0
> Reporter: David De Franco
> Priority: Major
> Fix For: 0.40.0
>
> Attachments: amqp.log, out-of-memory1.PNG, out-of-memory2.PNG
>
>
> We use Qpid JMS to connect to the Azure service bus.
> In our applications we cache the connections in a pool and cache a session
> for each connection for sending messages.
> When Azure believes the connection is idle for 5 minutes it is remotely
> closed. Resulting in closing the cached session in the application. The
> application responds by replacing the cached session with a newly created
> session.
> The problem here is that the closed sessions are not removed from the
> connection. Eventually resulting in an OutOfMemoryError.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
