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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.7.11
• Fix Version/s: 3.0.13, 3.1.11, 3.2.0
• Component/s: WS-* Components
• Estimated Complexity: Unknown
• Assignee: Christian Schneider
• Reporter: Philipp Hahn
• Created: 21/May/14 07:08
• Updated: 19/Apr/17 14:23
• Resolved: 15/Mar/17 13:33

Description

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)

 javax.jms.Message replyMessage = jmsTemplate.receiveSelected(replyToDestination, messageSelector);
                    if (replyMessage == null) {
                        throw new RuntimeException("Timeout receiving message with correlationId " + correlationId);
                    } else {
                        doReplyMessage(exchange, replyMessage);
                    }

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!

Issue Links

• contains: CXF-7079 JMSConduit – is not removing entry from corelationMap if relpyMessage is null (timeout)