You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Ryan T <br...@yahoo.com> on 2017/03/28 22:04:50 UTC
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
Posted by Ryan T <br...@yahoo.com>.
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 expected that once it handled the exception it would continue to
process the rest of the nodes. I mean the whole point of putting all the
extra logging nodes into the route was to attempt to identify the actual
node having the timeout. But I am no closer to solving this.
Thanks for any help you might be able to provide.
--
View this message in context: http://camel.465427.n5.nabble.com/Help-diagnosing-camel-exception-tp5796669p5798261.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Help diagnosing camel exception
Posted by Ryan T <br...@yahoo.com>.
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 to
me that it is an external pause of some sort or maybe a GC happens.
Although the GC does not quite make sense either because other processes do
not pause at the same time from what I can see. I have had these timeouts
happen on single API calls too. Not just the batch jobs. It sure smells of
network issues to me. I want to eliminate the carriers(ATT, Verizon, etc)
as it happens regardless of carrier API I am hitting. If I were to narrow
down to what things it could be, I would say it is either network issues, a
problem in CXF(Camel), or a problem in the marshalling
JacksonXML/Json(Camel).
--
View this message in context: http://camel.465427.n5.nabble.com/Help-diagnosing-camel-exception-tp5796669p5798467.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Help diagnosing camel exception
Posted by souciance <so...@gmail.com>.
Hi Ryan
I agree with Paul. It is quit hard to troubleshoot those complicated
routes. It would be easier if you can break them into smaller and more
independent routes which can be tested easier.
I would also enable this class which is the AuditEventNotifier which will
give more detailed information about each step that is being executed.
http://camel.apache.org/eventnotifier-to-log-details-about-all-sent-exchanges.html
Essentially I think a call to MongoDB or some other third party system is
taking more than the allowed timeout value. Either increase the timeout and
see if the problem goes away or perhaps it could be worth run some sort of
a load test using JMeter to trigger those timeouts and then see exactly
which record is causing this happen.
Best
Souciance
<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 8:23 PM, Paul Gale [via Camel] <
ml+s465427n5798429h62@n5.nabble.com> wrote:
> Hi Ryan,
>
> It seems to be that you'd be better off breaking up some of those routes;
> they seem very large and monolithic. Prefer composed routes instead, each
> with discrete error handlers. Currently you're looking for a fault through
> a large slice of functionality. The use of the doCatch clauses is alluding
> to the fact that these routes need to be broken up. With a larger number
> of
> smaller composed routes it will bring greater focus to your error
> detection/handling. Same concept behind keeping regular method sizes
> small.
>
> Can you explain why some of the individual processor nodes in each route
> have processing times in the order of an hour or more!?
>
> 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!
>
> How are you testing these routes? What unit tests do you have for these
> routes?
>
> Thanks,
> Paul
>
> On Thu, Apr 27, 2017 at 1:59 PM, Ryan T <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=5798429&i=0>> wrote:
>
> > 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.
> >
>
>
> ------------------------------
> 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-tp5796669p5798429.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-tp5796669p5798436.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Help diagnosing camel exception
Posted by Ryan T <br...@yahoo.com>.
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 of the
route.
It is going into this portion of code which is why I included both routes as
this is in the parent route.
Do you think that the error message might be more plain and/or helpful if I
moved this onException into the seda routes? Is the fact that the
onException is in the parent route hiding important information do you
think?
--
View this message in context: http://camel.465427.n5.nabble.com/Help-diagnosing-camel-exception-tp5796669p5798468.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Help diagnosing camel exception
Posted by souciance <so...@gmail.com>.
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.
Re: Help diagnosing camel exception
Posted by Ryan T <br...@yahoo.com>.
> 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.
--
View this message in context: http://camel.465427.n5.nabble.com/Help-diagnosing-camel-exception-tp5796669p5798451.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Help diagnosing camel exception
Posted by Paul Gale <pa...@gmail.com>.
Hi Ryan,
It seems to be that you'd be better off breaking up some of those routes;
they seem very large and monolithic. Prefer composed routes instead, each
with discrete error handlers. Currently you're looking for a fault through
a large slice of functionality. The use of the doCatch clauses is alluding
to the fact that these routes need to be broken up. With a larger number of
smaller composed routes it will bring greater focus to your error
detection/handling. Same concept behind keeping regular method sizes small.
Can you explain why some of the individual processor nodes in each route
have processing times in the order of an hour or more!?
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!
How are you testing these routes? What unit tests do you have for these
routes?
Thanks,
Paul
On Thu, Apr 27, 2017 at 1:59 PM, Ryan T <br...@yahoo.com> wrote:
> 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.
>
Re: Help diagnosing camel exception
Posted by Ryan T <br...@yahoo.com>.
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.
Re: Help diagnosing camel exception
Posted by souciance <so...@gmail.com>.
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.
Re: Help diagnosing camel exception
Posted by Ryan T <br...@yahoo.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.
--
View this message in context: http://camel.465427.n5.nabble.com/Help-diagnosing-camel-exception-tp5796669p5798424.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Help diagnosing camel exception
Posted by souciance <so...@gmail.com>.
Hello,
Not the easiest route to follow ;) But basically the log seems to say that
you are doing a synchronous action over some protocol and waiting for a
response. You fail to get the response within 30000 milliseconds so you get
a timeout exception. I suspect it is in the bean(iJobService) based on the
logs but can't confirm. Do you do any calls to third party systems in that
bean?
Best
Souciance
On Thu, Apr 27, 2017 at 1:08 AM, Ryan T [via Camel] <
ml+s465427n5798367h40@n5.nabble.com> wrote:
> More code that might help in diagnosing the issue. What do you think
> could be happening?
>
> public class TimeOutErrorProcessor implements Processor {
>
> private static final Logger LOGGER = LogManager.getLogger(TimeOutErrorProcessor.class.getName());
>
> public TimeOutErrorProcessor() {
> // Empty Constructor
> }
>
> @Override
> public void process(Exchange exchange) throws Exception {
>
> LOGGER.debug("Begin:TimeOutErrorProcessor");
> String trackingId = "";
>
> final List<DeviceInformation> timeOutList = (List<DeviceInformation>) exchange.getProperty(IConstant.TIMEOUT_DEVICE_LIST);
> final DeviceInformation deviceInformation = (DeviceInformation) exchange.getIn().getBody();
> trackingId = "[" + deviceInformation.getNetSuiteId() + "] - ";
> printTimeoutDetails(exchange, trackingId);
> LOGGER.warn(trackingId + " NetSuite Id of timeOut Device is................" + deviceInformation.getNetSuiteId());
>
> timeOutList.add(deviceInformation);
> exchange.setProperty(IConstant.TIMEOUT_DEVICE_LIST, timeOutList);
>
> LOGGER.debug("End:TimeOutErrorProcessor");
> }
>
> private static void printTimeoutDetails(Exchange exchange, String midwayId) {
> LOGGER.warn(midwayId + " Id");
> LOGGER.warn(midwayId + " CamelFailureRouteId: " + exchange.getProperty("CamelFailureRouteId"));
> LOGGER.warn(midwayId + " CamelFailureEndpoint: " + exchange.getProperty("CamelFailureEndpoint"));
> RouteContext routeContext = (exchange.getUnitOfWork() == null || exchange.getUnitOfWork().getRouteContext() == null) ? null : exchange.getUnitOfWork().getRouteContext();
> String routeId = routeContext != null ? exchange.getUnitOfWork().getRouteContext().getRoute().getId() : "Unknown";
> LOGGER.warn(midwayId + " RouteId: " + routeId);
> final ExchangeTimedOutException ex = (ExchangeTimedOutException) exchange.getProperty(Exchange.EXCEPTION_CAUGHT);
> if (ex != null) {
> LOGGER.warn(midwayId + " Error: " + ex.getMessage(), ex);
> }
> LOGGER.warn(midwayId + " TimeOut exception occurred................" + exchange.getIn().getBody().toString());
> }
> }
>
>
>
> ------------------------------
> 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-tp5796669p5798367.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-tp5796669p5798401.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Help diagnosing camel exception
Posted by Ryan T <br...@yahoo.com>.
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
Posted by souciance <so...@gmail.com>.
Can you share your code?
Also I think it would be good to have some sort of a error handler route
where you log errors. You can log these parts to get better info where
something failed.
setHeader("CamelExceptionCaught", simple("Exception Object:
${property.CamelExceptionCaught}"))
.setHeader("CamelStacktrace", simple("${exception.stacktrace}"))
.setHeader("ExceptionMessage", simple("${exception.message}"))
.setHeader("CamelFailureEndpoint",
simple("${property.CamelFailureEndpoint}"))
.setHeader("CamelFailureRouteId", simple("${property.CamelFailureRouteId}"))
On Wed, Mar 29, 2017 at 11:17 PM, Ryan T [via Camel] <
ml-node+s465427n5796719h52@n5.nabble.com> wrote:
> 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 being received in time. When this happens my whole job
> stops processing and does not finish. Am I just not seeing the obvious or
> is there something I need to change in my route to be able to identify the
> actual part or node this is occurring in?
>
> Thanks
> Ryan
>
> ------------------------------
> 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-tp5796669p5796719.html
> To start a new topic under Camel - Users, email
> ml-node+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-tp5796669p5796725.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Help diagnosing camel exception
Posted by Ryan T <br...@yahoo.com>.
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 being received in time. When this happens my whole job stops
processing and does not finish. Am I just not seeing the obvious or is
there something I need to change in my route to be able to identify the
actual part or node this is occurring in?
Thanks
Ryan
--
View this message in context: http://camel.465427.n5.nabble.com/Help-diagnosing-camel-exception-tp5796669p5796719.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Help diagnosing camel exception
Posted by souciance <so...@gmail.com>.
According to the log you are not receiving the out message in time so it
times out.
Caused by: org.apache.camel.ExchangeTimedOutException: The OUT message
was not received within: 30000 millis.
Exchange[ID-mid1-34304-1490639453105-0-772494]
On Wed, Mar 29, 2017 at 12:04 AM, Ryan T [via Camel] <
ml-node+s465427n5796669h2@n5.nabble.com> wrote:
> can anyone help me on diagnosing this exception? Any hints as to how I
> might proceed on fixing it?
>
> 2017-03-28 09:05:08 ERROR DefaultErrorHandler:156 - Failed delivery for (MessageId: ID-mid1-34304-1490639453105-0-816855 on ExchangeId: ID-mid1-34304-1490639453105-0-816856). Exhausted after delivery attempt: 0 caught: null
>
> Message History
> ---------------------------------------------------------------------------------------------------------------------------------------
> RouteId ProcessorId Processor Elapsed (ms)
> [startJob ] [startJob ] [direct://startJob ] [ 3908102]
> [startJob ] [to111 ] [direct:processJob ] [ 3908100]
> [processJob ] [onCompletion4 ] [onCompletion ] [ 0]
> [processJob ] [insertJobDetails ] [bean[com.xyzcompany.appname.service.impl.JobServiceImpl@1a8962a4] ] [ 136]
> [processJob ] [bean233 ] [bean[com.xyzcompany.appname.service.impl.JobServiceImpl@1a8962a4] ] [ 0]
> [processJob ] [fetchDevices ] [bean[com.xyzcompany.appname.service.impl.JobServiceImpl@1a8962a4] ] [ 18189]
> [processJob ] [choice43 ] [when[simple{Simple: ${exchangeProperty[jobName]} == 'CONNECTION_HISTORY' ] [ 0]
> [processJob ] [bean235 ] [bean[com.xyzcompany.appname.service.impl.JobServiceImpl@1a8962a4] ] [ 0]
> [processJob ] [log36 ] [log ] [ 1]
> [processJob ] [choice44 ] [when[simple{Simple: ${exchangeProperty[jobName]} == 'CONNECTION_HISTORY' ] [ 3889773]
> [processJob ] [split23 ] [split[bean[com.xyzcompany.appname.splitter.JobSplitter]] ] [ 3889773]
> [processJob ] [process146 ] [Processor@0x3a51bfb7 ] [ 1]
>
> 2017-03-28 09:05:08 ERROR DefaultErrorHandler:156 - Failed delivery for (MessageId: ID-mid1-34304-1490639453105-0-816855 on ExchangeId: ID-mid1-34304-1490639453105-0-816856). Exhausted after delivery attempt: 0 caught: null
>
> Message History
> ---------------------------------------------------------------------------------------------------------------------------------------
> RouteId ProcessorId Processor Elapsed (ms)
> [startJob ] [startJob ] [direct://startJob ] [ 3908105]
> [startJob ] [to111 ] [direct:processJob ] [ 3908100]
> [processJob ] [onCompletion4 ] [onCompletion ] [ 0]
> [processJob ] [insertJobDetails ] [bean[com.xyzcompany.appname.service.impl.JobServiceImpl@1a8962a4] ] [ 136]
> [processJob ] [bean233 ] [bean[com.xyzcompany.appname.service.impl.JobServiceImpl@1a8962a4] ] [ 0]
> [processJob ] [fetchDevices ] [bean[com.xyzcompany.appname.service.impl.JobServiceImpl@1a8962a4] ] [ 18189]
> [processJob ] [choice43 ] [when[simple{Simple: ${exchangeProperty[jobName]} == 'CONNECTION_HISTORY' ] [ 0]
> [processJob ] [bean235 ] [bean[com.xyzcompany.appname.service.impl.JobServiceImpl@1a8962a4] ] [ 0]
> [processJob ] [log36 ] [log ] [ 1]
> [processJob ] [choice44 ] [when[simple{Simple: ${exchangeProperty[jobName]} == 'CONNECTION_HISTORY' ] [ 3889773]
> [processJob ] [split23 ] [split[bean[com.xyzcompany.appname.splitter.JobSplitter]] ] [ 3889773]
> [processJob ] [process146 ] [Processor@0x3a51bfb7 ] [ 1]
> [processJob ] [log33 ] [log ] [ 0]
>
> 2017-03-28 09:05:08 ERROR DefaultErrorHandler:156 - Failed delivery for (MessageId: ID-mid1-34304-1490639453105-0-816855 on ExchangeId: ID-mid1-34304-1490639453105-0-816856). Exhausted after delivery attempt: 0 caught: null
>
> Message History
> ---------------------------------------------------------------------------------------------------------------------------------------
> RouteId ProcessorId Processor Elapsed (ms)
> [startJob ] [startJob ] [direct://startJob ] [ 3908111]
> [startJob ] [to111 ] [direct:processJob ] [ 3908100]
> [processJob ] [onCompletion4 ] [onCompletion ] [ 0]
> [processJob ] [insertJobDetails ] [bean[com.xyzcompany.appname.service.impl.JobServiceImpl@1a8962a4] ] [ 136]
> [processJob ] [bean233 ] [bean[com.xyzcompany.appname.service.impl.JobServiceImpl@1a8962a4] ] [ 0]
> [processJob ] [fetchDevices ] [bean[com.xyzcompany.appname.service.impl.JobServiceImpl@1a8962a4] ] [ 18189]
> [processJob ] [choice43 ] [when[simple{Simple: ${exchangeProperty[jobName]} == 'CONNECTION_HISTORY' ] [ 0]
> [processJob ] [bean235 ] [bean[com.xyzcompany.appname.service.impl.JobServiceImpl@1a8962a4] ] [ 0]
> [processJob ] [log36 ] [log ] [ 1]
> [processJob ] [choice44 ] [when[simple{Simple: ${exchangeProperty[jobName]} == 'CONNECTION_HISTORY' ] [ 3889773]
> [processJob ] [split23 ] [split[bean[com.xyzcompany.appname.splitter.JobSplitter]] ] [ 3889773]
> [processJob ] [process146 ] [Processor@0x3a51bfb7 ] [ 1]
> [processJob ] [log33 ] [log ] [ 0]
> [processJob ] [log34 ] [log ] [ 0]
>
> 2017-03-28 09:05:08 ERROR DefaultErrorHandler:156 - Failed delivery for (MessageId: ID-mid1-34304-1490639453105-0-816855 on ExchangeId: ID-mid1-34304-1490639453105-0-816856). Exhausted after delivery attempt: 0 caught: null
> Message History
> ---------------------------------------------------------------------------------------------------------------------------------------
> RouteId ProcessorId Processor Elapsed (ms)
> [startJob ] [startJob ] [direct://startJob ] [ 3908116]
> [startJob ] [to111 ] [direct:processJob ] [ 3908100]
> [processJob ] [onCompletion4 ] [onCompletion ] [ 0]
> [processJob ] [insertJobDetails ] [bean[com.xyzcompany.appname.service.impl.JobServiceImpl@1a8962a4] ] [ 136]
> [processJob ] [bean233 ] [bean[com.xyzcompany.appname.service.impl.JobServiceImpl@1a8962a4] ] [ 0]
> [processJob ] [fetchDevices ] [bean[com.xyzcompany.appname.service.impl.JobServiceImpl@1a8962a4] ] [ 18189]
> [processJob ] [choice43 ] [when[simple{Simple: ${exchangeProperty[jobName]} == 'CONNECTION_HISTORY' ] [ 0]
> [processJob ] [bean235 ] [bean[com.xyzcompany.appname.service.impl.JobServiceImpl@1a8962a4] ] [ 0]
> [processJob ] [log36 ] [log ] [ 1]
> [processJob ] [choice44 ] [when[simple{Simple: ${exchangeProperty[jobName]} == 'CONNECTION_HISTORY' ] [ 3889773]
> [processJob ] [split23 ] [split[bean[com.xyzcompany.appname.splitter.JobSplitter]] ] [ 3889773]
> [processJob ] [process146 ] [Processor@0x3a51bfb7 ] [ 1]
> [processJob ] [log33 ] [log ] [ 0]
> [processJob ] [log34 ] [log ] [ 0]
> [processJob ] [bean229 ] [bean[com.xyzcompany.appname.service.impl.JobServiceImpl@1a8962a4] ] [ 0]
>
> 2017-03-28 09:05:08 ERROR DefaultErrorHandler:156 - Failed delivery for (MessageId: ID-mid1-34304-1490639453105-0-816855 on ExchangeId: ID-mid1-34304-1490639453105-0-816856). Exhausted after delivery attempt: 0 caught: null
>
> Message History
> ---------------------------------------------------------------------------------------------------------------------------------------
> RouteId ProcessorId Processor Elapsed (ms)
> [startJob ] [startJob ] [direct://startJob ] [ 3908122]
> [startJob ] [to111 ] [direct:processJob ] [ 3908100]
> [processJob ] [onCompletion4 ] [onCompletion ] [ 0]
> [processJob ] [insertJobDetails ] [bean[com.xyzcompany.appname.service.impl.JobServiceImpl@1a8962a4] ] [ 136]
> [processJob ] [bean233 ] [bean[com.xyzcompany.appname.service.impl.JobServiceImpl@1a8962a4] ] [ 0]
> [processJob ] [fetchDevices ] [bean[com.xyzcompany.appname.service.impl.JobServiceImpl@1a8962a4] ] [ 18189]
> [processJob ] [choice43 ] [when[simple{Simple: ${exchangeProperty[jobName]} == 'CONNECTION_HISTORY' ] [ 0]
> [processJob ] [bean235 ] [bean[com.xyzcompany.appname.service.impl.JobServiceImpl@1a8962a4] ] [ 0]
> [processJob ] [log36 ] [log ] [ 1]
> [processJob ] [choice44 ] [when[simple{Simple: ${exchangeProperty[jobName]} == 'CONNECTION_HISTORY' ] [ 3889773]
> [processJob ] [split23 ] [split[bean[com.xyzcompany.appname.splitter.JobSplitter]] ] [ 3889773]
> [processJob ] [process146 ] [Processor@0x3a51bfb7 ] [ 1]
> [processJob ] [log33 ] [log ] [ 0]
> [processJob ] [log34 ] [log ] [ 0]
> [processJob ] [bean229 ] [bean[com.xyzcompany.appname.service.impl.JobServiceImpl@1a8962a4] ] [ 0]
> [processJob ] [bean230 ] [bean[com.xyzcompany.appname.service.impl.JobServiceImpl@1a8962a4] ] [ 0]
>
> 2017-03-28 09:05:08 ERROR DefaultErrorHandler:156 - Failed delivery for (MessageId: ID-mid1-34304-1490639453105-0-816855 on ExchangeId: ID-mid1-34304-1490639453105-0-816856). Exhausted after delivery attempt: 0 caught: null
>
> Message History
> ---------------------------------------------------------------------------------------------------------------------------------------
> RouteId ProcessorId Processor Elapsed (ms)
> [startJob ] [startJob ] [direct://startJob ] [ 3908126]
> [startJob ] [to111 ] [direct:processJob ] [ 3908100]
> [processJob ] [onCompletion4 ] [onCompletion ] [ 0]
> [processJob ] [insertJobDetails ] [bean[com.xyzcompany.appname.service.impl.JobServiceImpl@1a8962a4] ] [ 136]
> [processJob ] [bean233 ] [bean[com.xyzcompany.appname.service.impl.JobServiceImpl@1a8962a4] ] [ 0]
> [processJob ] [fetchDevices ] [bean[com.xyzcompany.appname.service.impl.JobServiceImpl@1a8962a4] ] [ 18189]
> [processJob ] [choice43 ] [when[simple{Simple: ${exchangeProperty[jobName]} == 'CONNECTION_HISTORY' ] [ 0]
> [processJob ] [bean235 ] [bean[com.xyzcompany.appname.service.impl.JobServiceImpl@1a8962a4] ] [ 0]
> [processJob ] [log36 ] [log ] [ 1]
> [processJob ] [choice44 ] [when[simple{Simple: ${exchangeProperty[jobName]} == 'CONNECTION_HISTORY' ] [ 3889773]
> [processJob ] [split23 ] [split[bean[com.xyzcompany.appname.splitter.JobSplitter]] ] [ 3889773]
> [processJob ] [process146 ] [Processor@0x3a51bfb7 ] [ 1]
> [processJob ] [log33 ] [log ] [ 0]
> [processJob ] [log34 ] [log ] [ 0]
> [processJob ] [bean229 ] [bean[com.xyzcompany.appname.service.impl.JobServiceImpl@1a8962a4] ] [ 0]
> [processJob ] [bean230 ] [bean[com.xyzcompany.appname.service.impl.JobServiceImpl@1a8962a4] ] [ 0]
> [processJob ] [doTry20 ] [doTry ] [ 0]
>
> 2017-03-28 09:05:08 ERROR DefaultErrorHandler:204 - Failed delivery for (MessageId: ID-mid1-34304-1490639453105-0-410760 on ExchangeId: ID-mid1-34304-1490639453105-0-410761). Exhausted after delivery attempt: 1 caught: org.apache.camel.CamelExecutionException: Exception occurred during execution on the exchange: Exchange[ID-mid1-34304-1490639453105-0-410763]. Processed by failure processor: FatalFallbackErrorHandler[Channel[BeanProcessor[com.xyzcompany.appname.service.impl.AuditServiceImpl(0x693f196c)]]]
>
> Message History
> ---------------------------------------------------------------------------------------------------------------------------------------
> RouteId ProcessorId Processor Elapsed (ms)
> [route2 ] [route2 ] [quartz2://job/deviceDetailsUsageTimer24?cron=0+0+08+*+*+%3F&trigger.mis ] [ 3908276]
> [route2 ] [bean178 ] [bean[com.xyzcompany.appname.service.impl.JobServiceImpl@1a8962a4] ] [ 3]
> [route2 ] [bean179 ] [bean[com.xyzcompany.appname.service.impl.JobServiceImpl@1a8962a4] ] [ 3908273]
> [ ] [bean1 ] [bean[com.xyzcompany.appname.service.impl.AuditServiceImpl@693f196c] ] [ 140]
>
> Stacktrace
> ---------------------------------------------------------------------------------------------------------------------------------------
> org.apache.camel.CamelExecutionException: Exception occurred during execution on the exchange: Exchange[ID-mid1-34304-1490639453105-0-410763]
> at org.apache.camel.util.ObjectHelper.wrapCamelExecutionException(ObjectHelper.java:1706) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.util.ExchangeHelper.extractResultBody(ExchangeHelper.java:660) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.impl.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:471) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:133) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:149) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.impl.DefaultProducerTemplate.requestBody(DefaultProducerTemplate.java:301) ~[camel-core-2.17.6.jar:2.17.6]
> at com.xyzcompany.appname.service.impl.JobServiceImpl.scheduleJob(JobServiceImpl.java:241) ~[classes/:?]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
> at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
> at org.apache.camel.component.bean.MethodInfo.invoke(MethodInfo.java:408) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.component.bean.MethodInfo$1.doProceed(MethodInfo.java:279) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.component.bean.MethodInfo$1.proceed(MethodInfo.java:252) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.component.bean.BeanProcessor.process(BeanProcessor.java:177) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:468) [camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197) [camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:121) [camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:83) [camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197) [camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.processor.loadbalancer.QueueLoadBalancer.process(QueueLoadBalancer.java:44) [camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:109) [camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.processor.loadbalancer.LoadBalancerSupport.process(LoadBalancerSupport.java:97) [camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.component.quartz2.CamelJob.execute(CamelJob.java:58) [camel-quartz2-2.17.6.jar:2.17.6]
> at org.quartz.core.JobRunShell.run(JobRunShell.java:202) [quartz-2.2.2.jar:?]
> at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573) [quartz-2.2.2.jar:?]
> Caused by: org.apache.camel.ExchangeTimedOutException: The OUT message was not received within: 30000 millis. Exchange[ID-mid1-34304-1490639453105-0-772494]
> at org.apache.camel.component.seda.SedaProducer.process(SedaProducer.java:145) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.processor.SendProcessor.process(SendProcessor.java:145) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:468) [camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:468) [camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:109) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.processor.MulticastProcessor.doProcessParallel(MulticastProcessor.java:827) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.processor.MulticastProcessor.access$200(MulticastProcessor.java:85) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.processor.MulticastProcessor$1.call(MulticastProcessor.java:320) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.processor.MulticastProcessor$1.call(MulticastProcessor.java:305) ~[camel-core-2.17.6.jar:2.17.6]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_45]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[?:1.8.0_45]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[?:1.8.0_45]
> at java.lang.Thread.run(Thread.java:745) ~[?:1.8.0_45]
> 2017-03-28 09:05:08 ERROR CamelJob:65 - Error processing exchange. Exchange[ID-mid1-34304-1490639453105-0-410761]. Caused by: [org.quartz.JobExecutionException - org.apache.camel.CamelExecutionException: Exception occurred during execution on the exchange: Exchange[ID-mid1-34304-1490639453105-0-410763]]
> 2017-03-28 09:05:08 INFO JobRunShell:207 - Job job.deviceDetailsUsageTimerVerizon24 threw a JobExecutionException:
> org.quartz.JobExecutionException: org.apache.camel.CamelExecutionException: Exception occurred during execution on the exchange: Exchange[ID-mid1-34304-1490639453105-0-410763]
> at org.apache.camel.component.quartz2.CamelJob.execute(CamelJob.java:61) ~[camel-quartz2-2.17.6.jar:2.17.6]
> at org.quartz.core.JobRunShell.run(JobRunShell.java:202) [quartz-2.2.2.jar:?]
> at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573) [quartz-2.2.2.jar:?]
> Caused by: org.apache.camel.CamelExecutionException: Exception occurred during execution on the exchange: Exchange[ID-mid1-34304-1490639453105-0-410763]
> at org.apache.camel.util.ObjectHelper.wrapCamelExecutionException(ObjectHelper.java:1706) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.util.ExchangeHelper.extractResultBody(ExchangeHelper.java:660) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.impl.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:471) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:133) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:149) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.impl.DefaultProducerTemplate.requestBody(DefaultProducerTemplate.java:301) ~[camel-core-2.17.6.jar:2.17.6]
> at com.xyzcompany.appname.service.impl.JobServiceImpl.scheduleJob(JobServiceImpl.java:241) ~[classes/:?]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
> at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
> at org.apache.camel.component.bean.MethodInfo.invoke(MethodInfo.java:408) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.component.bean.MethodInfo$1.doProceed(MethodInfo.java:279) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.component.bean.MethodInfo$1.proceed(MethodInfo.java:252) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.component.bean.BeanProcessor.process(BeanProcessor.java:177) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:468) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:121) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:83) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.processor.loadbalancer.QueueLoadBalancer.process(QueueLoadBalancer.java:44) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:109) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.processor.loadbalancer.LoadBalancerSupport.process(LoadBalancerSupport.java:97) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.component.quartz2.CamelJob.execute(CamelJob.java:58) ~[camel-quartz2-2.17.6.jar:2.17.6]
> ... 2 more
> Caused by: org.apache.camel.ExchangeTimedOutException: The OUT message was not received within: 30000 millis. Exchange[ID-mid1-34304-1490639453105-0-772494]
> at org.apache.camel.component.seda.SedaProducer.process(SedaProducer.java:145) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.processor.SendProcessor.process(SendProcessor.java:145) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:468) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:468) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:109) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.processor.MulticastProcessor.doProcessParallel(MulticastProcessor.java:827) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.processor.MulticastProcessor.access$200(MulticastProcessor.java:85) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.processor.MulticastProcessor$1.call(MulticastProcessor.java:320) ~[camel-core-2.17.6.jar:2.17.6]
> at org.apache.camel.processor.MulticastProcessor$1.call(MulticastProcessor.java:305) ~[camel-core-2.17.6.jar:2.17.6]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_45]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[?:1.8.0_45]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[?:1.8.0_45]
> at java.lang.Thread.run(Thread.java:745) ~[?:1.8.0_45]
>
>
>
>
>
>
> ------------------------------
> 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-tp5796669.html
> To start a new topic under Camel - Users, email
> ml-node+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-tp5796669p5796673.html
Sent from the Camel - Users mailing list archive at Nabble.com.