Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Apache: Users

TimeOuts Received.

 

 

Apache users RSS feed   Index | Next | Previous | View Threaded


g.shrivastava1985 at gmail

Jul 30, 2012, 6:07 AM

Post #1 of 5 (1401 views)
Permalink
TimeOuts Received.

*
We automated our product

Env -

4 Managed Serves - WLS weblogic (RHL)
1 DB - Oracle (RHL)
1 Proxy server - APACHE

What i can see during the execution of and as the user load increases to
180 +
I can see messages of timeouts at RPT console where response is not
received for the request.
Surprisingly i can not see any error logs for time outs any where in app
server logs or proxy server logs.


We did a test again with out proxy servers where requests were directly
hitting the app server every thing works well than no timeouts are noticted.
So it looks like the issue is with the proxy server do you have any
suggestions for any tunable parameters.


Some of the parameters currently used.

<IfModule worker.c>
ThreadLimit 2000
ServerLimit 10
StartServers 6
MaxClients 20000
MinSpareThreads 2000
#MinSpareThreads 100
#MaxSpareThreads 20000
MaxSpareThreads 15000
ThreadsPerChild 2000
MaxRequestsPerChild 0
</IfModule>


Help will be highly appreciated.
*

--
*Cheers !!

Gaurav ....*


icicimov at gmail

Jul 30, 2012, 5:57 PM

Post #2 of 5 (1345 views)
Permalink
Re: TimeOuts Received. [In reply to]

On Mon, Jul 30, 2012 at 11:07 PM, gaurav shrivastava <
g.shrivastava1985 [at] gmail> wrote:

> *
> We automated our product
>
> Env -
>
> 4 Managed Serves - WLS weblogic (RHL)
> 1 DB - Oracle (RHL)
> 1 Proxy server - APACHE
>
> What i can see during the execution of and as the user load increases to
> 180 +
> I can see messages of timeouts at RPT console where response is not
> received for the request.
> Surprisingly i can not see any error logs for time outs any where in app
> server logs or proxy server logs.
>
>
> We did a test again with out proxy servers where requests were directly
> hitting the app server every thing works well than no timeouts are noticted.
> So it looks like the issue is with the proxy server do you have any
> suggestions for any tunable parameters.
>
>
> Some of the parameters currently used.
>
> <IfModule worker.c>
> ThreadLimit 2000
> ServerLimit 10
> StartServers 6
> MaxClients 20000
> MinSpareThreads 2000
> #MinSpareThreads 100
> #MaxSpareThreads 20000
> MaxSpareThreads 15000
> ThreadsPerChild 2000
> MaxRequestsPerChild 0
> </IfModule>
>
>
> Help will be highly appreciated.
> *
>
> --
> *Cheers !!
>
> Gaurav ....*
>
>
What OS is apache running on? What is apache version? What is your proxy
configuration? What do you see in the log files, anything related to the
timeouts from mod_proxy? Have you first tested the connectivity between
apache and Weblogic meaning can you even connect from the apache box to the
weblogic port on the other server? Any possible firewall between the
servers?


g.shrivastava1985 at gmail

Jul 30, 2012, 11:22 PM

Post #3 of 5 (1346 views)
Permalink
Re: TimeOuts Received. [In reply to]

RHEL 5.5
Apache version 2.2.1
There are no connectivity issues due to firewall.
There is nothing which comes in the error logs.



On Tue, Jul 31, 2012 at 6:27 AM, Igor Cicimov <icicimov [at] gmail> wrote:

> On Mon, Jul 30, 2012 at 11:07 PM, gaurav shrivastava <
> g.shrivastava1985 [at] gmail> wrote:
>
>> *
>> We automated our product
>>
>> Env -
>>
>> 4 Managed Serves - WLS weblogic (RHL)
>> 1 DB - Oracle (RHL)
>> 1 Proxy server - APACHE
>>
>> What i can see during the execution of and as the user load increases to
>> 180 +
>> I can see messages of timeouts at RPT console where response is not
>> received for the request.
>> Surprisingly i can not see any error logs for time outs any where in app
>> server logs or proxy server logs.
>>
>>
>> We did a test again with out proxy servers where requests were directly
>> hitting the app server every thing works well than no timeouts are noticted.
>> So it looks like the issue is with the proxy server do you have any
>> suggestions for any tunable parameters.
>>
>>
>> Some of the parameters currently used.
>>
>> <IfModule worker.c>
>> ThreadLimit 2000
>> ServerLimit 10
>> StartServers 6
>> MaxClients 20000
>> MinSpareThreads 2000
>> #MinSpareThreads 100
>> #MaxSpareThreads 20000
>> MaxSpareThreads 15000
>> ThreadsPerChild 2000
>> MaxRequestsPerChild 0
>> </IfModule>
>>
>>
>> Help will be highly appreciated.
>> *
>>
>> --
>> *Cheers !!
>>
>> Gaurav ....*
>>
>>
> What OS is apache running on? What is apache version? What is your proxy
> configuration? What do you see in the log files, anything related to the
> timeouts from mod_proxy? Have you first tested the connectivity between
> apache and Weblogic meaning can you even connect from the apache box to the
> weblogic port on the other server? Any possible firewall between the
> servers?
>
>
>
>


