Scheduled job has instance id as null after finishing first occurrence

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Scheduled job has instance id as null after finishing first occurrence

Deepak Agarwal-2
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
Reply | Threaded
Open this post in threaded view
|

Re: Scheduled job has instance id as null after finishing first occurrence

Deepak Agarwal-2
Got it. Used unique poolId for each instances.


On Sun, Apr 21, 2013 at 12:39 AM, Deepak Agarwal <[hidden email]>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
>



--
Thanks,
Deepak Agarwal,

Mobile: +91 9501190044
Reply | Threaded
Open this post in threaded view
|

Re: Scheduled job has instance id as null after finishing first occurrence

Adrian Crum-3
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 <[hidden email]>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
>>
>
>

Reply | Threaded
Open this post in threaded view
|

Re: Scheduled job has instance id as null after finishing first occurrence

Deepak Agarwal-2
Thanks Adrian,

Just to make sure, poll-enabled="true" can be set as false to disable the
polling on all other servers. right ? I think only polling can be disabled.


On Sun, Apr 21, 2013 at 1:12 PM, Adrian Crum <
[hidden email]> wrote:

> 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 <[hidden email]
>> >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
>>>
>>> --
>>> Thanks,
>>> Deepak Agarwal,
>>>
>>> Mobile: +91 9501190044 <%2B91%209501190044>
>>
>>
Reply | Threaded
Open this post in threaded view
|

Re: Scheduled job has instance id as null after finishing first occurrence

Adrian Crum-3
Correct. All servers except the job scheduler have poll-enabled set to
"false".

-Adrian

On 4/21/2013 9:05 AM, Deepak Agarwal wrote:

> Thanks Adrian,
>
> Just to make sure, poll-enabled="true" can be set as false to disable the
> polling on all other servers. right ? I think only polling can be disabled.
>
>
> On Sun, Apr 21, 2013 at 1:12 PM, Adrian Crum <
> [hidden email]> wrote:
>
>> 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 <[hidden email]
>>>> 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
>>>>
>>>> --
>>>> Thanks,
>>>> Deepak Agarwal,
>>>>
>>>> Mobile: +91 9501190044 <%2B91%209501190044>
>>>