[Openroad-users] App Server - Timeout Interval

[Jonathan Barton]

Many thanks for this Durwin.
 
This is exactly what I am after - I will implement the timeout interval
asap.  The reason I want it is because the ASO connection to the
database has been lost and so it needs replacing.  Would 30 minutes be
unreasonable bearing in mind the afore-mentioned issue we face?
 
With regards to the transaction limit:
 
Does the purge affect all slaves at the same time?
And what happens to any requests that have not been completed?
 
We actually stop and start the OR AppServer service every morning
anyway, which would be before way before 100000 transactions (max
20000).
 
Thanks again.
 
Jonathan
 
________________________________

From: openroad-users-bounces at peerlessit.com
[mailto:openroad-users-bounces at peerlessit.com] On Behalf Of Durwin
Wright
Sent: 28 September 2007 16:35
To: International OpenROAD Users
Subject: Re: [Openroad-users] App Server - Timeout Interval



I normaly set my Timeout Interval value to 60 minutes for stateless
ASOs.  This is an inactivity interval.  If the Dispatcher Manager
detects that an ASO has been inactive for this period of time then the
ASO is scheduled for shutdown.  You will see an entry in the SPOTrace
file that indicates that the ASO was shutdown due to a Timeout.  This
timeout counter is reset to zero each time a new request is processed.

 

After an ASO has been shutdown due to ta Timeout, the next time a
Call4GL request is scheduled for the shutdown ASO, an implicit Initiate
will be done.  This will result in a longer Call4GL execution time since
the Initiate time is now considered part of the Call4GL request.  

 

While the ASO is processing a request, the timeout interval does not
have any affect.

 

I also typically set my Transaction Limit to 100,000 for stateless ASOs.
This will shutdown the ASO after a fixed number of requests have been
processed.  An entry in the SPOTrace file will indicate that this action
has been take.  When the next Call4GL request is sent to the ASO, an
imiplicit Initiate will be down on behalf of the requestor.

 

Durwin Wright | Sr. Architect | Durwin.Wright at ingres.com
<mailto:Durwin.Wright at ingres.com>  | Ingres | 500 Arguello Street |
Suite 200 | Redwood City | CA | 94063 | USA
<http://maps.google.com/maps?q=500+arguello+street,+94063&ll=37.487297,-
122.233200&spn=0.004602,0.012771&t=k&hl=en>   +1 650-587-5523 | fax: +1
650-587-5550 

________________________________

From: openroad-users-bounces at peerlessit.com
[mailto:openroad-users-bounces at peerlessit.com] On Behalf Of Jonathan
Barton
Sent: Friday, September 28, 2007 6:09 AM
To: International OpenROAD Users
Subject: [Openroad-users] App Server - Timeout Interval

 

Hi 

 

Has anyone had experience in using the timeout Interval for a signature
on the OR App Server?

 

What is the recommended level?
What happens to calls that are currently being executed?

 

Currently we have this set to 0, but due to a current issue with network
connections dropping out the ASO slave connection becomes useless.

 

So much to learn... :-)

 

Many thanks.

 

JONATHAN

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

"University of the West of England"

* Work Email:         jonathan.barton at uwe.ac.uk

* Work No:             0117 3281075

 

P Please consider the environment before printing.

    

________________________________

This email was independently scanned for viruses by McAfee anti-virus
software and none were found 

________________________________

This incoming email to UWE has been independently scanned for viruses by
McAfee anti-virus software and none were detected 



This email was independently scanned for viruses by McAfee anti-virus software and none were found
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.peerlessit.com/pipermail/openroad-users/attachments/20071001/6ab1a103/attachment.html