[
https://issues.apache.org/jira/browse/QPIDJMS-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16718922#comment-16718922
]
Robbie Gemmell commented on QPIDJMS-438:
----------------------------------------
Inspecting things does suggest the sessions aren't fully cleaned up given a
remote closure.
Can you however enable protocol trace logging to show the remote session
closures? I don't recall the sessions being closed from (potentially faulty)
recollection of past discussion on this behaviour, only the producers. Its
possible the behaviour has changed. Or are you closing your producers after
each send and actually leaving the sessions 'unused'?
> 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
> Attachments: 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]
