different thead
or should i implement the loging inside the stopping thread?
Thanks
--
View this message in context:
http://camel.465427.n5.nabble.com/Database-route-shutdown-tp5787725p5787860.html
Sent from the Camel - Users mailing list archive at Nabble.com.
ht and pending exchanges to complete? How can i avoid this
> situation? Also when i use
> context.getShutdownStrategy().setTimeout(30);
> it does not seems to change the timeout.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Database-route-shutdown-tp5787725.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
in context:
http://camel.465427.n5.nabble.com/Database-route-shutdown-tp5787725.html
Sent from the Camel - Users mailing list archive at Nabble.com.
chBeanException - No bean could be
>>>>> found in
>>>>> the registry for: myBean]
>>>>> org.apache.camel.NoSuchBeanException: No bean could be found in the
>>>>> registry for: myBean
>>>>> at
>>>>> org.apache.camel.component.bean.RegistryBean.getBean(RegistryBean.java:85)[94:org.apache.camel.camel-core:2.15.1]
>>>>> at
>>>>> org.apache.camel.component.bean.BeanProcessor.process(BeanProcessor.java:78)[94:org.apache.camel.camel-core:2.15.1]
>>>>>
>>>>>
>>>>> I have double-checked that bean "myBean" is still around at this point
>>>>> in
>>>>> time.
>>>>> It seems perhaps the bean is prematurely removed from the registry?
>>>>> Or the timer for some reason fires even though the route is in the
>>>>> middle
>>>>> shutting down?
>>>>>
>>>>> - Martin
>>
>>
--
View this message in context:
http://camel.465427.n5.nabble.com/Issue-with-timer-route-NoSuchBeanException-on-route-shutdown-tp5767470p5767649.html
Sent from the Camel - Users mailing list archive at Nabble.com.
This didn't make a difference.
However, something else I noticed. There is a second CamelContext defined in
the same Blueprint file.
This Camel context is shutdown first.
As it contains a from(jms:) endpoint, the shutdown takes a few secs (and that's why the
timer-based route in the "myRouteCon
Try remove the depends-on, not sure if blueprint shutdown in reverse
order and therefore the bean before camel etc.
On Tue, May 26, 2015 at 9:56 PM, Martin Lichtin
wrote:
> Using Blueprint in an OSGi bundle:
>
> class="myPkg.MyBean">
>
>
> http://camel.apache.org/schema/blueprint";
Using Blueprint in an OSGi bundle:
class="myPkg.MyBean">
http://camel.apache.org/schema/blueprint";
xsi:schemaLocation="http://camel.apache.org/schema/blueprint
http://camel.apache.org/schema/blueprint/camel-blueprint.xsd";
id="myRouteContext" depends-on="myBean">
Using Blueprint in an OSGi bundle:
http://camel.apache.org/schema/blueprint";
xsi:schemaLocation="http://camel.apache.org/schema/blueprint
http://camel.apache.org/schema/blueprint/camel-blueprint.xsd";
id="myRouteContext" depends-on="myBean">
Hi
Are you using a spring xml file? Then its spring app context that is
the registry. Camel does not remove any beans from it. Its spring that
does that. So maybe you have some depends-on spring attribute order
wrong or something.
On Tue, May 26, 2015 at 12:41 PM, Martin Lichtin
wrote:
> Is anyo
Is anyone else seeing this issue on shutting down a simple timer-based route
such as
On shutting down, it reports
2015-05-22 01:20:14,970 | INFO | FelixStartLevel |
DefaultShutdownStrategy | mel.impl.DefaultShutdownStrategy
'm missing
Here are the various snippets of relevant code...
The restartRoute method:
The Mina2 listener route:
The error handler setup code:
--
View this message in context:
http://camel.465427.n5.nabble.com/Route-shutdown-does-not-fully-cleanup-tp5765541.html
Sent from th
arning("got a message, which I don't understand")
}
}
--
View this message in context:
http://camel.465427.n5.nabble.com/akka-camel-route-shutdown-tp5762782.html
Sent from the Camel - Users mailing list archive at Nabble.com.
ontext:
> http://camel.465427.n5.nabble.com/java-util-concurrent-RejectedExecutionException-null-during-route-shutdown-tp5734160.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
:
http://camel.465427.n5.nabble.com/java-util-concurrent-RejectedExecutionException-null-during-route-shutdown-tp5734160.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Thanks Claus. I created
https://issues.apache.org/jira/browse/CAMEL-4514 for this issue. I
took your advice and suggested adding the callback to RoutePolicy,
especially since it already has an onInit(Route) method.
On Tue, Oct 4, 2011 at 11:51 AM, Claus Ibsen wrote:
> On Tue, Oct 4, 2011 at 5:11
On Tue, Oct 4, 2011 at 5:11 PM, Jeff Segal wrote:
> I have an application which dynamically creates and removes routes in
> a camel context. I'd like to be able to invoke an onShutdown method
> when routes are removed so that I can perform some cleanup tasks. I've
> read http://camel.apache.org/gr
I have an application which dynamically creates and removes routes in
a camel context. I'd like to be able to invoke an onShutdown method
when routes are removed so that I can perform some cleanup tasks. I've
read http://camel.apache.org/graceful-shutdown.html but wasn't able to
find a good solutio
a route or at least stop the
> consumer (jms mainly) if all redelivery have failed.
>
-
Ben O'Day
IT Consultant -http://benoday.blogspot.com
--
View this message in context:
http://camel.465427.n5.nabble.com/route-shutdown-tp4375945p4377461.html
Sent from the Camel - Users m
Hi
I'm wondering if it is possible to shutdown a route or at least stop the
consumer (jms mainly) if all redelivery have failed.
Best Regards,
Antoine
Atos Worldline SA/NV - Chaussee de Haecht 1442 Haachtsesteenweg
- 1130 Brussels - Belgium
RPM-RPR Bruxelles-Br
19 matches
Mail list logo