--
*Cheers !!

Gaurav ....*


icicimov at gmail

Jul 31, 2012, 12:26 AM

Post #4 of 5 (1345 views)
Permalink
Re: TimeOuts Received. [In reply to]

On Tue, Jul 31, 2012 at 4:22 PM, gaurav shrivastava <
g.shrivastava1985 [at] gmail> wrote:

> RHEL 5.5
> Apache version 2.2.1
> There are no connectivity issues due to firewall.
> There is nothing which comes in the error logs.
>
>
>
> On Tue, Jul 31, 2012 at 6:27 AM, Igor Cicimov <icicimov [at] gmail> wrote:
>
>> On Mon, Jul 30, 2012 at 11:07 PM, gaurav shrivastava <
>> g.shrivastava1985 [at] gmail> wrote:
>>
>>> *
>>> We automated our product
>>>
>>> Env -
>>>
>>> 4 Managed Serves - WLS weblogic (RHL)
>>> 1 DB - Oracle (RHL)
>>> 1 Proxy server - APACHE
>>>
>>> What i can see during the execution of and as the user load increases to
>>> 180 +
>>> I can see messages of timeouts at RPT console where response is not
>>> received for the request.
>>> Surprisingly i can not see any error logs for time outs any where in app
>>> server logs or proxy server logs.
>>>
>>>
>>> We did a test again with out proxy servers where requests were directly
>>> hitting the app server every thing works well than no timeouts are noticted.
>>> So it looks like the issue is with the proxy server do you have any
>>> suggestions for any tunable parameters.
>>>
>>>
>>> Some of the parameters currently used.
>>>
>>> <IfModule worker.c>
>>> ThreadLimit 2000
>>> ServerLimit 10
>>> StartServers 6
>>> MaxClients 20000
>>> MinSpareThreads 2000
>>> #MinSpareThreads 100
>>> #MaxSpareThreads 20000
>>> MaxSpareThreads 15000
>>> ThreadsPerChild 2000
>>> MaxRequestsPerChild 0
>>> </IfModule>
>>>
>>>
>>> Help will be highly appreciated.
>>> *
>>>
>>> --
>>> *Cheers !!
>>>
>>> Gaurav ....*
>>>
>>>
>> What OS is apache running on? What is apache version? What is your proxy
>> configuration? What do you see in the log files, anything related to the
>> timeouts from mod_proxy? Have you first tested the connectivity between
>> apache and Weblogic meaning can you even connect from the apache box to the
>> weblogic port on the other server? Any possible firewall between the
>> servers?
>>
>>
>>
>>
>
>
> --
> *Cheers !!
>
> Gaurav ....*
>
> Ok what else is between Apache proxy and those 4 x Weblogic servers? Are
you using Apache as proxy load balancer or you have dedicated LB after it?
How's your load balancing set up?

Please post here your proxy configuration, including virtual host if the
proxy is nested inside one, so we can try to find if anything wrong here.

Your max number of concurrent client connections on your proxy is 20000. Do
you have thread pool of 20000 configured in Weblogic as well, meaning 5000
threads per server? Also is that thread pool on each of the WLS shared with
some other applications or not? My point is maybe the timeouts are really
timeouts due to WLS (maybe one of them at time) is going out of resources.

You said you tested the connection bypassing the proxy and it was fine. Was
this at the time of the proxy timeouts? If not your test is irrelevant.


g.shrivastava1985 at gmail

Jul 31, 2012, 2:22 AM

Post #5 of 5 (1427 views)
Permalink
Re: TimeOuts Received. [In reply to]

Apache was working as proxy server ans its was used as LB. The LB strategy
set as Round Robin.


