Re: seda concurrency when sending messages to another route

Hi Yes you can break up big routes into multiple routes, and "link" them together using direct endpoints. And yes the seda consumer will not pickup a new message while you call other routes using direct. On Sun, Jul 20, 2014 at 6:12 PM, Robert Rich wrote: > Hi folks, > > My understanding is that

How to retrieve Sqs message attributes

Hi all, I created a consumer to poll messages via aws sqs. I can retrieve message body but can not get message attributes. any suggestions? Thanks in advance -- View this message in context: http://camel.465427.n5.nabble.com/How-to-retrieve-Sqs-message-attributes-tp5754109.html Sent from the

RE: Camel automatic route triggers upon server startup

Thanks for replying! So this is interesting. I have implemented a timer via the Spring configuration, however we are trying to get out of Spring and run in 100% java. That said, if I had a timer running every second, or whatever, the example is filling a queue for then a second route to pick up,

seda concurrency when sending messages to another route

Hi folks, My understanding is that the seda queue is single-threaded by default, primarily by virtue of 'concurrentConsumers' defaulting to '1'. To me this means that the route will not pull another message off of the queue until the last one has completed processing. This is my desired beha

How to get all the properties in the exchange in spring configuration

Hi, In the spring configuration we use ${headers} in log to print all the headers in the exchange. Is there a similar way for printing all the properties in the log. Thanks, Naveen Raj -- View this message in context: http://camel.465427.n5.nabble.com/How-to-get-all-the-properties-in-t

Quartz job is not running

Hello, I have a route with quartz component. It was working before, suddenly it is not working. My Route is: As I checked the log, I observed this message. 4062 [main] INFO org.quartz.core.QuartzScheduler - Scheduler meta-data: Quartz Scheduler (v1.8.6) 'Default

Re: camel-spark-rest

On Sat, Jul 19, 2014 at 9:35 PM, Matt Sicker wrote: > On 19 July 2014 01:42, Claus Ibsen wrote: > >> This is changing slightly as part of the Rest DSL being part of camel-core. >> This DSL allows you to configure port number and other details. >> >> Ooh, is this related to CAMEL-7354 >

RE: JSON - Jackson return list rather than POJO

Well, a forum is a place you post things. So, it's a bit of a play on words to say, "I'll keep yo posted." -- View this message in context: http://camel.465427.n5.nabble.com/JSON-Jackson-return-list-rather-than-POJO-tp5717341p5754036.html Sent from the Camel - Users mailing list archive at Nab