[jira] Commented: (CAMEL-3169) Add continuation synchronize block to avoid the CamelAsync API return earlier then the interceptor chain is suspend

["Martin Krasser (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/activemq/browse/CAMEL-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62188#action_62188 ] 

Martin Krasser commented on CAMEL-3169:
---------------------------------------

Hi Willem,

I had a similar problem in the CamelContinuationServlet in camel-jetty and could solve it without using exclusive locks (i.e. synchronization). 

https://svn.apache.org/repos/asf/camel/trunk/components/camel-jetty/src/main/java/org/apache/camel/component/jetty/CamelContinuationServlet.java

I didn't investigate the CxfConsumer and CXF continuations in all details but I think the solution pattern from camel-jetty is also applicable here. Thoughts?



> Add continuation synchronize block to avoid the CamelAsync API return earlier then the interceptor chain is suspend  
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-3169
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3169
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-cxf
>            Reporter: Willem Jiang
>            Assignee: Willem Jiang
>             Fix For: 2.5.0
>
>
> As the CamelAsyncProcess always takes some time to do it job, we barely hit the upper situation, but it still has chance to hit this situation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.