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 11:12:08 GMT
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.
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message