[
https://issues.apache.org/jira/browse/CXF-7774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16533326#comment-16533326
]
Richard McLaren commented on CXF-7774:
--------------------------------------
Apologies, after some more investigation it seems that while the implementation
class MQQueue does have a close() method there is no way to call it via the JMS
interfaces and it should be closed via the connection/session.
Any idea when next 3.2.x version will be published officially?
> JMS Reply Queue handles leaking on IBM MQ.
> ------------------------------------------
>
> Key: CXF-7774
> URL: https://issues.apache.org/jira/browse/CXF-7774
> Project: CXF
> Issue Type: Bug
> Components: JMS
> Affects Versions: 3.1.11
> Reporter: Richard McLaren
> Priority: Major
>
> Using 3.1.11 and JMS we are seeing handles for our Reply Queue are being left
> open.
> This is using a SpringBoot application and IBM MQ client jars.
> The most likely suspect is in JMSConduit the field
> staticReplyDestination is set to null on a JMSException but the existing
> MQQueue is never closed.
> I have tried simulating the problem in IntelliJ by forcing a JMSException
> during the SendExchange.
> Should there be a "ResourceCloser.close(
> staticReplyDestination);" immediately prior to setting
> staticReplyDestination to null?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
