Q: Process Timeout Limit v7x

[Craig Carter-2]

Some parts of this message have been removed. Learn more about Nabble's security policy.

**

All,

 

When setting the process timeout limit in the administration tool, the maximum value is 60 seconds in v7.01.  We’re performing reporting and transmission processes that sometimes take longer than that.

 

Does anyone know of a way to increase that limit or has this limit been increased in later versions?  I know we could increase the “Set-Process-Timeout” value directly in the ar.cfg file but I would expect that to get overwritten the next time we make changes in the administrator  tool (it still shows 60 even if it is set to 120 in ar.cfg).

 

It would be great if you could specify a timeout value when you spawn a process but since it’s a single setting, we’re fine with increasing it overall if it works and we can make it stick.

 

//SIGNED//

Craig Carter

Information Technology Manager, RSP

 

 

 

_Platinum Sponsor: rmisolutions@... ARSlist: "Where the Answers Are"_

[Murnane, Phil]

Some parts of this message have been removed. Learn more about Nabble's security policy.

**

Craig:

 

I’ve seen long processes lock up threads in the AR Server, creating bottlenecks for other Remedy users.  Is this need anything that could be re-architected into something like this:

 

Process 1: Gather Required Data into temporary file – do not wait for process to complete

Process 2: keep checking to see if temporary file is finished creating

Process 3: Process Data from temporary file

 

Just a Thought,

--Phil

 

PS: I’ve never heard of setting the process timeout higher than 60 seconds, to answer your question directly.

 

From: Action Request System discussion list(ARSList) [mailto:arslist@...] On Behalf Of Craig Carter
Sent: Friday, November 06, 2009 19:38
To: arslist@...
Subject: Q: Process Timeout Limit v7x

 

**

All,

 

When setting the process timeout limit in the administration tool, the maximum value is 60 seconds in v7.01.  We’re performing reporting and transmission processes that sometimes take longer than that.

 

Does anyone know of a way to increase that limit or has this limit been increased in later versions?  I know we could increase the “Set-Process-Timeout” value directly in the ar.cfg file but I would expect that to get overwritten the next time we make changes in the administrator  tool (it still shows 60 even if it is set to 120 in ar.cfg).

 

It would be great if you could specify a timeout value when you spawn a process but since it’s a single setting, we’re fine with increasing it overall if it works and we can make it stick.

 

//SIGNED//

Craig Carter

Information Technology Manager, RSP

 

 

 

_Platinum Sponsor: rmisolutions@... ARSlist: "Where the Answers Are"_

_Platinum Sponsor: rmisolutions@... ARSlist: "Where the Answers Are"_

[LJ LongWing (Head)]

Some parts of this message have been removed. Learn more about Nabble's security policy.

**

I agree with Phil, you don't want it set higher than 60.  I think the best option would be to use a run-process to do a 'fire and forget', then have the external process update something within remedy when it's done, and have the client tool wait for that update event to occur.

---

From: Action Request System discussion list(ARSList) [mailto:arslist@...] On Behalf Of Craig Carter
Sent: Friday, November 06, 2009 5:38 PM
To: arslist@...
Subject: Q: Process Timeout Limit v7x

**

All,

 

When setting the process timeout limit in the administration tool, the maximum value is 60 seconds in v7.01.  We’re performing reporting and transmission processes that sometimes take longer than that.

 

Does anyone know of a way to increase that limit or has this limit been increased in later versions?  I know we could increase the “Set-Process-Timeout” value directly in the ar.cfg file but I would expect that to get overwritten the next time we make changes in the administrator  tool (it still shows 60 even if it is set to 120 in ar.cfg).

 

It would be great if you could specify a timeout value when you spawn a process but since it’s a single setting, we’re fine with increasing it overall if it works and we can make it stick.

 

//SIGNED//

Craig Carter

Information Technology Manager, RSP

 

 

 

