[jira] [Commented] (CXF-7774) JMS Reply Queue handles leaking on IBM MQ.

["Richard McLaren (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CXF-7774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16530025#comment-16530025 ] 

Richard McLaren commented on CXF-7774:
--------------------------------------

I have looked at other versions (3.1.x and 3.2.x) and while setting the 

staticReplyDestination to null has been extracted to a synchronised method there is still no attempt to close it.

> 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 IBMQueue 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)