Re: WAS3.0 way too slow on linux, help...

From: Yassir Khogaly <yassir_at_khogaly.freeserve.co.uk>
Date: Sat, 21 Nov 1998 22:39:18 -0000
Message-ID: <737fkd$pie$1@newsreader4.core.theplanet.net>

Can I suggest checking your listener .!

Configuring an Oracle Web Listener in Detail

The Oracle Web Listener Advanced Configuration form allows you to customize an Oracle Web Listener in more detail than the basic configuration allows. To use this form, you must first have selected a Web Listener process from the list on the Oracle Web Listener Administration form and have clicked its Configure button or clicked the Advanced Configuration button on the Create New Oracle Web Listener form.

You can use the Oracle Web Listener Advanced Configuration form to:

Create a new Web Listener by copying the selected Web Listener configuration Modify the selected Web Listener configuration Delete the selected Web Listener
For your convenience, each section of the form has Copy Listener, Modify Listener, and Delete Listener buttons to perform these actions; if you click any button in any section, the entire form will be processed.

Copying an Existing Web Listener
Before clicking the Copy Listener button, you must first enter a new listener name and at least one unused port number in the Addresses and Ports section of the form. When you click the Copy Listener button, the new Web Listener is created for the specified port or ports using the same parameter values as the original configuration except for the following parameters, which are reset to their default values:

Listener PID (see Network Parameters, below) Info File (Listener transaction log -- see Addresses and Ports) Error File (Listener error log -- see Log File Parameters) After you click the Copy Listener button, the Advanced Configuration form shows the configuration of the new Web Listener.

Modifying a Web Listener
You can click the Modify Listener button at any time to apply changes you have made to parameter values to the current Web Listener configuration.

Deleting a Web Listener
Clicking the Delete Listener button stops and destroys the selected Web Listener process. You can also delete a Web Listener by going to the Oracle Web Listener Administration form, selecting the Web Listener's name from the list of Web Listeners, and clicking the DELETE button.

Configuration Parameters
The Oracle Web Listener Advanced Configuration form divides configuration parameters into these categories:

Network Parameters -- Specifies the network identity of the host on which the Web Listener is running, and controls how the Web Listener uses the network
Log File Parameters -- Controls how the Web Listener logs transactions and errors
Miscellaneous Listener Parameters -- Configures various defaults for the Web Listener, such as default character set and time-outs User and Group Parameters -- Specifies the user and group identities the Web Listener assumes while running
Directory Mappings -- Maps specific virtual pathnames used in URLs to the physical pathnames of local files
Language Extensions -- Maps abbreviations identifying human languages to appropriate character sets and filename extensions MIME Types -- Maps Multipurpose Internet Mail Extension (MIME) types to filename extensions representing each type Encoding Extensions -- Specifies helper applications to use with files having the given extensions
Security: Access Control and Encryption -- Specifies the parameters to secure your Oracle WebListener
The only Web Listener parameters that can't be configured using this form involve security. Follow the Security link from the Advanced Configuration form to configure the security aspects of Web Listener behaviour. The following sections describe the parameters you can configure using the Advanced Configuration form.

Network Parameters
This section specifies the network identity of the host on which the Web Listener runs, and controls how the Web Listener uses the network.

Listener Name
You should choose an alphanumeric string no longer than six characters that uniquely identifies the Web Listener. The form will inform you if the name you choose is already being used.

Addresses and Ports
Each Oracle Web Listener process is capable of accepting connections on multiple TCP/IP ports. Each entry in this section specifies the network identity the Web Listener assumes for connections on a particular port. Each entry has the following fields:

Proxy
Turning on proxy behaviour allows a Web Listener running on a firewall machine to act as a proxy server, allowing users inside the firewall to access the Internet. If your Web Listener is not running on a firewall machine, or if you want to disable proxy behaviour, set this radio button to Off.

Address
The IP address associated with the specified port. On machines with more than one IP address, you may assign a different IP address to each port. A value of zero or "ANY" means the Web Listener can accept connections from the specified port on any of the machine's available addresses. (See your operating system documentation if you want to learn how to configure your multiple IP addresses on your machine.)

Port
A TCP/IP port on which the Web Listener can accept connections. You can choose any number from 1 to 65535. To use ports 1 through 1023, you must give the Web Listener process root privileges (see the User and Group Parameters sections.)

