You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ofbiz.apache.org by Vikas Jadhav <vi...@finicity.com> on 2009/09/23 12:43:10 UTC
JobPoller causing high cpu utilization.
Hi,
We are using OFBiz 3.0 and have some scheduled jobs in OFBiz.
We are having multiple instances of OFBiz pointing to the same database and
are having same pool ids or pool name in serviceengine.xml. Its been
observed that ofbiz process is utilizing 100% CPU usage and causing high CPU
utilization.
>From investigations, we find that JobPoller's run(), next() and JobManager's
poll methods are taking too much time.
Can any one help on this to sort it out.
Thanks,
Vikas
Re: JobPoller causing high cpu utilization.
Posted by Jacques Le Roux <ja...@les7arts.com>.
You may find what as been used so far here
http://docs.ofbiz.org/display/OFBADMIN/OFBiz+Related+Books
Jacques
From: "Olindo Pindaro" <o....@gmail.com>
> >
>> Hi guys, I am just evaluating ofBiz,
> I bought the online book, good for understanding how do develop a new ofBiz
> application but I didn't find any detailed description of features
> implemented, informations needed for business analisys, web design ecc.
> ecc.
>
>
> Any suggestion/link?
>
>
>
> TNX a lot
> Olindo Pindaro
> http://www.linkedin.com/in/olindopindaro
> +39 3939455830
>
Re: JobPoller causing high cpu utilization.
Posted by Olindo Pindaro <o....@gmail.com>.
>
> Hi guys, I am just evaluating ofBiz,
I bought the online book, good for understanding how do develop a new ofBiz
application but I didn't find any detailed description of features
implemented, informations needed for business analisys, web design ecc.
ecc.
Any suggestion/link?
TNX a lot
Olindo Pindaro
http://www.linkedin.com/in/olindopindaro
+39 3939455830
Re: JobPoller causing high cpu utilization.
Posted by Shi Jinghai <sh...@langhua.cn>.
I hope OFBiz can use Quartz in the future:
http://www.opensymphony.com/quartz/
Shi Jinghai/Beijing Langhua Ltd.
在 2009-09-23三的 06:09 -0600,Brett Palmer写道:
> I think Ofbiz 3.0 is pretty old so its going to be hard for the
> community to help with this issue.
>
> Here are a few suggestions:
>
> - are you archiving the job_sandbox table? This table can get very
> large if you don't
> - make sure you have services set to fail after a certain amount of
> retries. I have had bad services that just keep trying when the retry
> is set to -1
> - make sure you don't have table scans on that table
>
> And finally
>
> - update your ofbiz version to a more recent version
>
>
> Brett
>
> On 9/23/09, Vikas Jadhav <vi...@finicity.com> wrote:
> > Hi,
> >
> > We are using OFBiz 3.0 and have some scheduled jobs in OFBiz.
> >
> > We are having multiple instances of OFBiz pointing to the same database and
> > are having same pool ids or pool name in serviceengine.xml. Its been
> > observed that ofbiz process is utilizing 100% CPU usage and causing high CPU
> > utilization.
> >
> > From investigations, we find that JobPoller's run(), next() and JobManager's
> > poll methods are taking too much time.
> >
> > Can any one help on this to sort it out.
> >
> > Thanks,
> > Vikas
> >
>
Re: JobPoller causing high cpu utilization.
Posted by Brett Palmer <br...@gmail.com>.
I think Ofbiz 3.0 is pretty old so its going to be hard for the
community to help with this issue.
Here are a few suggestions:
- are you archiving the job_sandbox table? This table can get very
large if you don't
- make sure you have services set to fail after a certain amount of
retries. I have had bad services that just keep trying when the retry
is set to -1
- make sure you don't have table scans on that table
And finally
- update your ofbiz version to a more recent version
Brett
On 9/23/09, Vikas Jadhav <vi...@finicity.com> wrote:
> Hi,
>
> We are using OFBiz 3.0 and have some scheduled jobs in OFBiz.
>
> We are having multiple instances of OFBiz pointing to the same database and
> are having same pool ids or pool name in serviceengine.xml. Its been
> observed that ofbiz process is utilizing 100% CPU usage and causing high CPU
> utilization.
>
> From investigations, we find that JobPoller's run(), next() and JobManager's
> poll methods are taking too much time.
>
> Can any one help on this to sort it out.
>
> Thanks,
> Vikas
>
--
Sent from my mobile device