On 8/8/2012 10:10 PM, Jacques Le Roux wrote:
From: <[email protected]>
Quoting Brett Palmer <[email protected]>:
*Jacques,*
*
I had to review some of my notes to remember what we were trying to
do with
the JobSandbox. Here are my replies to your questions:
1. Did you use the purge-job-days setting in serviceengine.xml and the
related purgeOldJobs? If not was there a reason?
We were not using the purgeOldJobs service. This was probably
because we
didn’t understand how the service worked. We may have thought the
service
was specific to order only jobs which would not have worked for us.
Our
jobs are custom service jobs for the particular application we are
developing.
I just looked at that service and I don't like it. It is simplistic
and takes a brute-force approach. Basically, the service is
scheduled to run at midnight each day and it purges all jobs older
than a configurable time duration. There is no guarantee the Job
Poller will be idle when that service fires. The Java code tries to
limit the purge to 1000 record batches. That setting is hard-coded
and appears arbitrary.
I would prefer to put job purging back under the control of the Job
Poller - where purges can be scheduled during queue idle periods and
they can follow the same constraints as any other job.
That sounds like a good replacement indeed
+1
Implemented in rev 1371140.
-Adrian
