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 17:08:39 GMT
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+s465427n5798424h7@n5.nabble.com>:

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
interesting routes.  I've attempted to simplify them somewhat so the
original error logs may not reflect the current code.  I would if you have
time concentrate on the reply messages that I sent most recently instead.
Sorry if it confused you.  I tried to comment in the code what things are
doing so I did not have to send you the whole code base.  The important
thing to look at now would be the recent logs I messaged along with the
code.  The TimeOutErrorProcessor is implementing some of your suggestions
for the logs that is why I included it.  I sent you two routes, but the
second one is the most interesting as that is where the time out occurs.
See "//start of problem area".  I am just not sure which node.  I'm leaning
that it is the call externally, but since it never prints some of the log
entries I am not sure.  See success log example vs failure log example.
You will see that some of the log entries that should be printing out are
not and are skipped, but then when it gets to the "saveDeviceUsageHistory'
it starts logging again.  There are stop and end log entries inside of
every Processor/Bean node entry so that I can see when it is starting and
ending a node.  You can see this by looking at the successful log.

Sorry for the novel,  I hope you can help me.  And thanks for your time.

------------------------------
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-tp5796669p5798424.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-tp5796669p5798426.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message