On Fri, Jun 25, 2010 at 8:32 AM, Jim Talbut wrote:
> 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
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://ww
On Thu, Jun 24, 2010 at 7:29 PM, Ingo Düppe wrote:
> Hello,
>
> I found still some issues about clustering camel-quartz component (based
> on the current trunk version)
>
> First, why are stateful triggers are unscheduled on a graceful shutdown.
> I guess this causes, that the trigger is deleted w
On Thu, Jun 24, 2010 at 7:29 PM, Ingo Düppe wrote:
> Hello,
>
> I found still some issues about clustering camel-quartz component (based
> on the current trunk version)
>
> First, why are stateful triggers are unscheduled on a graceful shutdown.
> I guess this causes, that the trigger is deleted w
Hello,
I found still some issues about clustering camel-quartz component (based
on the current trunk version)
First, why are stateful triggers are unscheduled on a graceful shutdown.
I guess this causes, that the trigger is deleted within the database. So
not only the node that is shutting down l
Hi,
I added two patches to the jira issue. One for version 2.3.0 and one for
the trunk. Please check the patches and inform me if you will use them
in the next version. If you will use it then I could build my private
patched version until we can upgrade to the next up coming camel version.
Regar
Hi
If you are using maven you can exclude the quartz from camel-quartz and
include the right version of quartz that you want.
BTW, what kind of trouble did you get when you built the trunk ?
Willem
--
Apache Camel, Apache CXF committer
Open SOA http://www.fuses
Fine, I currently work on the 2.3.0 version of /tags. Because I have
some trouble to build the trunk.
Ingo
> On Tue, Jun 22, 2010 at 4:13 PM, Ingo Düppe wrote:
>
>> Hi,
>>
>> does any reason exists for not upgrading camel-quartz to use the current
>> quartz version 1.8.1?
>>
>>
> Its been
On Tue, Jun 22, 2010 at 4:13 PM, Ingo Düppe wrote:
> Hi,
>
> does any reason exists for not upgrading camel-quartz to use the current
> quartz version 1.8.1?
>
Its been upgraded to 1.8.2 on trunk.
> Regrads
>
> Ingo
>
> Am 04.06.10 14:36, schrieb Ingo Düppe:
>> Hi Claus,
>>
>> fine, I might pos
Hi,
does any reason exists for not upgrading camel-quartz to use the current
quartz version 1.8.1?
Regrads
Ingo
Am 04.06.10 14:36, schrieb Ingo Düppe:
> Hi Claus,
>
> fine, I might possibly have some time on next monday to create a patch
> for it.
> If not then in two weeks after my vacation I
Hi Claus,
fine, I might possibly have some time on next monday to create a patch
for it.
If not then in two weeks after my vacation I will create a patch for it.
Regards
Ingo
Am 04.06.10 06:55, schrieb Claus Ibsen:
> Hi Ingo
>
> On Thu, Jun 3, 2010 at 10:30 PM, Ingo Düppe wrote:
>
>> Hi Cla
Hi Ingo
On Thu, Jun 3, 2010 at 10:30 PM, Ingo Düppe wrote:
> Hi Claus,
>
> well I'm not sure if it is right. But I guess if the trigger is marked
> as volatile it will be automatically removed within in the database.
> Normally volatile jobs won't be stored in a db but in a cluster
> environment
Hi Claus,
well I'm not sure if it is right. But I guess if the trigger is marked
as volatile it will be automatically removed within in the database.
Normally volatile jobs won't be stored in a db but in a cluster
environment they will be.
The problem with camel is, that I cannot define an volati
Hi
If you have the app crash using kill -3 / -9 and then start it again
and expect quartz to recover and it does not.
Then I think you should ask at the Quartz user forum about this.
And maybe you can create a plain example with pure Quartz to not
pollute the example with Camel as the Quartz guys
Am 01.06.10 08:37, schrieb Claus Ibsen:
> On Mon, May 31, 2010 at 6:48 PM, Ingo Düppe wrote:
>
>> I forgot to mention that I currently use version 2.2.0.
>>
>>
> Can you create a small sample application that demonstrates this? Then
> its much easier to look into it to see what / if we can
On Mon, May 31, 2010 at 6:48 PM, Ingo Düppe wrote:
> I forgot to mention that I currently use version 2.2.0.
>
Can you create a small sample application that demonstrates this? Then
its much easier to look into it to see what / if we can do in Camel.
> - Ingo
>
>
--
Claus Ibsen
Apache Camel
I forgot to mention that I currently use version 2.2.0.
- Ingo
Hello,
I need to cluster my camel server and be able to simple restart the
service if a crash ocured. But I cannot figure out how to configure my
camel-quartz triggers to resume simply after a restart.
Or even worst, how to start the multiple instances of my cluster.
I always get the ObjectAlread
18 matches
Mail list logo