Proxy Setting -
#
# This is the main Apache HTTP server configuration file. It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.2> for detailed information.
# In particular, see
# <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
# for a discussion of each configuration directive.
#
# Do NOT simply read the instructions in here without understanding
# what they do. They're here only as hints or reminders. If you are unsure
# consult the online docs. You have been warned.
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path. If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "logs/foo_log"
# with ServerRoot set to "/opt/qasp04/Apache" will be interpreted by the
# server as "/opt/qasp04/Apache/logs/foo_log".

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# Do not add a slash at the end of the directory path. If you point
# ServerRoot at a non-local disk, be sure to point the LockFile directive
# at a local disk. If you wish to share the same ServerRoot for multiple
# httpd daemons, you will need to change at least LockFile and PidFile.
#
ServerRoot "/opt/Apache"

#TimeOut Amount of time the server will wait for certain events before
failing a request
TimeOut 300

#KeepAlive This will keep persistent connections on.
KeepAlive On

#KeepAliveTimeout Amount of time the server will wait for subsequent
requests on a persistent connection
KeepAliveTimeout 10

#MaxKeepAliveRequests Number of requests allowed on a persistent connection
MaxKeepAliveRequests 0


#UseCanonicalName Configures how the server determines its own name and port
UseCanonicalName off

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses.
#
#Listen 12.34.56.78:80
Listen 9.113.210.73:80

# worker MPM
#
# For tuning recommendations, refer to <NEWINFOCENTERURL>.
#
# ThreadLimit: maximum setting of ThreadsPerChild
# ServerLimit: maximum setting of StartServers
# StartServers: initial number of server processes to start
# MaxClients: maximum number of simultaneous client connections
# MinSpareThreads: minimum number of worker threads which are kept spare
# MaxSpareThreads: maximum number of worker threads which are kept spare
# ThreadsPerChild: constant number of worker threads in each server process
# MaxRequestsPerChild: maximum number of requests a server process serves
#<IfModule worker.c>
#ThreadLimit 512
#ServerLimit 128
#StartServers 2
#MaxClients 1024
#MinSpareThreads 25
#MaxSpareThreads 75
#ThreadsPerChild 256
#MaxRequestsPerChild 4000
#</IfModule>

<IfModule worker.c>
ThreadLimit 2000
ServerLimit 10
StartServers 6
MaxClients 20000
MinSpareThreads 2000
#MinSpareThreads 100
#MaxSpareThreads 20000
MaxSpareThreads 15000
ThreadsPerChild 2000
MaxRequestsPerChild 0
</IfModule>





#
# Dynamic Shared Object (DSO) Support
#
# To be able to use the functionality of a module which was built as a DSO
you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
#
# Example:
# LoadModule foo_module modules/mod_foo.so
#
LoadModule authn_file_module modules/mod_authn_file.so
LoadModule authn_dbm_module modules/mod_authn_dbm.so
LoadModule authn_anon_module modules/mod_authn_anon.so
LoadModule authn_dbd_module modules/mod_authn_dbd.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authz_host_module modules/mod_authz_host.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule authz_dbm_module modules/mod_authz_dbm.so
LoadModule authz_owner_module modules/mod_authz_owner.so
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule auth_basic_module modules/mod_auth_basic.so
LoadModule auth_digest_module modules/mod_auth_digest.so
LoadModule cache_module modules/mod_cache.so
LoadModule dbd_module modules/mod_dbd.so
LoadModule dumpio_module modules/mod_dumpio.so
LoadModule reqtimeout_module modules/mod_reqtimeout.so
LoadModule ext_filter_module modules/mod_ext_filter.so
LoadModule include_module modules/mod_include.so
LoadModule filter_module modules/mod_filter.so
LoadModule substitute_module modules/mod_substitute.so
LoadModule deflate_module modules/mod_deflate.so
LoadModule log_config_module modules/mod_log_config.so
LoadModule log_forensic_module modules/mod_log_forensic.so
LoadModule logio_module modules/mod_logio.so
LoadModule env_module modules/mod_env.so
LoadModule mime_magic_module modules/mod_mime_magic.so
LoadModule cern_meta_module modules/mod_cern_meta.so
LoadModule expires_module modules/mod_expires.so
LoadModule headers_module modules/mod_headers.so
LoadModule ident_module modules/mod_ident.so
LoadModule usertrack_module modules/mod_usertrack.so
LoadModule unique_id_module modules/mod_unique_id.so
LoadModule setenvif_module modules/mod_setenvif.so
LoadModule version_module modules/mod_version.so
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_connect_module modules/mod_proxy_connect.so
LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule proxy_scgi_module modules/mod_proxy_scgi.so
LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
LoadModule mime_module modules/mod_mime.so
LoadModule dav_module modules/mod_dav.so
LoadModule status_module modules/mod_status.so
LoadModule autoindex_module modules/mod_autoindex.so
LoadModule asis_module modules/mod_asis.so
LoadModule info_module modules/mod_info.so
LoadModule cgi_module modules/mod_cgi.so
LoadModule dav_fs_module modules/mod_dav_fs.so
LoadModule vhost_alias_module modules/mod_vhost_alias.so
LoadModule negotiation_module modules/mod_negotiation.so
LoadModule dir_module modules/mod_dir.so
LoadModule imagemap_module modules/mod_imagemap.so
LoadModule actions_module modules/mod_actions.so
LoadModule speling_module modules/mod_speling.so
LoadModule userdir_module modules/mod_userdir.so
LoadModule alias_module modules/mod_alias.so
LoadModule rewrite_module modules/mod_rewrite.so
LoadModule weblogic_module modules/mod_wl_22.so
<IfModule !mpm_netware_module>
<IfModule !mpm_winnt_module>
#
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.
#
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
#
User daemon
Group daemon

