[mod_cluster-issues] [JBoss JIRA] Commented: (MODCLUSTER-179) loosing connectivity with jboss on ajp
Gregory Lardiere (JIRA)
jira-events at lists.jboss.org
Thu Jul 22 12:55:39 EDT 2010
[ https://jira.jboss.org/browse/MODCLUSTER-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12540608#action_12540608 ]
Gregory Lardiere commented on MODCLUSTER-179:
---------------------------------------------
Sorry, here is the error :
[Thu Jul 22 16:32:59 2010] [error] (OS 10060)Une tentative de connexion a échoué car le parti connecté n'a pas répondu convenablement au-delà d'une certaine durée ou une connexion établie a échoué car l'hôte de connexion n'a pas répondu. : ajp_ilink_receive() can't receive header
[Thu Jul 22 16:32:59 2010] [error] ajp_read_header: ajp_ilink_receive failed
[Thu Jul 22 16:32:59 2010] [error] (120006)APR does not understand this error code: proxy: read response failed from 10.231.242.18:8009 (10.231.242.18)
[Thu Jul 22 16:32:59 2010] [debug] proxy_util.c(2017): proxy: AJP: has released connection for (10.231.242.18)
[Thu Jul 22 16:32:59 2010] [debug] mod_proxy_cluster.c(1582): cluster: Found value 2CF643D511FDA8971F315D93CD4D3CDC.svayn02a for stickysession JSESSIONID|jsessionid
[Thu Jul 22 16:32:59 2010] [debug] mod_proxy_cluster.c(1910): cluster: Using route svayn02a
[Thu Jul 22 16:32:59 2010] [debug] mod_proxy_cluster.c(924): get_balancer_by_node found context /vadautodirectmaaf
[Thu Jul 22 16:32:59 2010] [debug] mod_proxy.c(993): Running scheme balancer handler (attempt 0)
[Thu Jul 22 16:32:59 2010] [debug] mod_proxy_ajp.c(644): proxy: AJP: serving URL ajp://10.231.242.19:8009/vadautodirectmaaf/SA_ProductionAutoClientDirect_FX/fr/maaf/productionauto/clientdirect/decouvconduct/ecran/SaisieConducteurAdditionnel.swf;jsessionid=2CF643D511FDA8971F315D93CD4D3CDC.svayn02a
[Thu Jul 22 16:32:59 2010] [debug] proxy_util.c(1999): proxy: AJP: has acquired connection for (10.231.242.19)
The problem is easily reproducible under moderate load (38 threads in JMeter).
It seems to happen on request with long response time (~10s).
When we disable the AJP connector on JBoss (so that mod_cluster communicates with JBoss in HTTP instead of AJP), there is almost no error (just once in a quite long run).
> loosing connectivity with jboss on ajp
> --------------------------------------
>
> Key: MODCLUSTER-179
> URL: https://jira.jboss.org/browse/MODCLUSTER-179
> Project: mod_cluster
> Issue Type: Bug
> Affects Versions: 1.0.3.GA
> Environment: Windows server 2008
> Apache 2.2.13 + mod_cluster
> JBoss EAP 5.0.1
> Reporter: Gregory Lardiere
> Assignee: Jean-Frederic Clere
> Fix For: 1.0.4.GA
>
>
> During performance test of a jboss cluster (no session preserved) we issue some problem with mod_cluster, specially when apache try to access to the jboss instance through ajp
> And we don't see where the problem come from (JBoss configuration, mod_cluster configuration, bug).
> We don't use Multicast to discover nodes of the cluster
> [Thu Jul 22 15:13:14 2010] [debug] mod_manager.c(1416): manager_trans STATUS (/)
> [Thu Jul 22 15:13:14 2010] [debug] mod_manager.c(1929): manager_handler STATUS (D:/) processing: "JVMRoute=svayn02a&Load=90"
> [Thu Jul 22 15:13:14 2010] [debug] proxy_util.c(1999): proxy: ajp: has acquired connection for (10.231.242.19)
> [Thu Jul 22 15:13:14 2010] [debug] proxy_util.c(2055): proxy: connecting ajp://10.231.242.19:8009/ to 10.231.242.19:8009
> [Thu Jul 22 15:13:14 2010] [debug] proxy_util.c(2153): proxy: connected ajp://10.231.242.19:8009/ to 10.231.242.19:8009
> [Thu Jul 22 15:13:14 2010] [debug] mod_proxy_cluster.c(1194): ajp_cping_cpong: Done
> [Thu Jul 22 15:13:14 2010] [debug] proxy_util.c(2017): proxy: ajp: has released connection for (10.231.242.19)
> [Thu Jul 22 15:13:14 2010] [debug] mod_manager.c(1970): manager_handler STATUS OK
> [Thu Jul 22 15:13:14 2010] [debug] mod_proxy_cluster.c(943): get_balancer_by_node balancer NOT found
> [Thu Jul 22 15:13:14 2010] [debug] mod_proxy_cluster.c(943): get_balancer_by_node balancer NOT found
> [Thu Jul 22 15:13:14 2010] [debug] mod_proxy_cluster.c(943): get_balancer_by_node balancer NOT found
> [Thu Jul 22 15:13:14 2010] [debug] mod_proxy_cluster.c(943): get_balancer_by_node balancer NOT found
> [Thu Jul 22 15:13:14 2010] [debug] mod_proxy_cluster.c(943): get_balancer_by_node balancer NOT found
> [Thu Jul 22 15:13:14 2010] [debug] mod_proxy_cluster.c(943): get_balancer_by_node balancer NOT found
> [Thu Jul 22 15:13:14 2010] [debug] mod_proxy_cluster.c(943): get_balancer_by_node balancer NOT found
> [Thu Jul 22 15:13:14 2010] [debug] mod_proxy_cluster.c(943): get_balancer_by_node balancer NOT found
> [Thu Jul 22 15:13:14 2010] [debug] mod_manager.c(1416): manager_trans STATUS (/)
> [Thu Jul 22 15:13:14 2010] [debug] mod_manager.c(1929): manager_handler STATUS (D:/) processing: "JVMRoute=svayn01a&Load=90"
> [Thu Jul 22 15:13:14 2010] [debug] proxy_util.c(1999): proxy: ajp: has acquired connection for (10.231.242.18)
> [Thu Jul 22 15:13:14 2010] [debug] proxy_util.c(2055): proxy: connecting ajp://10.231.242.18:8009/ to 10.231.242.18:8009
> [Thu Jul 22 15:13:14 2010] [debug] proxy_util.c(2153): proxy: connected ajp://10.231.242.18:8009/ to 10.231.242.18:8009
> [Thu Jul 22 15:13:14 2010] [debug] mod_proxy_cluster.c(1194): ajp_cping_cpong: Done
> [Thu Jul 22 15:13:14 2010] [debug] proxy_util.c(2017): proxy: ajp: has released connection for (10.231.242.18)
> [Thu Jul 22 15:13:14 2010] [debug] mod_manager.c(1970): manager_handler STATUS OK
> Configuration :
> common.conf :
> LoadModule proxy_module modules/mod_proxy.so
> LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
> LoadModule slotmem_module modules/mod_slotmem.so
> LoadModule manager_module modules/mod_manager.so
> LoadModule proxy_cluster_module modules/mod_proxy_cluster.so
> [...]
> SSLSessionCache none
> MaxRequestsPerChild 5000
> #MaxRequestsPerChild 0
> MaxMemFree 512
> #JkWatchdogInterval 60
> ThreadLimit 300
> ThreadsPerChild 300
> svayn.conf :
> PidFile var/svayn/httpd.pid
> Include conf/common.conf
> Listen 10.231.241.243:8031 http
> #Listen 10.231.241.243:8444 https
> MemManagerFile d:/Apache/var/svayn/manager
> ErrorLog d:/logs/apache/svayn/error.log
> #CustomLog d:/logs/apache/svayn/access.log combined
> NameVirtualHost 10.231.241.243:8031
> #NameVirtualHost 10.231.241.243:8444
> #SSLCertificateFile d:/certs/svayn/cert.crt
> #SSLCertificateKeyFile d:/certs/svayn/cert.key
> <Location />
> <LimitExcept OPTIONS GET HEAD POST PUT DELETE>
> Order deny,allow
> Deny from all
> Allow from wse0846.maafprod.e-corail.com wse0847.maafprod.e-corail.com 127.0.0.1
> </LimitExcept>
> </Location>
> <VirtualHost 10.231.241.243:8031>
> ServerName localhost
> DocumentRoot d:/www/empty
> <Location /cluster-status>
> SetHandler mod_cluster-manager
> Order deny,allow
> Deny from all
> Allow from 10.231.241.243 127.0.0.1
> </Location>
> <Location /server-status>
> SetHandler server-status
> Order deny,allow
> Deny from all
> Allow from 10.231.241.243 127.0.0.1
> </Location>
> </VirtualHost>
> #<VirtualHost 10.231.241.243:8444>
> # ServerName localhost
> # DocumentRoot d:/www/empty
> # SSLEngine on
> #</VirtualHost>
> <VirtualHost 10.231.241.243:8031>
> ServerName nsiperf.maafprod.e-corail.com
> ServerAlias nsiperf
> DocumentRoot d:/www/svayn/
> RewriteEngine on
> RewriteRule ^/(index.asp)?$ /vadautodirectmaaf/SA_ProductionAutoClientDirect_FX/SA_ProductionAutoClientDirect_FX.html?destination=AccesPublicCE&entryPoint=AccesPublicDefaut&enseigne=MAAF&contexte=D4RNMAAF [NC,R=301,L]
> UseAlias 1
> KeepAliveTimeout 60
> MaxKeepAliveRequests 0
> </VirtualHost>
> #<VirtualHost 10.231.241.243:8444>
> # ServerName nsiperf.maafprod.e-corail.com
> # ServerAlias nsiperf
> # DocumentRoot d:/www/svayn/
> # RewriteEngine on
> # RewriteRule ^/(index.asp)?$ /vadautodirectmaaf/SA_ProductionAutoClientDirect_FX/SA_ProductionAutoClientDirect_FX.html?destination=AccesPublicCE&entryPoint=AccesPublicDefaut&enseigne=MAAF&contexte=D4RNMAAF [NC,R=301,L]
> # SSLEngine on
> #</VirtualHost>
> Thx for your help.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the mod_cluster-issues
mailing list