Security
Specifies the security module to handle incoming requests through the address and port combination. Possible values are:

NORM -- Do not support Secure Sockets Layer (SSL) or Private Communication Technology (PCT) encryption on a port.
SSL -- Add support for SSL.
PCT -- Add support for PCT.
Host Name
The name by which the server identifies itself on this address/port combination. You can use your machine's primary host name, or an alias such as www.blob.com, by which you want to identify your Web Listener on the Internet. See your operating system documentation to learn how to define a hostname alias.

Base Directory
The directory name to which URL-encoded pathnames addressed to this port are to be appended. For example, if the base directory is /public_html, the URL http://www.blob.com/file is converted to http://www.blob.com/public_html/file.

Log Info Directory
The log information directory containing log information files that the listener uses to write informative messages for this port.

Authentication
Determines if the Web Application Server authenticates a client over an SSL port. Possible values are:

NONE -- Do not authenticate the client.
OPT -- Authenticate the client, but do not require a certificate.
REQ -- Authenticate the client and abort the SSL handshake if the client

does not send a certificate.
This parameter is used for clients implementing SSL 3.0 only. The Web Application Server never authenticates clients implementing SSL 2.0.

Certificate Label
The label pointing to certificate files in the Security field. You can only have one certificate label per port. If you selected NORM under Security, leave this field blank.

Maximum Connections
The maximum number of Web Listener connections that may be active at one time. The default is 338. You should allow as many connections as your machine can handle simultaneously without severely impairing performance. Experience will guide you in tuning this parameter value.

DNS Resolution
Specifies when to translate IP addresses into DNS (Domain Name Service) host names. Possible values are:

ALWAYS -- Always translate IP addresses into DNS hostnames. LAZY -- Translate IP addresses into DNS hostnames only when needed by an Application Development Interface (ADI) application or security module. LAZY_WITH_CGI -- Translate IP addresses into DNS hostnames only when needed by CGI programs.
NEVER -- Never use DNS hostnames (default). Setting DNS Resolution to ALWAYS slows your Web Listener's performance somewhat because the DNS server usually runs on a different machine from the Web Application Server, making each transaction subject to a time-consuming DNS query.
On the other hand, if you use domain-based restriction for access control, you must not set DNS Resolution to NEVER. In this case, setting DNS Resolution to LAZY_WITH_CGI is often a good compromise.

Redirection Server
The URL of a Web Listener process to which requests can be redirected when the selected Listener's maximum number of connections has been reached. The URL must be of the form:

http://HostName:PortNumber
Note: The redirection server must have all the capabilities of the selected Web Listener so that it can fulfill the same requests. If you are consistently receiving the maximum number of connections on a certain Web Listener process, you might want to create another Listener by copying the original Listener configuration and use the new Listener as a redirection server for the original.

Listener PID file
A file that contains the Process ID PID of the Web Listener process. Important: You must use the Oracle Web Listener Administration form to stop a Web Listener before changing its Listener PID file value. If you do not do this, the Oracle Web Listener Administration form loses track of the Web Listener process.

Log File Parameters
This section controls how the Web Listener logs transactions and errors. The Web Listener writes error messages to the Log Admin File, which is common for all address/port combinations. There is only one administrative file for all ports.
The Web Listener also writes informative messages to the Log Information File Directory for a particular address/port combination in the Network Parameters section (see above).

Log Admin File
The file to which the Web Listener logs error messages generated when it encounters problems accessing resources, interacting with requestors, and interacting with other gateway servers. The default is $ORACLE_HOME/ows3.0/log/svListenerName.err.

Log Admin File Rollover
Defines how often you want to roll over the log files. Valid values are daily, weekly, monthly, and never. The server closes the current connection's information files and begins writing to new files when the log files are rolled over. For example, if you select a weekly roll over, the server closes the log files at 0:00 on Sunday (GMT or local time). Each log file is appended with its creation date in YYMMDD format.

Log Time Style
Specifies the way time stamps should be written in log files. Possible values are:

Local -- Use local time (default).
GMT -- Use Greenwich Mean Time.

Log Information Files
Each entry in this section specifies which values the Web Application Server writes to each file. Each entry has the following fields:

Log Info File
The file to which the Web Application Server logs the information.

Format
Specifies the log file format. Possible values are:

