Hi Ashwin,
I am also facing the same issue.
The solution that you have given works only if camel is configured as a
Spring bean.
However, in my case, it is not configured as a Spring bean.
In this scenario, how do I get hold of the existing camel context when
I am using Java DSL and not Spring D
No, source MQ queue and error MQ queue are different.
First I tried with single JMS "wmq" only. It didn't work so I thought of
creating two - one for regular consumer and another for error queue. However,
that didn't work either.
Unfortunately due to restriction put here, I cannot send whole XM
Yes, onException is being called. As you see in the onException, exceptionPrint
method is getting called fine. ""
It is just not writing to the error queue.
Regards,
Nishant
From: Willem.Jiang [via Camel] [mailto:ml-node+s465427n5716571...@n5.nabble.com]
Sent: Saturday, July 28, 2012 6:57 AM
To
If you want to donate this component to Apache Camel (and you have the
right to do this), please raise a JIRA [1] and attach a patch (make sure
you grant the rights to Apache). As you may know, we love contributions
[2]... ;-)
[1] https://issues.apache.org/jira/browse/CAMEL
[2] http://camel.apache
If your doStart() method throws an exception, the application will not
start [1].
If your poll() method throws an exception, Camel will retry until the retry
count is exceeded. Than the route will stop polling [2].
[1]
https://svn.apache.org/repos/asf/camel/trunk/camel-core/src/main/java/org/apach
Hello,
The reason that camel does not stop the route directly is that there
are inflight messages in the route.
Setting the timeout to 1 will shorten the time camel wait for the
inflight messages to be processed so there is a risk that by doing
this messages will be lost.
Another approch could be
Hi All,
We've been using Camel and CouchDB successfully for 6 months on one of
our platforms at work. There was no CouchDB component that I could
find at the time, so I wrote one. I still cannot find one, so I've
open sourced mine.
You can find it here:
https://github.com/sksamuel/camel-couchdb
Do you try to stop the route running the same thread? You should do it in a
different thread.
Best,
Christian
On Sun, Jul 29, 2012 at 2:14 PM, soumya_sd wrote:
> I found a solution for this.
>
> I added the following and now the Camel forces the route to shutdown in 1
> seconds (timeout time) i
Hello Joe,
Provided that you do not have the routes set up to have
autoStartup(false) I do not believe you will have to call
camelContext.startRoute(..).
I agree that it is strange that the first route seem to shutdown
directly. Could you post some more information about your routes or
even a sma
Hi
I have a custom endpoint/component. The consumer is a scheduledpollconsumer.
I had a quick question on the behaviour of the *doStart() *and *poll()
*methods which I implement in my consumer.
Basically, the implementation of these 2 methods which I have provided in my
consumer do quite a bit of
Hi Folks
Thanks for all the helpful responses on this item.
Basically, I followed an approach similar to what Pontus outlined above.
However, I have noted some strange behavior. When my application has started
up the routes get added as follows:
*context.addRoutes(new RouteBuilder().*
Aft
I can update camelwatch to add in extra properties, or you could
update the project and do a pull request.
On Sat, Jul 28, 2012 at 7:45 PM, Bob Jolliffe wrote:
> Ah .. just realized that if I cast my CamelContext to a
> ModelCamelContext I can do all I need to do with RouteDefinitions
> (rather t
I found a solution for this.
I added the following and now the Camel forces the route to shutdown in 1
seconds (timeout time) instead of the default 300 seconds.
--
View this message in context:
http://camel.465427.n5.nabble.com/Options-for-creating-dyna
13 matches
Mail list logo
