camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From souciance <souciance.eqdam.ras...@gmail.com>
Subject Re: Help diagnosing camel exception
Date Thu, 27 Apr 2017 20:04:59 GMT
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");

<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virusfritt.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Thu, Apr 27, 2017 at 10:01 PM, Ryan T [via Camel] <
ml+s465427n5798451h44@n5.nabble.com> wrote:

> > 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 we only have 200 devices.  But for Verizon we have 50000
> devices and that can take around 2 hours to run.
>
> > How are you testing these routes? What unit tests do you have for these
> > routes?
>
> We have some Scala tests that unit test the individual Processors passing
> in a Mocked exchange object.  As for the beans they mostly are services to
> interact with a Mongodb store.  Not much processing actually happens in
> them.  I inherited this code and I have slowly been refactoring it to be
> less monolithic, but that takes time.  I have created some tests, not in
> this area with the timeouts, that test whole routes Mocking the external
> payloads that are received.  They are on the more simpler routes.   But
> doing these test can be difficult because of how monolithic these routes
> are.
>
> > Also, give each node in the processing chain of a route a discrete ID.
> > Makes it a lot easier to map, rather than figuring out what 'choice43'
> is!
>
> Agreed this would help.  I will implement them right away.   The problem
> is, to get the verbose logging, I have to tell camel that the exceptions
> are not handled and if I do that then the whole batch stops when an
> exception happens.  I need a way of printing the verbose logging, like in
> the original ticket message, but without stopping the world when they
> happen.  Do you know how to do that?
>
> Thanks for your help.
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
> http://camel.465427.n5.nabble.com/Help-diagnosing-camel-
> exception-tp5796669p5798451.html
> To start a new topic under Camel - Users, email ml+s465427n465428h31@n5.
> nabble.com
> To unsubscribe from Camel - Users, click here
> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=465428&code=c291Y2lhbmNlLmVxZGFtLnJhc2h0aUBnbWFpbC5jb218NDY1NDI4fDE1MzI5MTE2NTY=>
> .
> NAML
> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>




--
View this message in context: http://camel.465427.n5.nabble.com/Help-diagnosing-camel-exception-tp5796669p5798460.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message