Re: ExchangeTimedOutException

So what I discovered is this message history is the history starting from the onException. Which does not help me. I need the history from the original route before the exception occurred or maybe the whole route history to help me discover where this timeout is occurring. Or maybe we could

Re: ExchangeTimedOutException

I was hoping the messageHistory might have enough information in it to give me an idea of where to look. Added the following code to my TimeOutErrorProcessor When I finally got the exception this is what it printed out: Is there any way to get a more descriptive Node identifier rather than

Re: ExchangeTimedOutException

Those pieces of information were too general. It reported "seda:processItemsJob" as the endpoint, but there is a lot of segments in that area. Any other suggestions? The other problem I am having is because of the parallel processing the log messages are getting all tangled together. It would

ExchangeTimedOutException

I have a route similar to the following: Everything once in a while I get the ExchangeTimedOutException, but I do not know from which route segment the ExchangeTimedOutException is happening. Does anyone know how to determine where the timeout is actually occurring? -- View this message in

Tracing performance

I would like to be able to print out in the logs temporarily a traceRoute with processing times. similar to the message history, but without an exception happening. Is there a way at the end of the route to print the message history or is there a better way to diagnose performance? -- View

Re: quartz2 endpoint timezone issue

Anyone have any ideas on this? -- View this message in context: http://camel.465427.n5.nabble.com/quartz2-endpoint-timezone-issue-tp579p5793386.html Sent from the Camel - Users mailing list archive at Nabble.com.

quartz2 endpoint timezone issue

I'm running an endpoint of: quartz2://job/deviceDetailsUsageTimer48?cron=0+0+04+*+*+?=GMT=2 on an amazon ec2 instance that has the timezone set to UTC. My expectation is that the job should go off at 4am GMT based on the quartz2 endpoint configuration, but the logs on the ec2 instance show it

Re: Camel route not getting to aggregation and bean in certain cases

*Solution:*So I found the problem. The problem was with my doTry...Catch...[endDoTry] block.Do not use the endDoTry closing method. Just call end to end your try catch block. Can we some how add to the docmentation to not use the endDoTry and/or explain what the endDoTry does.Or can we remove

Re: Camel route not getting to aggregation and bean in certain cases

So, I tried to consolidate the calls all into the same route where it is getting dropped to see if having it in its own direct route was causing the problem. See new code below for reference. No change in functionality occurred. -- View this message in context:

Re: Camel route not getting to aggregation and bean in certain cases

I placed a log call here: It only printed out when there was an error, with the same results as before. The aggregationId was in the header for the error one, but then again I only got the one 'error' result continuing. Thanks for your quick reply! -- View this message in context:

Camel route not getting to aggregation and bean in certain cases

*Camel route not getting to aggregation and bean in certain cases.* Below is my camel route. When the route encounters a SoapFault the route works great. However, in the case of success from the soap call the route never gets to the aggregation and bean calls marked < below. I would expect

camel-kafka 2.16.2 -> 2.17.3

I have upgraded camel-kafka from 2.16.2 -> 2.17.3 and I am having an issue with the serializerClass the above used to work, but now it is throwing the exception below: There is a lot of documentation on using the "kafka.serializer.StringEncoder" for kafka 0.8.2 or older, but nothing for

Re: CamelTestSupport best way to unit test the OUT or result of the route

@Steve973 Can you elaborate on your comment? I don't understand why that would be the case. Why have the "skipSendToOriginalEndpoint" if a strict unit test was not intended? I'm new to Camel so if you could help me understand. I would like to correctly implement testing in camel. -- View

Re: CamelTestSupport best way to unit test the OUT or result of the route

I applogize, I just missed that. I actually do have that in my test. I've kinda got a mix of an example of what I have in prod and the test code. right after context.start(); i have: template.request("direct:someCamelEndpoint", (Exchange exchange) -> setExchangeProperties(exchange,

CamelTestSupport best way to unit test the OUT or result of the route

Using CamelTestSupport how do you test the out, or result of the route when it does not end in a endpoint call? Would I just put in my production route code a .to("mock:result) for each API call/route and intercept it or is there a better way that does not put a mock:endpoint in my production

Re: Dynamic routing based on collection values

Here is another option to look at that takes a little bit different approach. -- View this message in context: http://camel.465427.n5.nabble.com/Dynamic-routing-based-on-collection-values-tp5789157p5789362.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel Spring Unit Testing with Mocks

Ok, so it appears that I understand and have a working copy. There are however a few remaining questions. If you feel they are no longer relevant in this thread let me know and I will create a new thread. In the code below I expected it to grab the "myRouteMiddle" route and find the

Re: CxfEndpoint soap client usernametoken authentication

In step 1 you set 4 props. Where would these props get set in the DSL? or can I somehow set them in the camel-config.xml as part of the cxfendpoint element? This part is a little vague to me. I hope you can help? Thanks! -- View this message in context:

Camel Spring Unit Testing with Mocks

Background I'm a newbie to Apache Camel. (3 months) I have read the testing section to Camel in Action MEAP version. I have read http://camel.apache.org/testing.html and http://camel.apache.org/spring-testing.html I have searched this forum, google and stackoverflow for answers. I've tried using

Re: CxfEndpoint soap client usernametoken authentication

Just was wondering if anyone had thought about a solution to this issue yet? -- View this message in context: http://camel.465427.n5.nabble.com/CxfEndpoint-soap-client-usernametoken-authentication-tp5787910p5788623.html Sent from the Camel - Users mailing list archive at Nabble.com.

RE: CxfEndpoint soap client usernametoken authentication

I looked at that article already. It mainly talks about how to the digest version, but I need to do the username plain text. Then I could not figure out how to merge cxf-ws-security into the Camel route. Also, I was hoping that someone had already crossed this bridge and had a solution that was

CxfEndpoint soap client usernametoken authentication

I am trying to access a soap service that requires that I athenticate with a usernametoken in the security header. Example desired outcome: I can get the soap envelope part right with body, but the header with security header alludes me. Does anyone have a best practices for doing this in