Re: Q: Process Timeout Limit v7x
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:arsl...@arslist.org] On Behalf Of Axton Sent: Monday, November 09, 2009 10:47 AM To: arslist@ARSLIST.ORG 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 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: rmisoluti...@verizon.net ARSlist: "Where the Answers > Are"_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
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 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: rmisoluti...@verizon.net ARSlist: "Where the Answers > Are"_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
Re: Q: Process Timeout Limit v7x
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:arsl...@arslist.org] On Behalf Of Craig Carter Sent: Friday, November 06, 2009 19:38 To: arslist@ARSLIST.ORG 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: rmisoluti...@verizon.net ARSlist: "Where the Answers Are"_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"