Re: [2.17.0] NULLs are not allowed with named parameter in SQL component

I logged a ticket https://issues.apache.org/jira/browse/CAMEL-9906 On Fri, Apr 22, 2016 at 12:37 PM, Claus Ibsen wrote: > Hi > > You are welcome to try to provide a PR to fix this > http://camel.apache.org/contributing > > On Fri, Apr 22, 2016 at 12:28 PM, Arapov, Artem > wrote: >> Hi, >> >> I'v

Camel SFTP,quartz2 component gives:Cannot retrieve file :caused by GenericFileOperationFailedException,when polling multiple files from sftp

*I'm trying to poll files from sftp location using the below camel route and using quartz2 scheduler, after polling couple of files i'm getting a GenricFileOpertaionFailedException caused by java.io.IOException: Pipe closed* JaxbDataFormat dataFormat = new JaxbDataFormat(); dataFormat.setContext(J

Re: Need an interceptSendTo hook

Actually, one thing I just considered was that the id() DSL doesn't appear to support an expression, so generating it dynamically may not be possible (something I was hoping to be able to do in a second weave spot). Right now I'm actually using the 'browse' component + recipient list for my test ho

Re: Need an interceptSendTo hook

Awesome, thanks Claus. I switched to using weaveById and got the exact behavior that I wanted in my actual route (weaveByType could work too but is a bit less explicit). For the benefit of others, this is how I'd switch my route DSL from what I sent earlier: from("direct:start") .setBody(

Re: TarAggregationStrategy - /tmp directory is full !!

Hi I found room for improvement and trying to address this https://issues.apache.org/jira/browse/CAMEL-9905 You can build from the source with this fix and test it on your system. On Fri, Apr 22, 2016 at 8:40 PM, Claus Ibsen wrote: > Make a shorter and simpler example and see what happens. > >

Re: TarAggregationStrategy - /tmp directory is full !!

Make a shorter and simpler example and see what happens. Also are you running on windows? Then mind that it has such file problems with not able to delete/move files if not all streams has been carefully closed, even if they are from the same process that created it. All that works nicely on linux

Re: Need an interceptSendTo hook

On Fri, Apr 22, 2016 at 6:23 PM, Jeff Segal wrote: > Minh - that's exactly what I'm trying to do. The issue is that I don't have > a great hook to insert my advice where I want. > > Claus - here's a rough example: > > from("direct:start") > .setBody().constant(someXml) > .split().x

Installing feature camel-sql (2.17.0) into karaf 4.0.4 caused karaf to hang

After a clean start of karaf 4.0.4, tried to install cxf and camel: feature:repo-add cxf 3.1.6 feature:install cxf cxf-rt-security feature:repo-add camel 2.17.0 feature:install camel-core camel-spring camel-cxf camel-sql camel-jdbc camel-velocity camel-quartz2 camel-mail camel-groovy The last ste

Re: Need an interceptSendTo hook

Minh - that's exactly what I'm trying to do. The issue is that I don't have a great hook to insert my advice where I want. Claus - here's a rough example: from("direct:start") .setBody().constant(someXml) .split().xpath(anXpathExpression) .setHeader("myHeader", constan

Re: Camel 2.17 - Spring Boot 1.3.3 + Camel-Elasticsearch component conflict(2.2.0->1.5.2)

Another related issue is that the Spring initializer https://start.spring.io/ , can generate a project including Camel (after the resolution of  https://github.com/spring-io/initializr/issues/207), but camel-spring-boot-starter version in the dependencies is not managed by spring-boot-starter-p

RE: How to return early from a direct: subroute?

Hi Ranx, After giving it more thoughts, I think your suggestion of throwing exception is a neat solution. Using a route level OnException to catch and handle the exception, then quietly return to the caller of the direct route. I will give it a try. But there are situations where I need

Camel Kafka 2.17 consumer options

Hello All, We have 2 parameters in consumer for Camel kafka 2.17 component consumerStreams and consumersCount Please could someone help me with the difference between two? And in case we need to improve performance/throughput of Kafka consumer job, which one should be used? Vanshul

Re: Camel 2.17 - Spring Boot 1.3.3 + Camel-Elasticsearch component conflict(2.2.0->1.5.2)

I see. According to their current documentation "The client must have the same major version (e.g. 2.x, or 5.x) as thenodes in the cluster" . This does not look like a major limitation. On Friday, April 22, 2016 1:57 PM, Claus Ibsen wrote: And I hear that the ES guys are working o

Re: Need an interceptSendTo hook

On Thu, Apr 21, 2016 at 8:18 PM, Jeff Segal wrote: > I've got a route that I'd like to do some unit testing on at various > stages. It does a few splits, sets some headers, etc. The problem is that > there's no actual endpoint for me to intercept until the very end, but I'd > like to do some verif

Re: Camel 2.17 - Spring Boot 1.3.3 + Camel-Elasticsearch component conflict(2.2.0->1.5.2)

And I hear that the ES guys are working on a Java client that is more agnostic what ES server version you use. The current Java client is too tightly coupled to the server version. On Fri, Apr 22, 2016 at 11:12 AM, Claus Ibsen wrote: > This is not a Camel problem. > > Its limitation with spring

Re: [2.17.0] NULLs are not allowed with named parameter in SQL component

Hi You are welcome to try to provide a PR to fix this http://camel.apache.org/contributing On Fri, Apr 22, 2016 at 12:28 PM, Arapov, Artem wrote: > Hi, > > I've recently tried out new 2.17.0 version from 2.16.1 and discovered a bug > with named parameters and null values in SQL component. > I u

[2.17.0] NULLs are not allowed with named parameter in SQL component

Hi, I've recently tried out new 2.17.0 version from 2.16.1 and discovered a bug with named parameters and null values in SQL component. I use CamelSqlQuery header to set the query with named parameters as ":?param". Values for that parameters are stored in message body (map). Problem occurs when

Re: Camel 2.17 - Spring Boot 1.3.3 + Camel-Elasticsearch component conflict(2.2.0->1.5.2)

This is not a Camel problem. Its limitation with spring boot if they only work with old ES version. On Fri, Apr 22, 2016 at 11:04 AM, Lefteris Tsallas wrote: > Hi all, > > I started a new Camel Spring Boot project using the maven archetype > camel-archetype-spring-boot. Camel Version 2.17.0 ge

Camel 2.17 - Spring Boot 1.3.3 + Camel-Elasticsearch component conflict(2.2.0->1.5.2)

Hi all, I started a new Camel  Spring Boot project using the maven archetype camel-archetype-spring-boot. Camel Version 2.17.0 gets Spring Boot 1.3.3 After adding the camel-elasticsearch component, it requests  org.elasticsearch:elasticsearch:2.2.0  but Spring boot 1.3.3 forces elasticsearch1.

Re: RXCamel is not releasing the ActiveMQ connection once the subscription is complete

Ok thanks. When will be the new version available (2.7.1)? -- View this message in context: http://camel.465427.n5.nabble.com/Camel-rx-is-not-releasing-the-ActiveMQ-connection-once-the-subscription-is-complete-tp5781482p5781543.html Sent from the Camel - Users mailing list archive at Nabble.com

Re: Camel Spring Boot adding XML routes

Looks like the xml definition lacks the from element ;) --- Luca Burgazzoli On Thu, Apr 21, 2016 at 10:01 PM, Pontus Ullgren wrote: > Hello, > > From a project based on the camel-archetype-spring-boot I'm trying to add > additional routes defined in XML as described in the documentation[0]. > >

Re: RXCamel is not releasing the ActiveMQ connection once the subscription is complete

On Thu, Apr 21, 2016 at 11:16 PM, arunkabraham wrote: > I didnt understand properly. Was I doing some mistake? You attempt to stop the JMS consumer from the same thread that consumed the message, eg spring-jms do not support this, and goes into an endless loop. You need to use a separate thread