service engine default max-retries

[Si Chen-2]

Hi everybody.

Something else I noticed is that the serviceengine.xml has a

failed-retry-min="3"

but no failed-retry-max attribute.  Would it be nice to have a  
default-retry-max?  Right now it seems there is no max, so unless one  
is set for the service individually, the system keeps running them  
over and over again.

Si

[Andrew Zeneski]

This refers to the number of MINUTES to wait before the retry.. Not  
the min number of times. The max is unlimited unless it is specified  
when the service is invoked or on the service definition.

On Jun 28, 2006, at 2:58 PM, Si Chen wrote:

> Hi everybody.
>
> Something else I noticed is that the serviceengine.xml has a
>
> failed-retry-min="3"
>
> but no failed-retry-max attribute.  Would it be nice to have a  
> default-retry-max?  Right now it seems there is no max, so unless  
> one is set for the service individually, the system keeps running  
> them over and over again.
>
> Si
>

[Jacques Le Roux]

+1

> Hi everybody.
>
> Something else I noticed is that the serviceengine.xml has a
>
> failed-retry-min="3"
>
> but no failed-retry-max attribute.  Would it be nice to have a  
> default-retry-max?  Right now it seems there is no max, so unless one  
> is set for the service individually, the system keeps running them  
> over and over again.
>
> Si

[Jacques Le Roux]

Thanks Andy

Jacques

> This refers to the number of MINUTES to wait before the retry.. Not  
> the min number of times. The max is unlimited unless it is specified  
> when the service is invoked or on the service definition.
>
> On Jun 28, 2006, at 2:58 PM, Si Chen wrote:
>
> > Hi everybody.
> >
> > Something else I noticed is that the serviceengine.xml has a
> >
> > failed-retry-min="3"
> >
> > but no failed-retry-max attribute.  Would it be nice to have a  
> > default-retry-max?  Right now it seems there is no max, so unless  
> > one is set for the service individually, the system keeps running  
> > them over and over again.
> >
> > Si
> >

... [show rest of quote]

[Si Chen-2]

So what do you think of having a default # of max-retry times?

On Jun 28, 2006, at 1:24 PM, A. Zeneski wrote:

> This refers to the number of MINUTES to wait before the retry.. Not  
> the min number of times. The max is unlimited unless it is  
> specified when the service is invoked or on the service definition.
>
> On Jun 28, 2006, at 2:58 PM, Si Chen wrote:
>
>> Hi everybody.
>>
>> Something else I noticed is that the serviceengine.xml has a
>>
>> failed-retry-min="3"
>>
>> but no failed-retry-max attribute.  Would it be nice to have a  
>> default-retry-max?  Right now it seems there is no max, so unless  
>> one is set for the service individually, the system keeps running  
>> them over and over again.
>>
>> Si
>>

... [show rest of quote]

[David E. Jones]

I don't know if this is a good idea. In essence with it you are saying that the service is not important enough to make sure it goes through, or stays in the queue until someone takes care of it. While important to support that, I don't know that we want to have it be the default behavior...

-David


Si Chen wrote:

> So what do you think of having a default # of max-retry times?
>
> On Jun 28, 2006, at 1:24 PM, A. Zeneski wrote:
>
>> This refers to the number of MINUTES to wait before the retry.. Not
>> the min number of times. The max is unlimited unless it is specified
>> when the service is invoked or on the service definition.
>>
>> On Jun 28, 2006, at 2:58 PM, Si Chen wrote:
>>
>>> Hi everybody.
>>>
>>> Something else I noticed is that the serviceengine.xml has a
>>>
>>> failed-retry-min="3"
>>>
>>> but no failed-retry-max attribute.  Would it be nice to have a
>>> default-retry-max?  Right now it seems there is no max, so unless one
>>> is set for the service individually, the system keeps running them
>>> over and over again.
>>>
>>> Si
>>>
>

... [show rest of quote]