[ https://issues.apache.org/jira/browse/CXF-7774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16531077#comment-16531077 ]
Freeman Fang edited comment on CXF-7774 at 7/3/18 9:22 AM: ----------------------------------------------------------- Yes, at least it's the Activemq way, thought not sure about IBM implementation. Btw, the fix for CXF-7768 also closes the JMS MessageConsumer which get registered to the replyDestination, previously MessageConsumer can hold replyDestination to be closed when close the connection. Anyway, it may worth of trying the latest CXF snapshot with your testcase was (Author: ffang): Yes, at least it's the Activemq way, thought not sure IBM implementation. Btw, the fix for CXF-7768 also closes the JMS MessageConsumer which get registered to the replyDestination, previously MessageConsumer can hold replyDestination to be closed when close the connection. Anyway, if may worth of trying the latest CXF snapshot with your testcase > 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)