CLF -- Common LogFile Format
XLF -- Extended LogFile Format
Format Fields
Specifies the fields you want the Web Application Server to write to the log info file. Use braces separated by spaces, for example, {time cs-method cs-uri}. The following table lists the fields you can use in either XLF or CLF files:
Value Description
clf
Fields which would normally be written to a CLF file: c-dns cauth-id [clf-date] "request line" sc-status bytes

clf-date
Date and time of the request in the same format as used in the CLF: [dd/mm/yyyy:hour:minutes:seconds GMT_offset]

c-auth-id
User name if the request contained an attempt to authenticate

bytes
Content-length of the transferred document

date
Date at which the transaction completed

time
Time at which the transaction completed

time-taken
Amount of time taken for transaction to complete in seconds

c-ip
Client's IP address and port

s-ip
Server's IP address and port

c-dns
Client's DNS name

s-dns
Server's DNS name

sc-status
Server to client status code

sc-comment
Server to client comment returned with the status code

cs-method
Server to client method (GET, POST, or others)

cs-uri
Client to server URI

cs-uri-stem
Client to server stem portion of URI, omitting the query

cs-uri-query
Client to server query portion of URI, omitting the stem

prefix (header)
Header is an HTTP header field and prefix is one of the following:

c: client
s: server
r: remote

cs: client to server
sc: server to client

Miscellaneous Listener Parameters
This section configures various defaults for the Web Listener, such as default character set and time-outs.

Configuration Directory
The directory where you want the Web Listener configuration file, named svListenerName.cfg, to reside. If you choose a different directory than the default value provided, make sure the permissions on the directory allow the Web Listener to read the file.

Initial File
The default file to retrieve from a directory when a URL specifies only the directory. The default filename is "initial". For example, if you set this field to index.html, the request URL http://www.blob.com/ will translate to http://www.blob.com/index.html.

User Directory
The default subdirectory to search in a user's home directory if a URL specifies only the user's home directory. For example, if the user directory is public_html, and a browser requests http://www.blob.com/~jane, the URL is converted to http://www.blob.com/~jane/public_html/. There is no default. There are several restrictions imposed on user directories:

For security, no CGI scripts may run from a user directory. The Web Listener performs no filename negotiation within user directories; the URL must specify the requested filename exactly. If several browsers access the same file within a user directory at the same time, they do not share a common memory-mapped copy of the file, which makes accesses to user directories somewhat less efficient than access to other directories.

Default MIME Type
Specifies a Multipurpose Internet Mail Extensions (MIME) type to use in interpreting requested files of an unsupported MIME type. The default is application/octet-stream, which means that by default, the Web Listener treats any requested file of unidentified MIME type as a binary file. You can review the RFCs that define MIME at http://www.oac.uci.edu/indiv/ehood/MIME/MIME.html.

Default Character Set
The character set to use in interpreting a file that uses an unrecognized character set. You must use a character set name defined by RFC 1521. The default is iso-8859-1, the character set used for English.

Preferred Language
The language to choose when handling a request for a file available in more than one language, if the request doesn't specify a language. You must use a language identifier defined by RFC 1766. The default is "en" (English).

Image Map Extension
Filename extensions that the Web Listener should use to identify image map files. There is no default, so if you want this Web Listener to support image maps, you must set this field to the filename extension, such as map, that you use for your image map files.

Use Directory Indexing
Specifies whether the Web Listener should provide a directory listing when a URL resolves to a directory that does not contain a file named by InitialFile. If you enter "false", such a URL will produce an error. Directory listings can sometimes help requestors correct spelling errors in their request URLs. The default is "true". For security or privacy, you might not want to expose all directory contents to clients; in this case, set this field to "false".

Service Timeout
Specifies the number of seconds the control panel services waits for a start, stop, or continue operation to finish before reporting a failure. This parameter is valid only for Windows NT.

CGI Timeout
Specifies the number of seconds the Oracle Web Listener allows a CGI or WinCGI application to complete before terminating the script's execution.

Keep Alive Timeout
Specifies the number of seconds the Oracle Web Listener keeps a connection open without any activity on that connection. If you leave this field empty, the default value is 10 seconds.

Rescan Interval
Specifies the number of seconds after which a directory is automatically rescanned regardless of whether it has been modified. If you leave this field empty, the default value is 0 seconds, which denotes that a directory is rescanned only when its last modification time has changed.

