Could you share you’re blueprint XML files? I use Blueprint + Karaf
extensively, and I’ve always got into trouble if I mistakenly use the Spring
namespace. I’d be interested to see what is different about your Blueprint XML
files.
> On Mar 9, 2017, at 8:24 AM, kumar wrote:
>
>
> I found th
I have a route similar to the following:
Everything once in a while I get the ExchangeTimedOutException, but I do not
know from which route segment the ExchangeTimedOutException is happening.
Does anyone know how to determine where the timeout is actually occurring?
--
View this message in c
You could try to use the exchange property ${property.CamelFailureEndpoint}
and ${property.CamelFailureRouteId} to determine which route and endpoint
failed.
On Tue, Mar 21, 2017 at 4:40 PM, catequil [via Camel] <
ml-node+s465427n5795836...@n5.nabble.com> wrote:
> I have a route similar to the fo
Are you using a transacted session with ActiveMQ?
> On Mar 20, 2017, at 12:49 PM, hammod wrote:
>
> I am receiving a message from a client using a netty interface and this
> message should be sent to ActiveMQ to be saved.
> All is good but if I dropped the connection between camel and ActiveMQ
Could you define route A to send the message to an intermediary (vm endpoint,
jms, seda) and then have the other routes consume from there?
> On Mar 8, 2017, at 4:54 AM, vonezzz <34618...@qq.com> wrote:
>
> i want to use two routedefine,not one route.
>
>
>
> --
> View this message in contex
Anyone have feedback on the patched version?
Manual testing with the patched version in our product was successful,
basically just starting/stopping the database and observing that the
component was always able to reconnect. Without this change it continues to
throw the exception first reported
Those pieces of information were too general. It reported
"seda:processItemsJob" as the endpoint, but there is a lot of segments in
that area. Any other suggestions? The other problem I am having is because
of the parallel processing the log messages are getting all tangled
together. It would be
Made slight mods on the route and it worked. Thanks
@Override
public void configure() throws Exception {
* JaxbDataFormat searchXmlRequestJaxb= new JaxbDataFormat();
searchXmlRequestJaxb.setContext(JAXBContext.newInstance(com.trvl.integration.domain.busbooking.tbo.search.xmlob
I was hoping the messageHistory might have enough information in it to give
me an idea of where to look.
Added the following code to my TimeOutErrorProcessor
When I finally got the exception this is what it printed out:
Is there any way to get a more descriptive Node identifier rather than to,
So what I discovered is this message history is the history starting from the
onException. Which does not help me. I need the history from the original
route before the exception occurred or maybe the whole route history to help
me discover where this timeout is occurring. Or maybe we could reco
My Blueprint XML files has beans defined and Camel Context defined in it.
remaining are routes files. with camel namespace
Best Regards
Kumar Phani: Touchpeak Software
cell: +65 9821 8689
email: ku...@touchpeak.com
On Tue, Mar 21, 2017 at 10:18 PM, Quinn Stevenson [via Camel] <
ml-node+s465427n57
11 matches
Mail list logo
