[jira] [Resolved] (CXF-5754) JMSConduit - temporary queue not beeing closed if relpyMessage is null (timeout)

["Christian Schneider (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CXF-5754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Schneider resolved CXF-5754.
--------------------------------------
    Resolution: Fixed

Thanks for validating the change. I have now back ported to 3.1.x and 3.0.x.

> JMSConduit - temporary queue not beeing closed if relpyMessage is null (timeout)
> --------------------------------------------------------------------------------
>
>                 Key: CXF-5754
>                 URL: https://issues.apache.org/jira/browse/CXF-5754
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>    Affects Versions: 2.7.11
>            Reporter: Philipp Hahn
>            Assignee: Christian Schneider
>             Fix For: 3.2.0, 3.0.13, 3.1.11
>
>         Attachments: eclipse-mem-analyzer.png, fixed-test01.png, memory-leak-due-to-timeouts-4hrs.png, unfixed-test01.png
>
>
> Our implementation:
> CXF 2.7.11
> JMS Queue on TIBCO
> We have the problem, that if a timeout is raised the temporary queue is not been deleted.
> After code review of the JmsConduit class we have seen, that in case of a timeout, cxf is only raises only an RuntimeException (JmsConduit line 256)
> {code}
>  javax.jms.Message replyMessage = jmsTemplate.receiveSelected(replyToDestination, messageSelector);
>                     if (replyMessage == null) {
>                         throw new RuntimeException("Timeout receiving message with correlationId " + correlationId);
>                     } else {
>                         doReplyMessage(exchange, replyMessage);
>                     }
> {code} 
> Is this the problem why the temporary queue is not been closed in case of a timeout? Is there an solution for this problem?
> Thanks!



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)