Date: Wed, 30 Apr 2003 13:56:00 -0400
Reply-To: John Stimpson <john.stimpson@UK.FID-INTL.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: John Stimpson <john.stimpson@UK.FID-INTL.COM>
Subject: Re: SAS/Intrnet - App dispatcher ports becoming unavailable
Some of you may remember the post below from last year. At the time, no
solution was found, so it is a problem we have lived with since then. At
SUGI I brought this up with SAS/Intrnet development staff, and after some
investigation it was determined that this was caused by a load manager bug
(specific to load manager running on Solaris, I believe). This has been
fixed in version 9.1, and we are now running without problems using load
manager (version 9.1) and application server (version 8.2). So if you
suffer from something similar to what is described below, it may be worth
contacting SI to see if the 9.1 solution will work for you.
Data Warehouse Team
External: 01737 836342
Fidelity Investments International, Fidelity Investment Services Limited,
Fidelity Pensions Management and Financial Administration Services Limited
(a Fidelity Group company) are all regulated in the UK by the FSA and have
their registered offices at Oakhill House, 130 Tonbridge Road,
Hildenborough, Tonbridge, Kent TN11 9DZ. Tel 01732 361144. Fidelity only
gives information on its products and does not give investment advice to
private clients based on individual circumstances. Any comments or
statements made are not necessarily those of Fidelity. The information
transmitted is intended only for the person or entity to which it is
addressed and may contain confidential and/or privileged material. If you
received this in error, please contact the sender and delete the material
from any computer. All e-mails sent from or to Fidelity may be subject to
our monitoring procedures..
On Wed, 1 May 2002 04:42:56 -0400, John Stimpson <john.stimpson@UK.FID-
>I am having a problem with the Application Dispatcher that I thought I
>would send to the list, as I am sure it must have been seen before. We are
>running SAS 8.2 on Solaris 2.6. The application I have developed uses the
>load manager to launch SAS processes as required, and I have made a range
>of 10 ports available to support these processes. In the broker
>configuration file, I have set the MinRun parameter to 1, so that there
>will always be 1 SAS process running to support incoming requests. The
>issue I am seeing can best be described by example - here is what is
> - Port number "1" is processing requests.
> - A new request comes in, and a SAS process is opened on port number "2"
>to process this request.
> - Users on port "1" cease activity, and the SAS process on port "1" shuts
>down in accordance with the timeout directive. Port "2" is still processing
> - A new request comes in while processing is occuring on Port "2", and a
>new session is opened by the load manager on Port "3".
>This is the problem. Even though Port "1" is not in use, this port is not
>used - instead, the process is started on the next available Port. The
>cycle will repeat down the list of ports until it runs out of available
>ports, and then the application no longer functions. The load manager must
>then be stopped and restarted. The software does not seem to recognise that
>higher ports are now available and can be used. I do not believe this issue
>is caused by application errors, although this is something not yet fully
>Before I start modifying the Broker configuration, I would very much like
>to hear from people who have some thoughts on what is happening here, and
>what can be done about it.
>Thanks as always