Hi,
Thanks for your answer, I'll try this in a real environment. In my
testcase, the error is not raised anymore but the process is not
executed.
(My testcase is attached here https://issues.apache.org/jira/browse/CAMEL-5993)
Denis
2013/1/21 garrydias :
> It´s a nice approach.
>
> I solved my pr
It´s a nice approach.
I solved my problem setting camel quartz endpoint as stateful. But this
comes at a high cost. With around 1500 jobs I lost 18MB in heap memory
because my Exchanges have around 25kb.
Trying to solve the memory issue, I changed the RamJobStore to JdbcJobStore
but Quartz also
Hello
change the release solve the problem?
I´m facing the same problem in production environment when I start more than
500 quartz endpoints. The failure occurs at fire time.
I cannot reproduce this error in dev environment. The error just not
happens.
My Camel version is 2.10.1.
--
View th
Hi
Can you try upgrading to the latest Camel 2.9.x release?
On Fri, Dec 7, 2012 at 10:34 AM, Hude wrote:
> We're using the camel quartz component (camel version 2.9.0 and quartz in
> version 1.8.5) to trigger some jobs once a day. The routes are looking
> similar to this:
>
> from("quartz://aen
