[
https://issues.apache.org/jira/browse/CXF-7414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16053751#comment-16053751
]
Christian Schneider commented on CXF-7414:
------------------------------------------
I also just tried to switch to the request/reply greetMe Method and get this
log:
https://apaste.info/f8dy
The interesting part here is:
java.lang.IllegalStateException: s=COMPLETING i=false a=NOT_ASYNC
at
org.eclipse.jetty.server.HttpChannelState.dispatch(HttpChannelState.java:480)
at
org.eclipse.jetty.server.AsyncContextState.dispatch(AsyncContextState.java:121)
at
org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation.redispatch(Servlet3ContinuationProvider.java:137)
at
org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation.resume(Servlet3ContinuationProvider.java:143)
> ws-rm Messages get lost in case of multi threaded calls and delays
> ------------------------------------------------------------------
>
> Key: CXF-7414
> URL: https://issues.apache.org/jira/browse/CXF-7414
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Affects Versions: 3.1.11
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Fix For: 3.2.0
>
>
> I added a new systest to show the isse:
> org.apache.cxf.systest.ws.rm.DeliveryAssuranceOnewayTest.testOnewayAtLeastOnceInOrderDelay()
> in branch
> https://github.com/cschneider/cxf/tree/inorderdelaytest2
> The test sets up an ws-rm service with at least once and inorder policies.
> Then 4 one way calls are sent to the service with a short delay so it can be
> assumed they trigger the cxf client in order. One of these calls is then
> delayed just before sending out to the server.
> For one of the calls we get an 404 error. Together with a
> java.lang.IllegalStateException: AsyncContext completed and/or Request
> lifecycle recycled .
> See
> https://apaste.info/l9YD
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
