[Apache2 et PHP5] Impossible d'avoir plusieurs connexions simultanées

[Cartman34]

Bonjour,

J'ai découvert qu'avec la configuration par défaut d'Apache2 et PHP5, on ne pouvait pas ouvrir 2 pages PHP du même site en même temps tant que la première n'avais pas fini de s'exécuter. Il semblerait que PHP5 soit bloquant vis à vis de lui même, tant qu'il y a un script en exécution pour un utilisateur, cet utilisateur ne peut lancer un second script.

Plusieurs utilisateurs peuvent utiliser le site en même temps et un même utilisateur peut naviguer simultanément sur plusieurs espace de nom de domaine.

Ceci est très embêtant pour les téléchargements de fichier passant par PHP5, ils bloquent tout le site pour l'utilisateur.

Ce problème survient sur, apparemment, tous les systèmes et quelque soit la configuration PHP5/Apache2.

Cela a été testé sur Ubuntu x64, Debian x32/x64 et Windows 7 x64.
Cela ne le fait pas en CLI.

Avez vous une solution de configuration ou autre ?!

NB: Ce message concerne d'assez loin les jeux mais il peut très bien vous intéresser.

[Zamentur]

Je croyais qu'ils étaient multi thread?

Par ailleurs je crois que ma version n'a pas ce problème, car je peux uploader et exécuter des pages php en même temps.

[Cartman34]

J'ai bien parlé ici de téléchargement via PHP (readfile()), pas d'upload. Mais on peut étendre ça à un script s'exécutant pendant un long moment et pendant ce long moment, impossible de charger une autre page.

J'ai essayé avec plusieurs versions mais j'ai toujours eu le même soucis.
Vous pouvez voir un exemple sur Staart.fr, tant que la vidéo n'a pas fini de charger, vous ne pourrez pas charger une nouvelle page.

[Sephi-Chan]

Ça me paraît bizarre ton affaire. Si Apache souffrait d'une telle limitation, il n'aurait pas la statut qu'il a de nos jours.

Peux-tu coller ton fichier de configuration (commentaires compris) qu'on voit un peu ?


Sephi-Chan

[Cartman34]

J'ai été autant surpris quand je me suis rendu compte de ça !

Voici le fichier apache2.conf

#
# Based upon the NCSA server configuration files originally by Rob McCool.
#
# This is the main Apache server configuration file. It contains the
# configuration directives that give the server its instructions.
# See http://httpd.apache.org/docs/2.2/ for detailed information about
# the directives.
#
# 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.
#
# The configuration directives are grouped into three basic sections:
# 1. Directives that control the operation of the Apache server process as a
# whole (the 'global environment').
# 2. Directives that define the parameters of the 'main' or 'default' server,
# which responds to requests that aren't handled by a virtual host.
# These directives also provide default values for the settings
# of all virtual hosts.
# 3. Settings for virtual hosts, which allow Web requests to be sent to
# different IP addresses or hostnames and have them handled by the
# same Apache server process.
#
# 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 "foo.log"
# with ServerRoot set to "/etc/apache2" will be interpreted by the
# server as "/etc/apache2/foo.log".
#

### Section 1: Global Environment
#
# The directives in this section affect the overall operation of Apache,
# such as the number of concurrent requests it can handle or where it
# can find its configuration files.
#

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE! If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the LockFile documentation (available
# at <URL:http://httpd.apache.org/docs-2.1/mod/mpm_common.html#lockfile>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
#
ServerRoot "/etc/apache2"
ServerName localhost

#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
LockFile ${APACHE_LOCK_DIR}/accept.lock

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
# This needs to be set in /etc/apache2/envvars
#
PidFile ${APACHE_PID_FILE}

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300

#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On

#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 15

##
## Server-Pool Size Regulation (MPM specific)
##

# prefork MPM
# StartServers: number of server processes to start
# MinSpareServers: minimum number of server processes which are kept spare
# MaxSpareServers: maximum number of server processes which are kept spare
# MaxClients: maximum number of server processes allowed to start
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule mpm_prefork_module>
StartServers 16
MinSpareServers 16
MaxSpareServers 64
MaxClients 128
MaxRequestsPerChild 64
</IfModule>

# worker MPM
# 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
# ThreadLimit: ThreadsPerChild can be changed to this maximum value during a
# graceful restart. ThreadLimit can only be changed by stopping
# and starting Apache.
# ThreadsPerChild: constant number of worker threads in each server process
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule mpm_worker_module>
StartServers 2
MinSpareThreads 25
MaxSpareThreads 75
ThreadLimit 64
ThreadsPerChild 25
MaxClients 150
MaxRequestsPerChild 0
</IfModule>

# event MPM
# 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 mpm_event_module>
StartServers 2
MaxClients 150
MinSpareThreads 25
MaxSpareThreads 75
ThreadLimit 64
ThreadsPerChild 25
MaxRequestsPerChild 0
</IfModule>

# These need to be set in /etc/apache2/envvars
User ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}

#
# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives. See also the AllowOverride
# directive.
#

AccessFileName .htaccess

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

#
# DefaultType is 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


#
# 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

# 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 ${APACHE_LOG_DIR}/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

# Include module configuration:
Include mods-enabled/*.load
Include mods-enabled/*.conf

# Include all the user configurations:
Include httpd.conf

# Include ports listing
Include ports.conf

#
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
# If you are behind a reverse proxy, you might want to change %h into %{X-Forwarded-For}i
#
LogFormat "%v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" vhost_combined
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %O" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent

# Include of directories ignores editors' and dpkg's backup files,
# see README.Debian for details.

# Include generic snippets of statements
Include conf.d/

# Include the virtual host configurations:
Include sites-enabled/

Le plus étonnant, c'est que ce n'est qu'en utilisant PHP via Apache2.
Si je télécharge un fichier directement via Apache2, je n'ai aucun soucis et PHP en CLI (avec plusieurs terminaux), je n'ai pas non plus de soucis.

[Sephi-Chan]

Utilises-tu Apache en mode Prefork ou en mode Worker ? Est-ce que PHP est utilisé via CGI (ou FastCGI) ou via mod_php ?


Sephi-Chan

[Cartman34]

PHP ne peut que s'exécuter sur Apache2 Prefork donc bon...
Il s'agit de la configuration par défaut (à ce niveau), je crois que c'est mod_php, non ?!

[niahoo]

si tu appelles une page web contenant

si tu appelles une page web contenant



<?php while(1) echo time(), "\n";

ça t'empêche d'appeler tout autre script php de ton serveur, c'est ça que tu veux dire ?

[Cartman34]

En gros oui, mais ca peut etre autre chose qu'un while, à partir du moment ou le script n'est pas terminé.

[niahoo]

oui oui, c'était pour me donner le temps de lancer un autre script en parallèle.

en tout cas c'est pas normal.