You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by garrydias <ga...@gmail.com> on 2013/01/16 21:17:15 UTC
Re: Camel QuartzComponent failed on recreating endpoint
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 this message in context: http://camel.465427.n5.nabble.com/Camel-QuartzComponent-failed-on-recreating-endpoint-tp5723760p5725660.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel QuartzComponent failed on recreating endpoint
Posted by Denis Delangle <de...@gmail.com>.
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 <ga...@gmail.com>:
> 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 keeps my exchange in memory and not in its BLOB field in
> database table named QRTZ_JOB_DETAILS as I espected.
>
> So, stateful jobs is enough for me. To solve my memory issue I´ll work to
> reduce the size of my Exchange.
>
> thanx
>
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Camel-QuartzComponent-failed-on-recreating-endpoint-tp5723760p5725938.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel QuartzComponent failed on recreating endpoint
Posted by garrydias <ga...@gmail.com>.
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 keeps my exchange in memory and not in its BLOB field in
database table named QRTZ_JOB_DETAILS as I espected.
So, stateful jobs is enough for me. To solve my memory issue I´ll work to
reduce the size of my Exchange.
thanx
--
View this message in context: http://camel.465427.n5.nabble.com/Camel-QuartzComponent-failed-on-recreating-endpoint-tp5723760p5725938.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel QuartzComponent failed on recreating endpoint
Posted by Hude <fl...@googlemail.com>.
Hello,
no not really. We've changed our routes from quartz to direct. Also we've
created a CamelTriggerJob Bean. This Bean extends QuartzJobBean and has an
Producer which triggeres the direct routes.
For example:
<bean id=3D"terminTrigger"
class=3D"org.springframework.scheduling.quartz.CronTriggerBean">
<property name=3D"jobDetail" ref=3D"quartzJob" />
<property name=3D"cronExpression" value=3D"${a.schedule}" />
</bean>
<bean name=3D"quartzJob"
class=3D"org.springframework.scheduling.quartz.JobDetailBean">
<property name=3D"jobClass" value=3D"...quartz.CamelTriggerJob" />
<property name=3D"jobDataAsMap">
<map>
<entry key=3D"endpoint" value=3D"direct:termine" />
<entry key=3D"camelContext" value-ref=3D"camelContext" />
</map>
</property>
</bean>
--
View this message in context: http://camel.465427.n5.nabble.com/Camel-QuartzComponent-failed-on-recreating-endpoint-tp5723760p5725719.html
Sent from the Camel - Users mailing list archive at Nabble.com.