Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <4C244D8D.7030707@spudsoft.co.uk>
Date: Fri, 25 Jun 2010 07:32:45 +0100
From: Jim Talbut <jtalbut@spudsoft.co.uk>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB;
 rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5
MIME-Version: 1.0
To: users@camel.apache.org
Subject: Re: Clustering with camel-quartz
References: <4C03E1E0.2050407@dueppe.com> <4C03E86D.1030406@dueppe.com>
 	<AANLkTikVPJMweY3H54NKo1UbjJA2RicJmZrLuvgNmBQ_@mail.gmail.com>
 	<4C077F28.8030006@dueppe.com>
 <AANLkTilttYNRdRZDOG6nBv-3nojo-CTMW-EPwXBJx9-M@mail.gmail.com>
 	<4C081100.2090306@dueppe.com>
 <AANLkTikgY7TijRWGYSSujj2jc9HLV4EzOoB0eU9eUWQO@mail.gmail.com>
 	<4C08F364.3080407@dueppe.com> <4C20C519.7020503@dueppe.com>
 	<AANLkTinZmUoa-qmtR2kwOcy7geyasHylyMTvHK66kpyD@mail.gmail.com>
 	<4C20DADE.6020509@dueppe.com> <4C2168C5.7080509@gmail.com>
 	<4C2395ED.8040008@dueppe.com>
 <AANLkTik-6_fZIGF8qt2zF7q-v5YT7e8w2M1_ZQKEaIBD@mail.gmail.com>
In-Reply-To: <AANLkTik-6_fZIGF8qt2zF7q-v5YT7e8w2M1_ZQKEaIBD@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 25/06/2010 06:17, Claus Ibsen wrote:
> I think the reason is the scheduler is started before the other routes
> has been fully started. And quartz starts very quick.
>
> We could add an option so you can configure a delay option so it can
> be started with delay.
> It has a startDelayed method:
> http://www.quartz-scheduler.org/docs/api/1.8.1/org/quartz/Scheduler.html
>
>
> However a better solution is to offer this as a feature in Camel which
> allows component to register callbacks to be invoked when all the
> other stuff have been started, so they can start last.
>
>
> I have created a ticket to track that
> https://issues.apache.org/activemq/browse/CAMEL-2855
>    
In my experience* one always needs to use the delay start features of 
quartz because it always gets going before its dependents.
Even if you have a "start last" feature, unless you make it a complex 
tree of dependencies you are going to face the situation where quartz (a 
late starter) is dependent on another late starter and you still have 
the race condition.
Also a start-last feature doesn't work when the thing which quartz 
depends upon is outside of camel.

So a start-last feature may be a good idea, but I think camel should 
probably make the delay start features of quartz available too.

Jim

* Which is restricted to using clustered quartz (and hence a persistent 
store for jobs) outside of camel.