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 <[email protected]> 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
