You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Tomas Vanhala (JIRA)" <ji...@apache.org> on 2018/11/26 14:50:00 UTC

[jira] [Created] (CXF-7909) WS-Addressing allowDuplicates=false rejects legitimate retransmissions

Tomas Vanhala created CXF-7909:
----------------------------------

             Summary: WS-Addressing allowDuplicates=false rejects legitimate retransmissions
                 Key: CXF-7909
                 URL: https://issues.apache.org/jira/browse/CXF-7909
             Project: CXF
          Issue Type: Improvement
          Components: WS-* Components
            Reporter: Tomas Vanhala


According to the WS-Addressing specification ([https://www.w3.org/Submission/ws-addressing]):

"No two messages with a distinct application intent may share a [message id] property. A message MAY be retransmitted for any purpose including communications failure and MAY use the same [message id] property."

Our application currently has the setting:

 
{noformat}
<bean id="mapAggregator" class="org.apache.cxf.ws.addressing.MAPAggregator">
  <property name="allowDuplicates" value="false"/>
</bean>
{noformat}
We encountered a situation, where our application was misconfigured (could not read trust store used for SAML validation) for a short period of time and rejected incoming messages.

Once the misconfiguration was fixed, retransmissions of these same messages were rejected due to them being detected as duplicates. This was not a desired outcome.

Now we are thinking about how to avoid rejecting legitimate retransmissions, while retaining the benefit of using the WS-Addressing messageid cache.

Could the caching implementation in CXF be enhanced to offer further configurability? Could the behavour be dependent on whether the original message was processed successfully (SOAP response) or whether the message was rejected (SOAP fault)?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)