request-reply with RabitMQ and Camel

Hi, I'm trying to convert to from ActiveMQ to RabbitMQ (with the RabbitMQ component) but I cant seem to get reply's working. When using the ActiveMQ component on an inOut route I see the TemporaryQueueReplyManager and jmsreplyto header automatically handle the response for me. However I cant seem t

Re: Camel can't Route Topic

Try destinationName injection: #deadQueue*&jmsMessageType=Text"/> -- View this message in context: http://camel.465427.n5.nabble.com/Camel-can-t-Route-Topic-tp5762517p5762712.html Sent from the Camel - Users mailing list archive at Nabble.com.

Archiving Files after sending records to Queue

We would like to process a set of files, batch the records into small batches, send to queue and archive the files to another folder. We are using Apache Camel Framework. Also We are validating CamelSplitComplete property to check whether we can perform archival of the files. The files are not g

Re: FileLockExclusiveReadLockStrategy doesn't hold lock and error on commit

I don't think this is a platform issue. It could be that the filelock strategy as a whole is simply not compatible with the rename file strategy at all and what is currently there is just a hack pretending to do it correctly. The error is happening because the lock is being released immediately a

Re: breadcrumbId does not survive http call

Hello Claus, I have logged https://issues.apache.org/jira/browse/CAMEL-8351. Thanks! Ralf Claus Ibsen-2 wrote > You are welcome to log a JIRA. I think spring-ws has some ways of telling > it to include HTTP headers too. -- View this message in context: http://camel.465427.n5.nabble.com/b

Re: breadcrumbId does not survive http call

On Fri, Feb 13, 2015 at 1:43 PM, rsteppac2 wrote: > I absolutely require a log correlation ID that never changes for a request > across all our components. The breadcrumb looked like a good fit for that. > Yeah lets see if we can get that dude safe across camel-spring-ws. You are welcome to log a

Re: breadcrumbId does not survive http call

I absolutely require a log correlation ID that never changes for a request across all our components. The breadcrumb looked like a good fit for that. James Carman wrote > Do you absolutely require that the breadcrumb's match between the proxy > and your web service? -- View this message in

Re: request-reply with ActiveMQ and Camel

The source code for InOut over JMS is all in the camel-jms component. Mind there is a lighter alternative component called camel-sjms, but its not as battle tested or feature rich as camel-jms (which uses spring jms). On Fri, Feb 13, 2015 at 10:56 AM, Marco Crivellaro wrote: > Thanks for the rep

Re: FileLockExclusiveReadLockStrategy doesn't hold lock and error on commit

Hi Windows file system works different than unix based and therefore you can hit issue like that, that otherwise works on unix systems. Its a bit wonky having to add logic to cater for this on windows. The other read locks works better on windows. And using readLock=fileLock is not guaranteed to

Re: RejectedExecutionException: Task rejected due queue size limit reached

Hi See http://camel.apache.org/threading-model.html On Fri, Feb 13, 2015 at 10:58 AM, Behrad wrote: > I'd have preferred to set maxQueueSize to 1 or 10 instead of > rolling a new executorService, isn't that configurable? > > 2015-02-13 12:33 GMT+03:30 Taariq Levack : > >> You can try set

Re: RejectedExecutionException: Task rejected due queue size limit reached

I'd have preferred to set maxQueueSize to 1 or 10 instead of rolling a new executorService, isn't that configurable? 2015-02-13 12:33 GMT+03:30 Taariq Levack : > You can try set a custom executorServiceRef on your error handler, by > default the maxQueueSize is 1000, mind that you don't r

Re: Camel java dsl: try/catch+stop = finally is not evaluated

Hi Yes a stop is a hard stop, doFinally was intended about an exception was thrown, but you want to call some logic. It may further complicate routing engine if a stop is not a stop but should continue under special use-cases. On Fri, Feb 13, 2015 at 10:42 AM, vasilievip wrote: > I'm thinking

Re: request-reply with ActiveMQ and Camel

Thanks for the replies Camel is only used to consume the request queue and post the replies, the requestor is a .NET app based on NMS and the aggregation part works fine as the setup works fine when using a standard queue on JMSReplyTo header: camel is sending the multiple replies to the queue and

Re: Camel java dsl: try/catch+stop = finally is not evaluated

stop() stops the route so i thinks in my opinion this is expected behavior. What happens if you remove stop() from doCatch() and put it at the end of the doFinally() ? On 13/02/2015 10:42, vasilievip wrote: I'm thinking to stop execution in case of exception, but I do want to perform some log

Camel java dsl: try/catch+stop = finally is not evaluated

I'm thinking to stop execution in case of exception, but I do want to perform some logging in finally block. The .stop() definition looks like does what I need but it stops "finally" definition as well. https://github.com/vasilievip/camel-spring-boot/blob/master/src/main/java/cameltest/CamelConfigu

Re: RejectedExecutionException: Task rejected due queue size limit reached

You can try set a custom executorServiceRef on your error handler, by default the maxQueueSize is 1000, mind that you don't run OOM. Here's the relevant code and comments from DefaultThreadPoolFactory; // need to wrap the thread pool in a sized to guard against the problem that the