[
https://issues.apache.org/jira/browse/CAMEL-12104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang reassigned CAMEL-12104:
------------------------------------
Assignee: Freeman Fang
> Unintuitive default cxf timeout behavior
> ----------------------------------------
>
> Key: CAMEL-12104
> URL: https://issues.apache.org/jira/browse/CAMEL-12104
> Project: Camel
> Issue Type: Bug
> Components: camel-cxf, camel-cxfrs
> Reporter: Adam Campbell
> Assignee: Freeman Fang
> Priority: Major
> Fix For: 2.21.0
>
> Attachments: Screen Shot 2018-02-28 at 15.20.31.png
>
>
> There is very strange behavior in Camel cxf and cxfrs timeouts which could
> lead to sensitive data being released.
> Below is a code sample which illustrates the unexpected behavior. I think any
> developer would expect the test API to return "Valid Response" or some kind
> exception, but in fact it returns "SENSITIVE DATA" due to the default
> continuationTimeout of 30 seconds.
> This issue seems to have been introduced by
> https://issues.apache.org/jira/browse/CAMEL-7401
> {code:java}
> public void configure() {
> from("cxf:///test?dataFormat=MESSAGE")
> .setBody(constant("SENSITIVE DATA"))
>
> .to("cxf://http://localhost:8003/slowApi?serviceClass=com.example.ExampleService&dataFormat=MESSAGE";)
> .transform(constant("Valid Response"));
> from("cxf:///slowApi?dataFormat=MESSAGE")
> .process(new Processor(){
> @Override
> public void process(final Exchange exchange) throws Exception
> {
> Thread.sleep(45000);
> }
> });
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
