Hi,
I've run into a similar problem before:
We were receiving MQ request messages (meant for InOut exchanges) even though
we were disabling the replyTo and expected MQ datagram messages (InOnly). The
incoming JMS headers had an IBM-specific header set to indicate the message
type and we were
Hi,
I've just submitted a patch for the following issue:
https://issues.apache.org/jira/browse/CAMEL-4227
I've added more info to the issue comments, where I recommend a further
improvement to SedaProducer by making it inherit from DefaultAsyncProducer
directly instead of from CollectionProduc
Hi,
I've attached a unit test to the jira issue CAMEL-4332; it seems to be already
working.
>From the svn history, it looks like the NagiosProducer always did:
exchange.getIn().getBody(String.class);
which should trigger type conversion.
Can you confirm if your route still works without
Hi,
It sounds like Camel would definitely be good fit for the scenario you are
describing. It's the kind of integration problem that Camel is meant for!
You may be able to leverage some features of your JMS provider (have you
decided on one?) for the TTL since JMS messages can have a property
mel for it?
>
> Thanks in advance,
> Vitaly
>
> On Mon, Aug 29, 2011 at 12:11 AM, Mathieu Lalonde wrote:
> >
> > Hi,
> > It sounds like Camel would definitely be good fit for the scenario you are
> > describing. It's the kind of integration pro
Hi Jeevan,
It sounds like you need the Aggregator Enterprise Integration Pattern (EIP).
http://camel.apache.org/aggregator.html
Cheers,
Mathieu
> Date: Tue, 30 Aug 2011 09:53:26 -0700
> From: jeevan.koteshw...@gmail.com
> To: users@camel.apache.org
> Sub
Kal,
from("activemq:queue:myQueue") would typically create a message driven consumer.
I think you are on the right track with thoughts on polled endpoints.
I you are looking to consume messages when a state changes, you could generate
application events when that happens and use a pollEnrich(.
Hi,
I was wondering what was the best way to resubmit exchanges that did not get
aggregated within a given timeout.
from("direct:aggregate")
.aggregate(MyStrategy).completionSize(2).completionTimeout(..)
.to("mock:result");
It seems like the completionTimeout is to decide when the exchang
49:10 +0200
> Subject: Re: Aggregator - how to fail & resubmit if timeout expired
> To: users@camel.apache.org
>
> On Thu, Oct 20, 2011 at 2:30 PM, Mathieu Lalonde wrote:
> >
> > Hi,
> >
> > I was wondering what was the best way to resubmit exchanges that
Hi Tung,
Try removing the from your route.
Normally, for InOut, you should not send the response back explicitly. Camel
takes care of that for you. :)
Good luck.
Mathieu
> Date: Mon, 24 Oct 2011 18:21:02 +0200
> Subject: JMS request-reply and transac
, 25 Oct 2011 10:48:02 +0200
> Subject: Re: JMS request-reply and transactions
> From: wingtung.le...@gmail.com
> To: users@camel.apache.org
>
> On Tue, Oct 25, 2011 at 1:24 AM, Mathieu Lalonde wrote:
>
> > Try removing the from your route.
> > Normally, for I
Are you wrapping your connection factory in a SpringCachingConnection factory?
camel-jms uses Spring's Jms template which requires a connection factory that
pools or caches connections in order achieve good performance.
See the JMS template gotchas on the wiki for JMS component.
http://camel.apa
Are you sending your message through JMS?If so, the default behavior is to only
keep headers with primitive values and String, Date, BigInteger and primitive
wrappers...
I don't know if this can be customized...http://camel.apache.org/jms.html
Cheers,Mathieu
> From: zcalv...@motive.com
> To:
13 matches
Mail list logo