[
https://issues.apache.org/jira/browse/CXF-5539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-5539.
------------------------------
Resolution: Fixed
Fix Version/s: 2.7.12
2.6.15
Assignee: Daniel Kulp
> 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
> Assignee: Daniel Kulp
> Fix For: 2.6.15, 2.7.12
>
>
> 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.2#6252)
