You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Aki Yoshida (JIRA)" <ji...@apache.org> on 2013/12/11 14:42:29 UTC

[jira] [Resolved] (CXF-5435) WS-RM's retransmission should call conduit.close(message) after successful retransmission

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

Aki Yoshida resolved CXF-5435.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.7.9
                   2.6.12
                   3.0.0-milestone2

> WS-RM's retransmission should call conduit.close(message) after successful retransmission
> -----------------------------------------------------------------------------------------
>
>                 Key: CXF-5435
>                 URL: https://issues.apache.org/jira/browse/CXF-5435
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>    Affects Versions: 2.7.8
>            Reporter: Aki Yoshida
>            Assignee: Aki Yoshida
>             Fix For: 3.0.0-milestone2, 2.6.12, 2.7.9
>
>
> The message retransmission code in WS-RM is currently directly closing the output stream associated associated with the retried message after its successful retransmission.
> As the normal transmission case uses condui't prepare(Message) to start transmission and ends with close(Message), which closes the output stream associated with the retried message. 
> To provide a consistent behavior, the WS-RM's retransmission should also use conduit's close(Message) method to close the output stream. 
> Note that this is not an issue for the normal HTTPConduit as its close(Message) method does not contain any special logic but simply closes the output stream associated with the message.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)