Hi Not sure what is wrong there. But setting exchangePattern=InOnly works in unit tests. You could try setting disableReplyTo=true as a workaround
On Fri, Jan 9, 2015 at 3:05 PM, Ettoregia <ettore...@gmail.com> wrote: > Hi All, > > I'm facing a problem which I guess stems from the usage of MEP. > > Actually when I hit the http://localhost:8082/user/ by using a PUT verb, the > client hangs for > 20 millis and then an exception is raised (see below). I thought that by > specifying the exchangePattern=InOnly > Camel should return a response back straight away. > > Any ideas? > > -------------------------------------------------------------------------------------------------------------- > restConfiguration().component("jetty").bindingMode(RestBindingMode.json) > .host("localhost").port(8082); > > rest("/user").description("User rest service").consumes("application/json") > > .put().description("Updates or create a user") > .route() > .choice() > .when(header("firstInvocation")) > > .to("activemq:queue1?exchangePattern=InOnly") > .log("######### Order received from > browser rest client #########") > .otherwise() > .log("######### All done #########") > .to("mock:result") > .endChoice().endRest() > > ----------------------------------------------------------------------------------------------------------- > org.apache.camel.ExchangeTimedOutException: The OUT message was not received > within: 20000 millis due reply message with correlationID: > corrID0111111111111111111111111 not received. Exchange[Message: > {replyQueue1=replyQueue1, height=46, weight=34, age=29}] > at > org.apache.camel.component.jms.reply.ReplyManagerSupport.processReply(ReplyManagerSupport.java:133) > at > org.apache.camel.component.jms.reply.TemporaryQueueReplyHandler.onTimeout(TemporaryQueueReplyHandler.java:61) > at > org.apache.camel.component.jms.reply.CorrelationTimeoutMap.onEviction(CorrelationTimeoutMap.java:54) > at > org.apache.camel.component.jms.reply.CorrelationTimeoutMap.onEviction(CorrelationTimeoutMap.java:30) > at > org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:212) > at > org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:162) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > ----------------------------------------------------------------------------------------------------------------------- > > Regards, > Ettore. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Rest-DSL-org-apache-camel-ExchangeTimedOutException-The-OUT-message-was-not-received-within-20000-mis-tp5761530.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
