Re: Camel 2.15.1 XSLT returning only the closing tags

Hi, On 03/28/2017 06:43 AM, Boba wrote: I am trying to do a really simple xml to xml transformation using the xslt uri, I have dumbed it down so the input and transformed messages are basically the same to try and work this out... I used stylus studio to create the xml to xml mapping (I'm not

Re: Is there any way to limit the values for Accept: header for camel-atom and camel-rss?

Hi, It seems to be right, both of camel-rss and camel-atom doesn't allow to configure request headers other than basic auth. You may want to file a JIRA for it. Or I haven't tried yet though, it seems possible to use camel-http4 as a polling consumer which accepts custom

Re: Camel instanciated as null

I cleaned this up a bit it loads without any errors but does not run anyone have any ideas why this would fail? http://www.osgi.org/xmlns/blueprint/v1.0.0; xmlns:jaas="http://karaf.apache.org/xmlns/jaas/v1.0.0;

Camel 2.15.1 XSLT returning only the closing tags

I am trying to do a really simple xml to xml transformation using the xslt uri, I have dumbed it down so the input and transformed messages are basically the same to try and work this out... I used stylus studio to create the xml to xml mapping (I'm not knowledgeable in xslt)

Re: Unable to Catch an Exception in Netty

doTry didn't help either, as the error "Could not create JMS transaction" I think is happening before starting the route, so it is not being caught in doCatch or ErrorHandlers -- View this message in context:

Re: Unable to Catch an Exception in Netty

I found this thread also, so maybe it is a bug in Camel. http://camel.465427.n5.nabble.com/exception-handling-of-transacted-servlet-route-td5779274.html -- View this message in context: http://camel.465427.n5.nabble.com/Unable-to-Catch-an-Exception-in-Netty-tp5796040p5796446.html Sent from the

Re: Unable to Catch an Exception in Netty

doTry didn't help either, as the error "Could not create JMS transaction" I think is happening before starting the route, so it is not being caught in doCatch or ErrorHandlers -- View this message in context:

Re: Unable to Catch an Exception in Netty

What happens if you add a doTry() and doCatch(Exception.class) around the part which throws the exception? Does this catch the exception? On Mon, Mar 27, 2017 at 9:38 PM, hammod [via Camel] < ml-node+s465427n5796442...@n5.nabble.com> wrote: > I found this thread, it is the same problem I think,

Re: Unable to Catch an Exception in Netty

I found this thread, it is the same problem I think, also the OP in that thread said he is getting exception handling working when he is removing transaction notation http://camel.465427.n5.nabble.com/Problem-with-exception-handler-onException-on-Camel-2-12-X-routes-td5742605.html -- View this

Re: Unable to Catch an Exception in Netty

java.lang.Exception true -- View this message in context:

Re: Unable to Catch an Exception in Netty

Can you share your OnException code as well`? On Mon, Mar 27, 2017 at 9:16 PM, hammod [via Camel] < ml-node+s465427n5796438...@n5.nabble.com> wrote: > I just found that the OnExcpetion is working when I remove the > part form the routes, unfortunately I need this route to be > transacted > >

Is there any way to limit the values for Accept: header for camel-atom and camel-rss?

I'm trying to tap into an atom feed that is requiring the Accept request header to either be application/xml or application/atom+xml. Is there a way to limit the atom feed definition in the uri to specify only those two values? Currently the default for the atom feed appears to be Accept:

Re: Unable to Catch an Exception in Netty

I just found that the OnExcpetion is working when I remove the part form the routes, unfortunately I need this route to be transacted -- View this message in context: http://camel.465427.n5.nabble.com/Unable-to-Catch-an-Exception-in-Netty-tp5796040p5796438.html Sent from the Camel - Users

Re: RabbitMQ fanout exchange + request-reply + aggergator

Hi Souciance, I did exactly what you propose in the second part of your reply. I split the flow into 2 steps: 1) send out the request to multiple consumers via the fanout exchange with inOnly pattern; 2) aggregate the reply messages in another route, that consumes the replies from a fixed

Re: Unable to Catch an Exception in Netty

Any help ? -- View this message in context: http://camel.465427.n5.nabble.com/Unable-to-Catch-an-Exception-in-Netty-tp5796040p5796302.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel Activemq property JMSDestination value different between 5.12.1 and 5.13.0

Hi Claus thanks for the reply. I am posting here as I have run the test case from the master branch which is using activemq 5.14.4 broker and client. However, the test case still returns the correct value : org.apache.camel.component.jms.activemq.ActiveMQConsumeWildcardQueuesTest Connected to

Re: Camel Activemq property JMSDestination value different between 5.12.1 and 5.13.0

Hi You should likely ask on the ActiveMQ user forum as its a change in ActiveMQ and not Camel. On Mon, Mar 27, 2017 at 4:51 PM, chiippy wrote: > Hi > > my question is about the JSMDestination camel header value changes when > connect my client to use between activemq 5.12.1

Camel Activemq property JMSDestination value different between 5.12.1 and 5.13.0

Hi my question is about the JSMDestination camel header value changes when connect my client to use between activemq 5.12.1 and 5.13.4. My application was implemented bases on the this existing camel-jms test case: ActiveMQConsumeWildcardQueuesTest.java

Re: RabbitMQ fanout exchange + request-reply + aggergator

Hello, Your description points to some hybrid between publish/subscribe i.e. you want to send to multiple consumers and you want responses from them to aggregate the messages which is more synchronous. I am not sure this is easily accomplished in one step as the two patterns don't mix in Rabbit

RabbitMQ fanout exchange + request-reply + aggergator

I'd like to implement the request-reply pattern over RabbitMQ the following way: 1. The request is sent to a RabbitMQ fanout exchange (i.e. it will be received by multiple consumers) 2. Each consumer prepares and sends its on response (e.g. if they can fulfill the given request/order and at what

Re: Best way to poll a database and process in chunks

I didn't see the original message from dvlato. We are doing pretty much exactly what you describe. We are using blueprint.xml to describe our routes. We start with a timer Then we have some intermediate code using a bean that determines status we are going to look for - in our case records

Re: Unable to send response to webservice

What you use as response must fit what the SOAP webservice is defined to use as response, eg in all that WSDL / SOAP spec stuff. In your use case you use a bean as the endpoint so must match that bean endpoint as well. And study some of the CXF examples from Camel, or from 3rd party blogs, or in

Re: Old Exchange always returns null

If you want all files to be aggregated together then use a constant expression. Read more about the eip pattern and how it works http://camel.apache.org/aggregator2.html Its concept is also detailed in the EIP book. And other books like Camel in Action and Camel Cookbook have much more details

Unable to send response to webservice

Hi, My scenario is like: 1. Expose a CXF endpoint and accept the request message 2. Transform the request message 3. Put the message in a JMS queue 4. Send a response to the caller that the message is successfully posted in the queue My route is as follows from("cxf:bean:someEndpoint")

Re: Old Exchange always returns null

If I use the following from("direct:items") .aggregate(header(*"id"*), myAggregationStrategy) .completionTimeout(500) .to("direct:send-to-A"); I am getting invalid correlation id error. Regards, Prasad On Mon, Mar 27, 2017 at 2:42 PM, Claus Ibsen wrote:

Re: Old Exchange always returns null

Your use the file name as aggregrate expression and therefore its grouping per file name and so file a.txt and b.txt do not group together. And you get aggregate with old exchange as null when a new group is started On Mon, Mar 27, 2017 at 10:49 AM, Ambika Das

RE: Exception not thrown on connect failed in Dynamic Routes

Hi upgrading is not an option right now as a bunch of routes depend on this. Please suggest an alternative From: Andrea Cosentino-2 [via Camel] [mailto:ml-node+s465427n579627...@n5.nabble.com] Sent: Monday, March 27, 2017 2:49 PM To: Shankar, Shivaranjini

Re: camel-spring-boot + @UseAdviceWith

Hi, I am having similar issues as per https://issues.apache.org/jira/browse/CAMEL-9332 I noticed the solution (https://github.com/apache/camel/tree/master/components/camel-spring-boot/src/test/java/org/apache/camel/spring/boot/mockendpoints ) and downloaded it. The example worked fine until I

Re: Exception not thrown on connect failed in Dynamic Routes

Hi, > Camel Version used: 2.10.1 > JDK: 6 It's actually quite old. Try the latest Camel 2.18.3 and JDK 8 and see the issue is still persistent. Many bugs have been fixed since 2.10.1. On Mon, Mar 27, 2017 at 6:01 PM, Shankar, Shivaranjini < shivaranjini.shan...@blackrock.com> wrote: > Hi team

Re: Exception not thrown on connect failed in Dynamic Routes

Camel 2.10.1 is too old. Try with a new release. -- Andrea Cosentino -- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Monday, March 27, 2017 11:16 AM, Shivu195

Exception not thrown on connect failed in Dynamic Routes

We are facing the following issue. Whenever the camel route is unable to connect to an endpoint(from a list of endpoints dynamically generated using "@DynamicRouter"), it stops sftp-ing the files to all endpoints after the failed endpoint and also it does not throw an error when the said endpoint

Re: file input with tail -f behaviour

What do you mean by start from beginning? It ought to read line by line when the file is appended. And if a new file is created it starts from top again. If you shutdown Camel, it does not remember where it was last time, and start all over again On Fri, Mar 24, 2017 at 11:28 AM, Oliver Wulff

RE: Exception not thrown on connect failed in Dynamic Routes

Hi team We are facing the following issue. Whenever the camel route is unable to connect to an endpoint(from a list of endpoints dynamically generated using "@DynamicRouter"), it stops sftp-ing the files to all endpoints after the failed endpoint and also it does not throw an error when the

Re: Process several messages from several JMSEndpoints with single ThreadPool

Yes. -- View this message in context: http://camel.465427.n5.nabble.com/Process-several-messages-from-several-JMSEndpoints-with-single-ThreadPool-tp5796093p5796265.html Sent from the Camel - Users mailing list archive at Nabble.com.

Old Exchange always returns null

Hi, I am aggregating contents of a csv file. the csv file can contain rows with same e mail id. For those lines I need to generate a combined JSON with contents aggregated. I am using PreCompletionAwareAggregationStrategy and my aggregate method looks like this. if (oldExchange == null) {

Re: Process several messages from several JMSEndpoints with single ThreadPool

Are you using ActiveMQ as your provider? On Mon, Mar 27, 2017 at 9:57 AM, makkenza [via Camel] < ml-node+s465427n5796247...@n5.nabble.com> wrote: > The GUI might get updates to the product from the customers, therefore, we > want to keep the queues as long as the GUI is running. Users have

Re: Process several messages from several JMSEndpoints with single ThreadPool

The GUI might get updates to the product from the customers, therefore, we want to keep the queues as long as the GUI is running. Users have Alerts setup on their GUI, so when customers send updates, those Alerts might trigger... -- View this message in context:

Re: Process several messages from several JMSEndpoints with single ThreadPool

The reason I ask is that, shouldn't the queues be temporarily created and once the processing is over, they are then destroyed? On Mon, Mar 27, 2017 at 9:16 AM, makkenza [via Camel] < ml-node+s465427n5796223...@n5.nabble.com> wrote: > They usually start with 50 then during the day, as users need

Re: Process several messages from several JMSEndpoints with single ThreadPool

They usually start with 50 then during the day, as users need to work on more products, they add more. Mid-day they end up with OOM error when they hit 180 - 200 products. -- View this message in context: