https4

I'm trying to connect to devices that have https enabled but you connect to an ip address and no valid certificates. How can I allow all certificates using http4 endpoint? Getting error: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: No trusted certificate found

Re: ExchangeTimedOutException

Any other advice out there as to the problem I am trying solve? -- View this message in context: http://camel.465427.n5.nabble.com/ExchangeTimedOutException-tp5795836p5795893.html Sent from the Camel - Users mailing list archive at Nabble.com.

Help diagnosing camel exception

can anyone help me on diagnosing this exception? Any hints as to how I might proceed on fixing it? -- View this message in context: http://camel.465427.n5.nabble.com/Help-diagnosing-camel-exception-tp5796669.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Help diagnosing camel exception

First, thanks souciance for responding. You seem to be the only one that will respond to me posts and you have been of great help. I understand that I am having a timeout because the OUT is not received in time. What I am having trouble finding is what actual part or node that the OUT is not b

Re: Exception handling in camel

You can obtain the exception like this in side your ExceptionProcessor: As far as the bean, I am unsure as to what bean you are referring to, but if I could make a guess you probably want to just get the exchange.getIn().getBody() When an exception happens the body of the currently processing m

Re: Exception handling in camel

On a side note to save you some trouble: DO NOT USE the endDoTry() method call. Change them to just end() it will save you a headache as I spent a ton of time figuring why the try catch was not working properly. It should look like the following: Hope that helps. Cheers! -- View this messa

Re: Help diagnosing camel exception

Sorry it took me so long to get back. I wanted to add some more logging to try to be more complete in defining my problem. Below is the code: Below here is the logs of what I am getting: Error: success: In the error case I am confused to as why it skipped several nodes of the route. I exp

Re: Help diagnosing camel exception

More code that might help in diagnosing the issue. What do you think could be happening? -- View this message in context: http://camel.465427.n5.nabble.com/Help-diagnosing-camel-exception-tp5796669p5798367.html Sent from the Camel - Users mailing list archive at Nabble.com.

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: 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

> 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

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.

Bug in onException with onRedelivery

I am running into an anomaly that I am hoping someone can resolve. I have a route that looks like: And a MyProcessor: RedeliveryProcessor: I start the test as below: Result obtained: --- redeliveryCount: 1 --- redeliveryCount: 2 [main] WARN route3 - *** YetAnotherException happened. B

Re: Bug in onException with onRedelivery

Can someone verify that this is a bug or not? -- View this message in context: http://camel.465427.n5.nabble.com/Bug-in-onException-with-onRedelivery-tp5798549p5798619.html Sent from the Camel - Users mailing list archive at Nabble.com.

How to increase camel exchange timeout threshold

I'm getting this exception. org.apache.camel.ExchangeTimedOutException: The OUT message was not received within: 3 millis. Exchange[ID-mid3-33287-1493765150908-0-613311] Anyone know how to change the threshold to say 60 seconds? I've tried: from("seda:myProcess?concurrentConsumers=10&timeou

Re: How to increase camel exchange timeout threshold

souciance, Thanks for the feed back. I will try that change. Do you know if there is a way to do it at the route level? -- View this message in context: http://camel.465427.n5.nabble.com/How-to-increase-camel-exchange-timeout-threshold-tp5798620p5798654.html Sent from the Camel - Users maili

Re: Bug in onException with onRedelivery

I stepped through it with the debugger and yep it does. You could try it if you would like. https://github.com/catequil/CamelTests.git The repository should be public. -- View this message in context: http://camel.465427.n5.nabble.com/Bug-in-onExc

seda timeout setting not working as expected

I have a seda route: I expected and error in the logs as below: The OUT message was not received within: 45000 millis. Exchange[ID-rtracy-53657-1494891566058-0-24] But I got the below instead: The OUT message was not received within: 3 millis. Exchange[ID-rtracy-53657-1494891566058-0-24]