ofbiz-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adrian Crum <adrian.c...@sandglass-software.com>
Subject Re: Scheduled job has instance id as null after finishing first occurrence
Date Sun, 21 Apr 2013 07:42:56 GMT
In a typical installation, you would configure only one server as the 
job scheduler. So, the pool IDs would remain identical and only one 
server is configured to run jobs in that pool.

-Adrian

On 4/21/2013 5:37 AM, Deepak Agarwal wrote:
> Got it. Used unique poolId for each instances.
>
>
> On Sun, Apr 21, 2013 at 12:39 AM, Deepak Agarwal <dagarwal82@gmail.com>wrote:
>
>> Hi All,
>>
>> I am scheduling a service to run every one hour and I am running 3 server
>> with instance id ofbiz1,ofbiz2 and ofbiz3.
>> I schedule the jobs from ofbiz3. First time the job gets executed
>> correctly by making an entry SERVICE_RUNNING and run_by_instance as ofbiz3.
>> But then SERVICE_PENDING has run_by_instance as null and therefore getting
>> picked by ofbiz1 and ofbiz2 also.
>>   --
>> Thanks,
>> Deepak Agarwal,
>>
>> Mobile: +91 9501190044
>>
>
>


Mime
View raw message