_Platinum Sponsor: rmisolutions@... ARSlist: "Where the Answers Are"_ _Platinum Sponsor: rmisolutions@... ARSlist: "Where the Answers Are"_

[Axton Grams]

You can fork the process, in which case your workflow will not wait on
the completion of the forked process.  This done using a run process
action.  In this way you are not bound to the timeout limits, but it
may not fit your need.

Axton Grams

On Fri, Nov 6, 2009 at 6:37 PM, Craig Carter
<Craig.Carter@...> wrote:

> **
> All,
>
> When setting the process timeout limit in the administration tool, the
> maximum value is 60 seconds in v7.01.  We’re performing reporting and
> transmission processes that sometimes take longer than that.
>
> Does anyone know of a way to increase that limit or has this limit been
> increased in later versions?  I know we could increase the
> “Set-Process-Timeout” value directly in the ar.cfg file but I would expect
> that to get overwritten the next time we make changes in the administrator
> tool (it still shows 60 even if it is set to 120 in ar.cfg).
>
> It would be great if you could specify a timeout value when you spawn a
> process but since it’s a single setting, we’re fine with increasing it
> overall if it works and we can make it stick.
>
> //SIGNED//
> Craig Carter
> Information Technology Manager, RSP
>
>
>
> _Platinum Sponsor: rmisolutions@... ARSlist: "Where the Answers
> Are"_

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:rmisolutions@... ARSlist: "Where the Answers Are"

[Craig Carter-2]

The problem is that we are transmitting data to an external service and the agent is waiting for a successful response from that service to proceed and complete that case--they don't want to have to come back to it later and it's important this data get where it needs to go.  We're already looking at a variety of other options but none of them are ideal compared to just giving it a little more time.  In the majority of cases, it easily completes within the 60 seconds.

I just wanted to ask the question before working the other alternatives.
Thanks.

//SIGNED//
Craig Carter, YC-02
Information Technology Manager, RSP

-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:arslist@...] On Behalf Of LJ Longwing
Sent: Monday, November 09, 2009 7:29 AM
To: arslist@...
Subject: Re: Process Timeout Limit v7x

**
I agree with Phil, you don't want it set higher than 60.  I think the best option would be to use a run-process to do a 'fire and forget', then have the external process update something within remedy when it's done, and have the client tool wait for that update event to occur.

________________________________

From: Action Request System discussion list(ARSList) [mailto:arslist@...] On Behalf Of Craig Carter
Sent: Friday, November 06, 2009 5:38 PM
To: arslist@...
Subject: Q: Process Timeout Limit v7x


**
All,
 
When setting the process timeout limit in the administration tool, the maximum value is 60 seconds in v7.01.  We're performing reporting and transmission processes that sometimes take longer than that.
 
Does anyone know of a way to increase that limit or has this limit been increased in later versions?  I know we could increase the "Set-Process-Timeout" value directly in the ar.cfg file but I would expect that to get overwritten the next time we make changes in the administrator  tool (it still shows 60 even if it is set to 120 in ar.cfg).
 
It would be great if you could specify a timeout value when you spawn a process but since it's a single setting, we're fine with increasing it overall if it works and we can make it stick.
 
//SIGNED//
Craig Carter
Information Technology Manager, RSP
 
 
 
_Platinum Sponsor: rmisolutions@... ARSlist: "Where the Answers Are"_
_Platinum Sponsor: rmisolutions@... ARSlist: "Where the Answers Are"_

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:rmisolutions@... ARSlist: "Where the Answers Are"

[Craig Carter-2]

Hi Axton,

This process has to succeed at some point and the agents want to complete the case at the time they push the button--not come back later.  They are processing hundreds of cases and cannot afford to reopen these to see if it worked, try again if it didn't work, etc.

We may have to reengineer this so the agent can tell the system to send it and we have a separate process that continues to try and send it until it completes successfully versus having the agent wait for the response.

Regards,

//SIGNED//
Craig Carter, YC-02
Information Technology Manager, RSP


