[
https://issues.apache.org/jira/browse/CXF-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985295#action_12985295
]
Dennis Sosnoski edited comment on CXF-3271 at 1/23/11 6:28 AM:
---------------------------------------------------------------
Here's an Eclipse-generated patch to get InOrder working. It's not necessarily
ideal, in that it still has a thread associated with each message waiting for
its turn to be delivered (potentially including duplicate messages), but at
least it gets the basics working.
Note that this includes the test code and files provided earlier to demonstrate
the problem, so applying the patch is all that needs to be done.
was (Author: dsosnoski):
Here's an Eclipse-generated patch to get InOrder working. It's not
necessarily ideal, in that it still has a thread associated with each message
waiting for its turn to be delivered (potentially including duplicate
messages), but at least it gets the basics working.
> WS-RM code does not support InOrder assurances
> ----------------------------------------------
>
> Key: CXF-3271
> URL: https://issues.apache.org/jira/browse/CXF-3271
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Affects Versions: 2.3.2
> Reporter: Dennis Sosnoski
> Priority: Critical
> Attachments: CXF-3271-patch.txt, inorder.zip
>
>
> The WS-RM implementation does not support InOrder assurances. When InOrder is
> used alone (which is effectively the same as combined with AtLeastOnce) or
> with AtMostOnce messages are just delivered in whatever order they arrive.
> When InOrder is combined with ExactlyOnce the code never delivers any
> messages (due to a logic error in
> DestinationSequence.allPredecessorsAcknowledged()). See attached integration
> test and policy documents to demonstrate the issues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
