You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Richard McLaren (JIRA)" <ji...@apache.org> on 2018/07/02 14:59:00 UTC
[jira] [Comment Edited] (CXF-7774) JMS Reply Queue handles leaking
on IBM MQ.
[ https://issues.apache.org/jira/browse/CXF-7774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16530025#comment-16530025 ]
Richard McLaren edited comment on CXF-7774 at 7/2/18 2:58 PM:
--------------------------------------------------------------
I have looked at other versions (3.1.x and 3.2.x) and while
jmsConfig.resetCachedReplyDestination()
has been added there is still no attempt to close the underlying queue.
was (Author: ricky.mclaren):
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 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)