-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:arslist@...] On Behalf Of Axton
Sent: Monday, November 09, 2009 10:47 AM
To: arslist@...
Subject: Re: Q: Process Timeout Limit v7x

You can fork the process, in which case your workflow will not wait on
the completion of the forked process.  This done using a run process
action.  In this way you are not bound to the timeout limits, but it
may not fit your need.

Axton Grams

On Fri, Nov 6, 2009 at 6:37 PM, Craig Carter
<Craig.Carter@...> wrote:

> **
> All,
>
> When setting the process timeout limit in the administration tool, the
> maximum value is 60 seconds in v7.01.  We're performing reporting and
> transmission processes that sometimes take longer than that.
>
> Does anyone know of a way to increase that limit or has this limit been
> increased in later versions?  I know we could increase the
> "Set-Process-Timeout" value directly in the ar.cfg file but I would expect
> that to get overwritten the next time we make changes in the administrator
> tool (it still shows 60 even if it is set to 120 in ar.cfg).
>
> It would be great if you could specify a timeout value when you spawn a
> process but since it's a single setting, we're fine with increasing it
> overall if it works and we can make it stick.
>
> //SIGNED//
> Craig Carter
> Information Technology Manager, RSP
>
>
>
> _Platinum Sponsor: rmisolutions@... ARSlist: "Where the Answers
> Are"_

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:rmisolutions@... ARSlist: "Where the Answers Are"

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:rmisolutions@... ARSlist: "Where the Answers Are"

[LJ LongWing (Head)]

I have a filter api timeout (web services) that I've had to increase in the
past, but never been able to get the set fields process higher.

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:arslist@...] On Behalf Of Craig Carter
Sent: Thursday, November 12, 2009 7:13 AM
To: arslist@...
Subject: Re: Process Timeout Limit v7x

The problem is that we are transmitting data to an external service and the
agent is waiting for a successful response from that service to proceed and
complete that case--they don't want to have to come back to it later and
it's important this data get where it needs to go.  We're already looking at
a variety of other options but none of them are ideal compared to just
giving it a little more time.  In the majority of cases, it easily completes
within the 60 seconds.

I just wanted to ask the question before working the other alternatives.
Thanks.

//SIGNED//
Craig Carter, YC-02
Information Technology Manager, RSP

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:arslist@...] On Behalf Of LJ Longwing
Sent: Monday, November 09, 2009 7:29 AM
To: arslist@...
Subject: Re: Process Timeout Limit v7x

**
I agree with Phil, you don't want it set higher than 60.  I think the best
option would be to use a run-process to do a 'fire and forget', then have
the external process update something within remedy when it's done, and have
the client tool wait for that update event to occur.

________________________________

From: Action Request System discussion list(ARSList)
[mailto:arslist@...] On Behalf Of Craig Carter
Sent: Friday, November 06, 2009 5:38 PM
To: arslist@...
Subject: Q: Process Timeout Limit v7x


**
All,
 
When setting the process timeout limit in the administration tool, the
maximum value is 60 seconds in v7.01.  We're performing reporting and
transmission processes that sometimes take longer than that.
 
Does anyone know of a way to increase that limit or has this limit been
increased in later versions?  I know we could increase the
"Set-Process-Timeout" value directly in the ar.cfg file but I would expect
that to get overwritten the next time we make changes in the administrator
tool (it still shows 60 even if it is set to 120 in ar.cfg).
 
It would be great if you could specify a timeout value when you spawn a
process but since it's a single setting, we're fine with increasing it
overall if it works and we can make it stick.
 
//SIGNED//
Craig Carter
Information Technology Manager, RSP
 
 
 
_Platinum Sponsor: rmisolutions@... ARSlist: "Where the Answers
Are"_ _Platinum Sponsor: rmisolutions@... ARSlist: "Where the
Answers Are"_

____________________________________________________________________________
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum
Sponsor:rmisolutions@... ARSlist: "Where the Answers Are"

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:rmisolutions@... ARSlist: "Where the Answers Are"