Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Tue, 4 Feb 2014 16:06:11 +0000 (UTC)
From: "Andrei Shakirin (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.12693128.1391529947494.34347.1391529971157@arcas>
In-Reply-To: <JIRA.12693128.1391529947494@arcas>
References: <JIRA.12693128.1391529947494@arcas>
Subject: [jira] [Created] (CXF-5539) WS-A with JMS for OneWay: empty
 response is sent to client queue
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Andrei Shakirin created CXF-5539:
------------------------------------

             Summary: WS-A with JMS for OneWay: empty response is sent to client queue
                 Key: CXF-5539
                 URL: https://issues.apache.org/jira/browse/CXF-5539
             Project: CXF
          Issue Type: Bug
            Reporter: Andrei Shakirin


I am struggling with one effect appearing in case of using WS-A, OneWay message pattern and JMS transport.

The problem is that service tries to send empty response to the client JMS queue.
Empty message is sent by OneWayProcessorInterceptor. Without WS-A it is not a problem, because JMSDestination.sendExchange() checks if exchange is oneway and if yes, returns immediately.
But if WS-A is active, MAPAggregator creates decoupled destination with JMSConduit as a sender. JMSConduit.sendExchange() doesn't has any checks for oneway and it tries to send empty response to ReplyTo address. If ReplyTo is anonymous or none, empty response is sent using http conduit to http://www.w3.org/2005/08/addressing/none address.
The question does the rebaseResponse and decoupled destination make sense for oneway at all? Client doesn't expect any response for JMS in this case (for HTTP 202). 


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)