[
https://issues.apache.org/jira/browse/CAMEL-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998369#comment-12998369
]
Daniel Kulp commented on CAMEL-3702:
------------------------------------
Willem,
It might be slightly harder to debug with 2.3.3-SNAPSHOT/2.4.0-SNAPSHOT as the
HttpRequestWrapper is now only created for one-ways and in some WS-RM/Addr
cases. Thus, it may "just work" with 2.3.3. Try doing a one-way and seeing
if the behavior persists.
> Example camel-example-cxf-tomcat does not work on Tomcat 7
> ----------------------------------------------------------
>
> Key: CAMEL-3702
> URL: https://issues.apache.org/jira/browse/CAMEL-3702
> Project: Camel
> Issue Type: Bug
> Components: examples
> Affects Versions: 2.6.0
> Environment: Windows 7, Tomcat 7.0.8, Camel 2.6.0
> Reporter: Arnoud Glimmerveen
>
> I am trying to get the example camel-example-cxf-tomcat to work on Tomcat
> 7.0.8. This example contains a CxfEndpoint that is configured as being
> asynchronous (by default). Because of this asynchronous setting I was
> notified by an Exception that I should set the async-supported property of
> the CXFServlet in the web.xml. After I set this property to true, I see that
> invocations are received and processed by the Camel route, however the result
> is not returned: the connection is closed directly.
> I assume this issue is not directly related to the example itself (apart from
> the missing async-supported property), however I was not able to pinpoint
> which component is triggering the connection to be closed before the result
> is written.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
