[
https://issues.apache.org/jira/browse/CXF-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-3271.
------------------------------
Resolution: Fixed
Fix Version/s: 2.3.3
Assignee: Daniel Kulp
Patch applied.
I modified the patch so that if continuations are available, it will use them
instead of blocking on the thread.
One optimization that COULD be done is instead of wakeing up ALL the waiting
continuations, we could just fine the one for the next in the sequence (and
duplicates) and wake them up.
Also, the Jetty continuations don't work with one-ways. I'll need to figure
out what to do about that. Not sure it really matters for most cases though.
The fallback to the wait() method works fine.
> 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
> Assignee: Daniel Kulp
> Priority: Critical
> Fix For: 2.3.3
>
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
