Actually Yogesh,
I may have just figured out my own answer here, and I have been fighting
this for months. I was operating under the assumption that I should be
stopping the route. And in all my tests I always stopped the route.
Figuring that if I was creating the object, i needed to take care
Thanks Yogesh.Well, sorta helps. The problem is that I have an
application running on Wildfly, not using Spring, and while i can create the
context run a route like the example shows, i have to provide the inputs
to the queue programatically, as the route isn't just sitting there waiting
for
I can kick-start a route (for example by a file or message/q or timer input)
automatically in Spring and read in a couple posts that doing this via a
pure Java DSL implementation was possible but still find no evidence of it.
Is this possible yet does anyone know? Or if anyone has gotten
I have a use-case of a message-driven bean intercepting a JMS message, then
triggering a Camel route inside another class. I currently have it sending
the message to the createRoute method, which then uses a producertemplate to
start the context, place the message on the first endpoint queue,
Well that turns out to be very interesting. Setting the timer to 1s and
sleep to 30s, it indeed runs the route 30 times! I am not sure I could
explain why it does that as I would think the route starting would include
running the timer continually, independent of code in the bean outside the
*Hi Ravi,*
I tried, but same results. Runs once but not again. Here are the log
entries for it. I even tried omitting the context.stop, no success...
7:32:12,460 INFO [org.apache.camel.impl.DefaultCamelContext] (default
task-4) Apache Camel 2.13.1 (CamelContext: camel-1) is starting
I can get routes kicked off in Java DSL however the timer routes execute once
and only once no matter what. Here is a sample of what I have, very
easy/simple. But it just fires once. Successfully, but just once.
Thanks for replying!
So this is interesting. I have implemented a timer via the Spring
configuration, however we are trying to get out of Spring and run in 100%
java. That said, if I had a timer running every second, or whatever, the
example is filling a queue for then a second route to pick up,
I have routes in the java DSL that grab messages from a queue and do things,
which works fine if I instantiate the class with the route in it, and it
runs it once.
What I need is a way to run routes in my appserver (Wildfly in this case),
which just sit pick up messages from a queue