<IfModule mod_userdir.c>
UserDir public_html

#
# Control access to UserDir directories. The following is an example
# for a site where these directories are restricted to read-only.
#
<Directory /home/*/public_html>
AllowOverride FileInfo AuthConfig Limit Indexes
Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
<Limit GET POST OPTIONS PROPFIND>
Order allow,deny
Allow from all
</Limit>
<LimitExcept GET POST OPTIONS PROPFIND>
Order deny,allow
Deny from all
</LimitExcept>
</Directory>
</IfModule>
# 'Main' server configuration
#
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition. These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
#
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
#

#
# ServerAdmin: Your address, where problems with the server should be
# e-mailed. This address appears on some server-generated pages, such
# as error documents. e.g. admin [at] your-domain
#
ServerAdmin you [at] example

#
# ServerName gives the name and port that the server uses to identify
itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If your host doesn't have a registered DNS name, enter its IP address
here.
#
#ServerName www.example.com:80

#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
DocumentRoot "/opt/Apache/htdocs"

#
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
#
# First, we configure the "default" to be a very restrictive set of
# features.
#
<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>

#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#

#
# This should be changed to whatever you set DocumentRoot to.
#
<Directory "/opt/Apache/htdocs">
#
# Possible values for the Options directive are "None", "All",
# or any combination of:
# Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI
MultiViews
#
# Note that "MultiViews" must be named *explicitly* --- "Options All"
# doesn't give it to you.
#
# The Options directive is both complicated and important. Please see
# http://httpd.apache.org/docs/2.2/mod/core.html#options
# for more information.
#
Options Indexes FollowSymLinks

#
# AllowOverride controls what directives may be placed in .htaccess
files.
# It can be "All", "None", or any combination of the keywords:
# Options FileInfo AuthConfig Limit
#
AllowOverride None

#
# Controls who can get stuff from this server.
#
Order allow,deny
Allow from all

</Directory>

#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
<IfModule dir_module>
DirectoryIndex index.html
</IfModule>

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<FilesMatch "^\.ht">
Order allow,deny
Deny from all
</FilesMatch>

#
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here. If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog "logs/error_log"

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn

<IfModule log_config_module>
#
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
#
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\"
\"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %b" common

<IfModule logio_module>
# You need to enable mod_logio.c to use %I and %O
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\"
\"%{User-Agent}i\" %I %O" combinedio
</IfModule>

#
# The location and format of the access logfile (Common Logfile Format).
# If you do not define any access logfiles within a <VirtualHost>
# container, they will be logged here. Contrariwise, if you *do*
# define per-<VirtualHost> access logfiles, transactions will be
# logged therein and *not* in this file.
#
CustomLog "logs/access_log" common

#
# If you prefer a logfile with access, agent, and referer information
# (Combined Logfile Format) you can use the following directive.
#
#CustomLog "logs/access_log" combined
</IfModule>

<IfModule alias_module>
#
# Redirect: Allows you to tell clients about documents that used to
# exist in your server's namespace, but do not anymore. The client
# will make a new request for the document at its new location.
# Example:
# Redirect permanent /foo http://www.example.com/bar

#
# Alias: Maps web paths into filesystem paths and is used to
# access content that does not live under the DocumentRoot.
# Example:
# Alias /webpath /full/filesystem/path
#
# If you include a trailing / on /webpath then the server will
# require it to be present in the URL. You will also likely
# need to provide a <Directory> section to allow access to
# the filesystem path.

#
# ScriptAlias: This controls which directories contain server scripts.
# ScriptAliases are essentially the same as Aliases, except that
# documents in the target directory are treated as applications and
# run by the server when requested rather than as documents sent to the
# client. The same rules about trailing "/" apply to ScriptAlias
# directives as to Alias.
#
ScriptAlias /cgi-bin/ "/opt/Apache/cgi-bin/"

</IfModule>

<IfModule cgid_module>
#
# ScriptSock: On threaded servers, designate the path to the UNIX
# socket used to communicate with the CGI daemon of mod_cgid.
#
#Scriptsock logs/cgisock
</IfModule>

#
# "/opt/qasp04/Apache/cgi-bin" should be changed to whatever your
ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "/opt/Apache/cgi-bin">
AllowOverride None
Options None
Order allow,deny
Allow from all
</Directory>

#
# DefaultType: the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value. If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
#
DefaultType text/plain

<IfModule mime_module>
#
# TypesConfig points to the file containing the list of mappings from
# filename extension to MIME-type.
#
TypesConfig conf/mime.types

#
# AddType allows you to add to or override the MIME configuration
# file specified in TypesConfig for specific file types.
#
#AddType application/x-gzip .tgz
#
# AddEncoding allows you to have certain browsers uncompress
# information on the fly. Note: Not all browsers support this.
#
#AddEncoding x-compress .Z
#AddEncoding x-gzip .gz .tgz
#
# If the AddEncoding directives above are commented-out, then you
# probably should define those extensions to indicate media types:
#
AddType application/x-compress .Z
AddType application/x-gzip .gz .tgz

#
# AddHandler allows you to map certain file extensions to "handlers":
# actions unrelated to filetype. These can be either built into the
server
# or added with the Action directive (see below)
#
# To use CGI scripts outside of ScriptAliased directories:
# (You will also need to add "ExecCGI" to the "Options" directive.)
#
#AddHandler cgi-script .cgi

# For type maps (negotiated resources):
#AddHandler type-map var

#
# Filters allow you to process content before it is sent to the client.
#
# To parse .shtml files for server-side includes (SSI):
# (You will also need to add "Includes" to the "Options" directive.)
#
#AddType text/html .shtml
#AddOutputFilter INCLUDES .shtml
</IfModule>

#
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type. The MIMEMagicFile
# directive tells the module where the hint definitions are located.
#
#MIMEMagicFile conf/magic

#
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
#
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
#

#
# MaxRanges: Maximum number of Ranges in a request before
# returning the entire resource, or one of the special
# values 'default', 'none' or 'unlimited'.
# Default setting is to accept 200 Ranges.
#MaxRanges unlimited

#
# EnableMMAP and EnableSendfile: On systems that support it,
# memory-mapping or the sendfile syscall is used to deliver
# files. This usually improves server performance, but must
# be turned off when serving from networked-mounted
# filesystems or if support for these functions is otherwise
# broken on your system.
#
#EnableMMAP off
#EnableSendfile off

# Supplemental configuration
#
# The configuration files in the conf/extra/ directory can be
# included to add extra features or to modify the default configuration of
# the server, or you may simply copy their contents here and change as
# necessary.

# Server-pool management (MPM specific)
#Include conf/extra/httpd-mpm.conf

# Multi-language error messages
#Include conf/extra/httpd-multilang-errordoc.conf

# Fancy directory listings
#Include conf/extra/httpd-autoindex.conf

# Language settings
#Include conf/extra/httpd-languages.conf

# User home directories
#Include conf/extra/httpd-userdir.conf

#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
HostnameLookups Off

#
# EnableSendfile: Control whether the sendfile kernel support is
# used to deliver files (assuming that the OS supports it).
# The default is on; turn this off if you serve from NFS-mounted
# filesystems. Please see
#
http://publib.boulder.ibm.com/httpserv/manual70/mod/core.html#enablesendfile
#
EnableSendfile off

ServerTokens Prod

#Details needs to be added


ServerSignature On

IndexOptions FancyIndexing VersionSort




# Real-time info on requests and configuration
#Include conf/extra/httpd-info.conf

# Virtual hosts
#Include conf/extra/httpd-vhosts.conf

# Local access to the Apache HTTP Server Manual
#Include conf/extra/httpd-manual.conf

# Distributed authoring and versioning (WebDAV)
#Include conf/extra/httpd-dav.conf

# Various default settings
#Include conf/extra/httpd-default.conf

# Secure (SSL/TLS) connections
#Include conf/extra/httpd-ssl.conf
#
# Note: The following must must be present to support
# starting without SSL on platforms with no /dev/random equivalent
# but a statically compiled-in mod_ssl.
#
<IfModule weblogic_module>
WebLogicCluster 9.113.210.73:7014,9.113.210.75:7015,9.113.210.79:7216,
9.113.210.79:7218,9.113.210.72:7025
WLSocketTimeoutSecs 30
</IfModule>

<Location />
SetHandler weblogic-handler
PathTrim /
</Location>

<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>



I would say since i can not see any time out from WLS side during the tests
i do not feel it can be a problem with WLS.
Also and since its been tested with out proxy server and no time outs are
received so some how it points towards the proxy server which is having
problems.




On T ue, Jul 31, 2012 at 12:56 PM, Igor Cicimov <icicimov [at] gmail> wrote:

> On Tue, Jul 31, 2012 at 4:22 PM, gaurav shrivastava <
> g.shrivastava1985 [at] gmail> wrote:
>
>> RHEL 5.5
>> Apache version 2.2.1
>> There are no connectivity issues due to firewall.
>> There is nothing which comes in the error logs.
>>
>>
>>
>> On Tue, Jul 31, 2012 at 6:27 AM, Igor Cicimov <icicimov [at] gmail> wrote:
>>
>>> On Mon, Jul 30, 2012 at 11:07 PM, gaurav shrivastava <
>>> g.shrivastava1985 [at] gmail> wrote:
>>>
>>>> *
>>>> We automated our product
>>>>
>>>> Env -
>>>>
>>>> 4 Managed Serves - WLS weblogic (RHL)
>>>> 1 DB - Oracle (RHL)
>>>> 1 Proxy server - APACHE
>>>>
>>>> What i can see during the execution of and as the user load increases
>>>> to 180 +
>>>> I can see messages of timeouts at RPT console where response is not
>>>> received for the request.
>>>> Surprisingly i can not see any error logs for time outs any where in
>>>> app server logs or proxy server logs.
>>>>
>>>>
>>>> We did a test again with out proxy servers where requests were directly
>>>> hitting the app server every thing works well than no timeouts are noticted.
>>>> So it looks like the issue is with the proxy server do you have any
>>>> suggestions for any tunable parameters.
>>>>
>>>>
>>>> Some of the parameters currently used.
>>>>
>>>> <IfModule worker.c>
>>>> ThreadLimit 2000
>>>> ServerLimit 10
>>>> StartServers 6
>>>> MaxClients 20000
>>>> MinSpareThreads 2000
>>>> #MinSpareThreads 100
>>>> #MaxSpareThreads 20000
>>>> MaxSpareThreads 15000
>>>> ThreadsPerChild 2000
>>>> MaxRequestsPerChild 0
>>>> </IfModule>
>>>>
>>>>
>>>> Help will be highly appreciated.
>>>> *
>>>>
>>>> --
>>>> *Cheers !!
>>>>
>>>> Gaurav ....*
>>>>
>>>>
>>> What OS is apache running on? What is apache version? What is your proxy
>>> configuration? What do you see in the log files, anything related to the
>>> timeouts from mod_proxy? Have you first tested the connectivity between
>>> apache and Weblogic meaning can you even connect from the apache box to the
>>> weblogic port on the other server? Any possible firewall between the
>>> servers?
>>>
>>>
>>>
>>>
>>
>>
>> --
>> *Cheers !!
>>
>> Gaurav ....*
>>
>> Ok what else is between Apache proxy and those 4 x Weblogic servers? Are
> you using Apache as proxy load balancer or you have dedicated LB after it?
> How's your load balancing set up?
>
> Please post here your proxy configuration, including virtual host if the
> proxy is nested inside one, so we can try to find if anything wrong here.
>
> Your max number of concurrent client connections on your proxy is 20000.
> Do you have thread pool of 20000 configured in Weblogic as well, meaning
> 5000 threads per server? Also is that thread pool on each of the WLS shared
> with some other applications or not? My point is maybe the timeouts are
> really timeouts due to WLS (maybe one of them at time) is going out of
> resources.
>
> You said you tested the connection bypassing the proxy and it was fine.
> Was this at the time of the proxy timeouts? If not your test is irrelevant.
>
>



--
*Cheers !!

Gaurav ....*

Apache users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.