Re: Help diagnosing camel exception

Hello, Not the easiest route to follow ;) But basically the log seems to say that you are doing a synchronous action over some protocol and waiting for a response. You fail to get the response within 3 milliseconds so you get a timeout exception. I suspect it is in the bean(iJobService) based

2.18.3 - Rest DSL MockEndpoint - second unit test weaveByToUri fails with "no output which matches: direct:RouteB in the Route(getRoute)

I have discovered an issue when I run multiple tests on a route using weaveByToUri on the same endpoint. I have it replicated in my sample app. https://github.com/owain68/camel-spring-boot-examples It looks as though the .replace() replaces the endpoint for the whole test class, not just the indi

Re: XMLSecurity not generating

Hello Ayache, you can do this by implementing your own KeyAccessor. The KeyAccessor interface https://github.com/apache/camel/blob/master/components/camel-xmlsecurity/src/main/java/org/apache/camel/component/xmlsecurity/api/KeyAccessor.java contains the method KeyInfo getKeyInfo(Message message,

Re: Guidance to choose "future proof" http consumer/producer components

Thank you Zoran and Claus! To sum it up, the recommendation is: use http4 component for http producer endpoints (to(...)) and jetty component for http consumer endpoints (from(...)). Possibly re-evaluate when undertow component has matured. -- View this message in context: http://camel.465427.

Re: Guidance to choose "future proof" http consumer/producer components

Hi, Do you guys have any comments on the netty component for http? Will it continue or will it also soon be deprecated? Thanks Souciance On Thu, Apr 27, 2017 at 3:18 PM, sbrandt2 [via Camel] < ml+s465427n5798412...@n5.nabble.com> wrote: > Thank you Zoran and Claus! > > To sum it up, the recomme

Re: camel splitter

thank you very much for the idea, I will try that. I like it more than my approach. I will let you know. thanks so much again! - Gary Lee Mills -- View this message in context: http://camel.465427.n5.nabble.com/camel-splitter-tp5798339p5798416.html Sent from the Camel - Users mailing li

Re: XMLSecurity not generating

Many thanks Franz, that's what I've implemented yesterday and I was going to come back here to update the post and you beat me. -- View this message in context: http://camel.465427.n5.nabble.com/XMLSecurity-not-generating-tp5798321p5798419.html Sent from the Camel - Users mailing list archive

Camel 2.18.1 Jetty UrlRewrite does not return cookies from original response

Hi all, we are just upgrading one of our applications which also uses Camel for routing purposes. We also decided to upgrade the Camel version and went from 2.11.x to 2.18.1. We now discovered that when routing to the following endpoint 'to uri="jetty:$gui/polopoly/?bridgeEndpoint=true&urlRewrite

camel-kafka offset commit

Hi, I have a question about offset commit, if auto commit is off, then it does a batch commit, my question is in this case, ss a message considered consumed after reading from the topic or after the whole processing is done? Thanks Shannon -- View this message in context: http://camel.465427.

Re: Help diagnosing camel exception

In the bean:jobService it may go on to hit a mongo instance. But I'm not sure where in the logs it led you to think it was there except that you looked at the initial logs in the original message. Those logs could be a little confusing I'm sure as the original authors of the code did some interes

Re: header message show different values in log statements

On Wed, Apr 26, 2017 at 11:26 PM, jan.schjoenning wrote: > Given following route : > > from("direct:TranslateEpgData") > .routeId("TranslateEpgData") > .setHeader("xxx", constant("xxx")) >.to("log:?showAll=true&multiline=true") >

Re: Help diagnosing camel exception

Just a quick thing, couldn't you disable all the routes and beans first and then enable them one by one to pinpoint which one is the culprit? Den 27 apr. 2017 6:54 em skrev "Ryan T [via Camel]" < ml+s465427n579842...@n5.nabble.com>: In the bean:jobService it may go on to hit a mongo instance. Bu

Re: header message show different values in log statements

Thanks Doug ! Fine explanation - and make sense. Reason for having log was to find out why parameters transfer to xslt were "wrong"- so they will be removed from solution. Regards Jan -- View this message in context: http://camel.465427.n5.nabble.com/header-message-show-different-values-i

Re: Help diagnosing camel exception

That would be ideal, but I it is really hard to reproduce. Out of say 6 records processed. I "sometimes" get the timeout. Everytime I run it in my local dev environment it seems to succeed. When it does fail in my dev environment, I usually have to add more logging as I learn more. I'm bas

Re: Help diagnosing camel exception

Hi Ryan, It seems to be that you'd be better off breaking up some of those routes; they seem very large and monolithic. Prefer composed routes instead, each with discrete error handlers. Currently you're looking for a fault through a large slice of functionality. The use of the doCatch clauses is

Re: Help diagnosing camel exception

Hi Ryan I agree with Paul. It is quit hard to troubleshoot those complicated routes. It would be easier if you can break them into smaller and more independent routes which can be tested easier. I would also enable this class which is the AuditEventNotifier which will give more detailed informati

Re: Help diagnosing camel exception

> Can you explain why some of the individual processor nodes in each route > have processing times in the order of an hour or more!? The route is a batch job process that is triggered by a Quartz2 or API get call. The base route can take anywhere from 2 minutes to run in the case of ATT because

Re: Help diagnosing camel exception

Couldn't you use an OnException for logging and then continue? This way, the processing doesn't step because of one error. OnException().continued(true).to("seda:LogErrors"); Virusfritt.

Re: Help diagnosing camel exception

I thought about increasing the timeout limit, but the timings do not suggest that would be the best way to handle the issue. The reason I say that is because the timings on 99% are with in 2 seconds. Fact is the only time i see them go above 2 seconds is when these timeouts occur. This suggests

Re: Help diagnosing camel exception

I actually do have that. If you look at the code the try catch only catches: CxfOperationException.class, UnknownHostException.class, ConnectException.class, SocketTimeoutException.class, NoRouteToHostException.class, Fault.class When the TimeoutException happens it does not go into this portion

Understanding onExceptionOccurred

What is the difference between the following: and -- View this message in context: http://camel.465427.n5.nabble.com/Understanding-onExceptionOccurred-tp5798470.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: AWS S3 and Minio (or other S3 emulator)

Why don't u go for a free tier account and use S3? I'm using it with camel and java sdk .. works well.. Sent from my Cyanogen phone On Apr 25, 2017 8:59 AM, Mark Nuttall wrote: Does anyone have experience using Camel with an AWS S3 "emulator". I don't currently have access to AWS S3 so i am tr

Re: AWS S3 and Minio (or other S3 emulator)

Thanks. I was thinking the same after looking at the free tier. It is for work though and I didn't want my info in our environment. I might stlll do it. I forged ahead with just using Minio with a processor. I might make up an endpoint that better emulates the S3 one and put it on github. On Thu

Re: AWS S3 and Minio (or other S3 emulator)

I don't know your app architecture but if you are planning to move that camel code on aws i will recommend to go with an ec2 instance and test it out on the free tier using S3. You may find some issues that you can address early before you move deep Sent from my Cyanogen phone On Apr 27, 2017

Camel_CXF - Basic Authentication - username password

Hi, I have tried to use Camel-CXF send a Soap message, and camel route like this: from("jms:queue:jms/XXXQ").recipientList(urls).aggregationStrategy(new CustomizeStrategy()).ignoreInvalidEndpoints().parallelProcessing(); List urls = new ArrayList(); String url = "cxf://http://localhost:18088/COM