SVN trunk
Release Branch 11.04
Fixed in R11 rev 1559353, and in R12 rev 1559346.
> Schedule Job Manager is creating more then one pending job for future.
> --
>
>
ssue has been solved in trunk and R13. Thanks
> Schedule Job Manager is creating more then one pending job for future.
> --
>
> Key: OFBIZ-5496
> URL: https://issues.apache.org/jir
anges and update you. Thanks.
> Schedule Job Manager is creating more then one pending job for future.
> --
>
> Key: OFBIZ-5496
> URL: https://issues.apache.org/jira/browse/OFBIZ-5496
>
d in the trunk and R13. I will
backport the improved Job Scheduler to R11 and R12 later.
> Schedule Job Manager is creating more then one pending job for future.
> --
>
> Key: OFBIZ-5496
>
and create the double future job for a
schedule job
> Schedule Job Manager is creating more then one pending job for future.
> --
>
> Key: OFBIZ-5496
> URL: https://issues.apache.org/ji
atch file(JobManager_1204_Generate_Issue.patch)
which can produce the issue and create the double future job for a schedule,
please take a look.
> Schedule Job Manager is creating more then one pending job for future.
> --
>
>
anch rev 1558779.
R11 and R12 should have the improved Job Scheduler backported because the
previous design had many problems.
> Schedule Job Manager is creating more then one pending job for future.
> --
>
>
of the previous rollback).
> Schedule Job Manager is creating more then one pending job for future.
> --
>
> Key: OFBIZ-5496
> URL: https://issues.apache.org/jira/browse/OFBIZ-5496
>
[
https://issues.apache.org/jira/browse/OFBIZ-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrian Crum reassigned OFBIZ-5496:
--
Assignee: Adrian Crum
> Schedule Job Manager is creating more then one pending job for fut
Attaching the patch for version 11.04, 12.04, 13.07 and trunk.
> Schedule Job Manager is creating more then one pending job for future.
> --
>
> Key: OFBIZ-5496
> URL: https://issues.apache.
[
https://issues.apache.org/jira/browse/OFBIZ-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ritu Raj Lakhera updated OFBIZ-5496:
Description:
Schedule Job Manager is creating more then one pending job for future. Issue
Ritu Raj Lakhera created OFBIZ-5496:
---
Summary: Schedule Job Manager is creating more then one pending
job for future.
Key: OFBIZ-5496
URL: https://issues.apache.org/jira/browse/OFBIZ-5496
Project
From:
Quoting Brett Palmer :
Is there a relationship between the “send-to-pool” attribute and the
“run-from-pool” names or are they independent of each other? For example,
if I don't have a run-from-pool element with a name="pool" will the default
"pool" still work?
They are not related. If
Brett,
Thank you for the update. I will look into this.
-Adrian
On 9/19/2012 6:02 AM, Brett Palmer wrote:
Adrian,
I'll have to setup a load test to verify that a large number of pending
jobs in the JobSandbox do not saturate the server. I'll also work with the
thread counts to see what works
Adrian,
I'll have to setup a load test to verify that a large number of pending
jobs in the JobSandbox do not saturate the server. I'll also work with the
thread counts to see what works for us.
Before I read your reply I had configured the service engine to use a
"send-to-pool=poolX" but did n
On Sun, Aug 5, 2012 at 6:21 AM, Adrian Crum <
adrian.crum@sandglass-softwa**re.com <http://software.com> <
adrian.crum@sandglass-**softwa**re.com <http://software.com><
adrian.crum@sandglass-**software.com
>
wrote:
On 8/5/2012 11:02 AM, Adrian Crum wrote:
I
>>> many
>>>>>> concurrent jobs are run. For example, if I had 4 app servers
>>>>>> connected
>>>>>> to
>>>>>> the same DB I may only want one app server to service particular jobs.
>>>>>> I
>
n 8/5/2012 11:02 AM, Adrian Crum wrote:
I just committed a bunch of changes to the Job Manager group of
classes.
The changes help simplify the code and hopefully make the Job Manager
more
robust. On the other hand, I might have broken something. ;) I will
monitor
the mailing list for problems.
I
I considered integrating Quartz, but the problems with the JobManager
and JobPoller were easy to identify and fix. Time will tell though...
-Adrian
On 8/18/2012 4:59 PM, Ean Schuessler wrote:
Yeah, that's not going to fly. Its interesting to note that David Jones
replaced the JobPoller with Q
Yeah, that's not going to fly. Its interesting to note that David Jones
replaced the JobPoller with Quartz in Moqui.
- "Adrian Crum" wrote:
> 3. There is a JobPoller instance per delegator, and each instance
> contains the number of threads configured in serviceengine.xml. With the
> curr
2 1:21 PM, Adrian Crum wrote:
On 8/5/2012 11:02 AM, Adrian Crum wrote:
I just committed a bunch of changes to the Job Manager group of classes.
The changes help simplify the code and hopefully make the Job Manager more
robust. On the other hand, I might have broken something. ;) I will monit
M, Adrian Crum wrote:
I just committed a bunch of changes to the Job Manager group of
classes.
The changes help simplify the code and hopefully make the Job Manager
more
robust. On the other hand, I might have broken something. ;) I will
monitor
the mailing list for problems.
I belie
>>>> the same DB I may only want one app server to service particular jobs.
>>>> I
>>>> thought this feature was possible but when I tried to implement it by
>>>> changing some of the configuration files it never worked correctly.
>>>>
>&g
On Sun, Aug 5, 2012 at 6:21 AM, Adrian Crum <
adrian.crum@sandglass-**software.com >
wrote:
On 8/5/2012 11:02 AM, Adrian Crum wrote:
I just committed a bunch of changes to the Job Manager group of classes.
The changes help simplify the code and hopefully make the Job Manager
more
ro
I just updated the schema with documentation that should help everyone
understand how to set up the Job Manager/Job Poller. It seems to me it
can accommodate the scenario you described.
-Adrian
On 8/13/2012 2:42 AM, Brett Palmer wrote:
*Adrian,
I think the single JobPoller is a good idea
2012 1:21 PM, Adrian Crum wrote:
>
>> On 8/5/2012 11:02 AM, Adrian Crum wrote:
>>
>>> I just committed a bunch of changes to the Job Manager group of classes.
>>> The changes help simplify the code and hopefully make the Job Manager more
>>> robust. On the o
,
Hans
On 08/12/2012 06:36 PM, Adrian Crum wrote:
On 8/5/2012 1:21 PM, Adrian Crum wrote:
On 8/5/2012 11:02 AM, Adrian Crum wrote:
I just committed a bunch of changes to the Job Manager group of
classes. The changes help simplify the code and hopefully make the
Job Manager more robust. On the oth
:
I just committed a bunch of changes to the Job Manager group of
classes. The changes help simplify the code and hopefully make the
Job Manager more robust. On the other hand, I might have broken
something. ;) I will monitor the mailing list for problems.
I believe the JobPoller settings in
On 8/5/2012 1:21 PM, Adrian Crum wrote:
On 8/5/2012 11:02 AM, Adrian Crum wrote:
I just committed a bunch of changes to the Job Manager group of
classes. The changes help simplify the code and hopefully make the
Job Manager more robust. On the other hand, I might have broken
something. ;) I
On 8/8/2012 10:10 PM, Jacques Le Roux wrote:
From:
Quoting Brett Palmer :
*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
Jacques,
It sounds like what Adrian implemented would solve a lot of our problems
with the service engine. Please see my comments inline..
On Wed, Aug 8, 2012 at 3:54 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:
> Hi Brett,
>
> Interesting...
>
> Brett Palmer wrote:
>
>> *Jacques,
their queuing mechanism for
jobs.
+1
Jacques
Brett
On Sun, Aug 5, 2012 at 6:21 AM, Adrian Crum <
adrian.crum@sandglass-**software.com >
wrote:
On 8/5/2012 11:02 AM, Adrian Crum wrote:
I just committed a bunch of changes to the Job Manager group of classes.
The changes help simpli
From:
Quoting Brett Palmer :
*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
Quoting Brett Palmer :
*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 we
ctly.
>>
>> - JMS support for the service engine. It would be nice if there was a JMS
>> interface for those that want to use JMS as their queuing mechanism for
>> jobs.
>>
>>
>> Brett
>>
>> On Sun, Aug 5, 2012 at 6:21 AM, Adrian Crum <
>&g
there was a JMS
interface for those that want to use JMS as their queuing mechanism for
jobs.
Brett
On Sun, Aug 5, 2012 at 6:21 AM, Adrian Crum <
adrian.c...@sandglass-software.com> wrote:
On 8/5/2012 11:02 AM, Adrian Crum wrote:
I just committed a bunch of changes to the Job Manager group
11:02 AM, Adrian Crum wrote:
I just committed a bunch of changes to the Job Manager group of classes.
The changes help simplify the code and hopefully make the Job Manager
more
robust. On the other hand, I might have broken something. ;) I will
monitor
the mailing list for problems.
I believ
their queuing mechanism for
>> jobs.
>>
>
> +1
>
> Jacques
>
>
>
>> Brett
>>
>> On Sun, Aug 5, 2012 at 6:21 AM, Adrian Crum <
>> adrian.crum@sandglass-**software.com >
>> wrote:
>>
>> On 8/5/2012 11:02 AM,
We can use JMS as an option to replace the job queue and associated
threads, but we can't eliminate the entity-engine-based Job Manager
code because there are too many places where the JobSandbox entity is
manipulated (a bad practice, but it is done a lot).
-Adrian
Quoting Jacques Le
ian.c...@sandglass-software.com> wrote:
On 8/5/2012 11:02 AM, Adrian Crum wrote:
I just committed a bunch of changes to the Job Manager group of classes.
The changes help simplify the code and hopefully make the Job Manager more
robust. On the other hand, I might have broken something. ;) I will mon
a JMS
interface for those that want to use JMS as their queuing mechanism for
jobs.
Brett
On Sun, Aug 5, 2012 at 6:21 AM, Adrian Crum <
adrian.c...@sandglass-software.com> wrote:
On 8/5/2012 11:02 AM, Adrian Crum wrote:
I just committed a bunch of changes to the Job Manager group of c
andglass-software.com> wrote:
> On 8/5/2012 11:02 AM, Adrian Crum wrote:
>
>> I just committed a bunch of changes to the Job Manager group of classes.
>> The changes help simplify the code and hopefully make the Job Manager more
>> robust. On the other hand, I might have broken
On 8/5/2012 11:02 AM, Adrian Crum wrote:
I just committed a bunch of changes to the Job Manager group of
classes. The changes help simplify the code and hopefully make the Job
Manager more robust. On the other hand, I might have broken something.
;) I will monitor the mailing list for problems
I just committed a bunch of changes to the Job Manager group of classes.
The changes help simplify the code and hopefully make the Job Manager
more robust. On the other hand, I might have broken something. ;) I will
monitor the mailing list for problems.
I believe the JobPoller settings in
44 matches
Mail list logo
