That would be ideal, but I it is really hard to reproduce. Out of say 60000 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 basically trying to prove that it is a network or connectivity issue and eliminate the code as the problem, but if I cannot pin point the exact node there is the doubt that it could be happening in the serializer or a database call to mongo or in the cxf code that does the rest call. My gut says that it is a connectivity issue, but how do you explain to management that the problem is between Amazon, and Verizon, Kore(T-Mobile), or ATT. They are more inclined to say it is the code base. Because of this being more reproducible in a production environment, it makes it really hard to just start removing node to find the problem. It is however an interesting thought and I will look into maybe making a pseudo route that can mimic pieces in the route, specifically the places I think it might be happening.
On a side note: I forgot to give you the actual exception in the log as part of the log post message to this board. Included below: -- View this message in context: http://camel.465427.n5.nabble.com/Help-diagnosing-camel-exception-tp5796669p5798428.html Sent from the Camel - Users mailing list archive at Nabble.com.