ISAPI Filename Extensions
Specifies valid ISAPI filename extensions. One or more ISAPI extensions, separated by spaces or commas, are allowed. The default is .so for UNIX.

Servlet Port
Specifies the port number used by the Web Application Server to communicate with the Java environment. Specify a value if you want to enable the servlet API. There is no default.

Servlet Timeout
Specifies the time in seconds the Web Application Server waits for a Java servlet to respond. If it exceeds this limit, a response from the servlet may be missing or incomplete. The default is 120 seconds.

User and Group Parameters
This section specifies the user and group identities the Web Listener assumes when it runs. When the Web Listener process starts up, it runs with root privileges until it completes its configuration. Then, the Web Listener assumes the user and group identities specified in the User ID and Group ID parameters.
The User ID and Group ID parameters you use must give the Web Listener the following access permissions to certain files and the directories in which they reside:

Read access to the configuration file
Read access to all files that provide content for servicing requests Read access to all image map files
Execute access to all Oracle Web Application Server binaries and program files that the Web Listener must execute Write access to the log and error files Read access to user directories
For security, however, you should take care in allowing a Web Listener with privileged user ID, such as root or oracle, or group ID, such as dba, to launch programs, because these programs inherit the Web Listener's privileges. You might consider assigning your Web Listeners an unprivileged user identity such as nobody.

User ID
The user identity that the Web Listener assumes after it completes its configuration. You can specify either a user name or numeric user ID in this field. To denote the root ID, however, you must specify "root" rather than "0".

Group ID
The group identity that the Web Listener assumes after it completes its configuration. You can specify either a group name or a numeric group ID in this field.

Directory Mappings
This section defines a virtual file system by mapping specific virtual pathnames used in URLs to the file-system pathnames of local directories. When the Web Listener starts up, it checks to make sure it has access to the file-system directories specified in this section, but it doesn't check individual files in the directories. If a subsequent request refers to a file that the Web Listener cannot access, the Listener returns a "404: Not found" error.

Each entry in this section has the following fields:

File-System Directory
Specifies the pathname of a directory in the local file system.

Flag
The first code in this field specifies whether CGI programs may run from the specified virtual directory. Possible values are:

N (Normal) -- Do not allow CGI programs to run from this directory.
C (CGI) -- Allow CGI programs to run from this directory.
W (WinCGI) -- (Windows NT only) Allow WinCGI programs to run from this

directory.
The second code specifies whether subdirectories of the specified file-system directory should mapped recursively--that is, whether the directory tree rooted at the specified file-system directory should be accessible through the specified virtual directory. Possible values are:

N (Non-recursive) -- Do not map subdirectories recursively. R (Recursive) -- Map subdirectories recursively. If you don't want to make the subdirectories of the mapped file-system directory accessible to clients, set the directory mapping to non-recursive.

Virtual Directory
Specifies the virtual directory through which the file-system directory will be accessed. The first entry in the Directory Mappings section must specify the virtual root directory ("/").

Language Extensions
This section maps abbreviations identifying human languages to appropriate character sets and filename extensions. Because character set specifications apply only to text files, language extensions for non-text files are ignored. For example, the files image.en.jpg and image.uc.jpg would be considered equivalent.

Each entry in this section has the following fields:

Language Type
A language identifier, such as en, as defined by RFC 1766.

Character Set
The name of the character set used for the specified language, such as iso-8859-1, as defined by RFC 1521.

File Extension(s)
Extension or extensions used to identify files encoded for the specified language, such as eng. Filename extensions are case sensitive; if you specify more than one extension, you must separate them by spaces or commas.

MIME Types
This section associates filename extensions with the Multipurpose Internet Mail Extensions (MIME) types that the Web Listener recognizes. Each entry in this section has the following fields:

MIME Type
A MIME type, such as text/html, as defined by RFCs 1521 and 1522.

File Extension(s)
Extension or extensions, such as htm or html, used to identify files of the specified MIME type. File extensions are case sensitive; if you specify more than one extension, you must separate them by spaces or commas.

Encoding Extensions
This section specifies filename extensions for files that use encodings the Web Listener recognizes. Each entry in this section has the following fields:

Encoding
The name of a helper application, such as compress, used to encode files. Received on Sat Nov 21 1998 - 16:39:18 CST