[
https://issues.apache.org/jira/browse/CXF-7774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16531053#comment-16531053
]
Richard McLaren commented on CXF-7774:
--------------------------------------
I have had a look at the fix for CXF-7768 and if you are referring to the
jmsListener.shutdown then this is not applicable since we never set up a
jmsListener.
This is because we do not specify a message selector. We use IBM style where
correlation id is not set and the receive is based on the message id instead.
Are you expecting that closing the connection will automatically close the
staticReplyDestination?
> 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)
