How do I inject the defaultShutdownStrategy bean into the camelContext? On Fri, Feb 26, 2016 at 1:20 PM, David Hoffer <dhoff...@gmail.com> wrote:
> I found a doc that says I can add the following to my camel context. I > tried it and it worked but then took it out and it still works so this > problem is random it doesn't happen all the time, no idea what is > triggering it yet. > > shutdownRoute="Default" shutdownRunningTask="CompleteCurrentTaskOnly" > > No we aren't using camel-disruptor, I'm not even aware of that. Thanks > for the bean DefaultShutdownStrategy tip, I'll experiment with that too. > > -Dave > > > > On Fri, Feb 26, 2016 at 1:02 PM, Matt Sicker <boa...@gmail.com> wrote: > >> Are you using camel-disruptor? I had a lot of problems like that. >> >> You could also configure your own DefaultShutdownStrategy and set a >> smaller >> timeout. For example: >> >> <bean id="defaultShutdownStrategy" >> class="org.apache.camel.impl.DefaultShutdownStrategy"> >> <property name="timeout" value="10"/> >> <property name="suppressLoggingOnTimeout" value="true"/> >> <property name="shutdownNowOnTimeout" value="true"/> >> </bean> >> >> >> On 26 February 2016 at 13:55, David Hoffer <dhoff...@gmail.com> wrote: >> >> > For some reason we are getting the following message from >> > the DefaultShutdownStrategy "Waiting as there are still 1 inflight and >> > pending exchanges to complete, timeout in 300 seconds." >> > >> > Which causes our app to not shut down for 5 minutes. This is happening >> > although there was no work for the app to do. E.g. we run as a service, >> > have lots of routes doing file and sftp work but in this case the app >> > starts no work to process but it gives this message on service shutdown. >> > (Happens also when there was work to do.) >> > >> > What might be this 1 exchange that is processing? How can I determine >> what >> > it is? Can I change the shut down strategy to cancel what might be >> > occurring? >> > >> > -Dave >> > >> >> >> >> -- >> Matt Sicker <boa...@gmail.com> >> > >
