Bug 899382 (JBEWS-153) - Frequent 503 when using mod_cluster with Tomcat6
Summary: Frequent 503 when using mod_cluster with Tomcat6
Keywords:
Status: CLOSED DUPLICATE of bug 2040112
Alias: JBEWS-153
Product: JBoss Enterprise Web Server 1
Classification: JBoss
Component: unspecified
Version: EWS 1.0.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: EWS 1.0.2
Assignee: Permaine Cheung
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-31 16:00 UTC by Radoslav Husar
Modified: 2012-11-13 16:26 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
CR1
Last Closed: 2011-04-07 13:09:04 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 899385 0 urgent CLOSED mod_cluster doesn't failover with Tomcat backend 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker JBEWS-153 0 Major Closed Frequent 503 when using mod_cluster with Tomcat6 2015-06-19 16:55:39 UTC

Internal Links: 899385

Description Radoslav Husar 2011-03-31 16:00:39 UTC
project_key: JBEWS

If I just set up EWS with simple defaults, I get 503 straight away. I deployed a web app on one tomcat instance, and mod_cluster registered it (in mc mgmt console) but kept returning 503 codes. When the node without the app deployed was shut down, then it started to get responses from correct server. Attaching a small excerpt from before the error occurred. Reminds me of race condition, possibly related to JBPAPP-3614.

This is 1.0.8 - so how is this fixed in 1.0.9? (CR2)


{code}
[Thu Mar 31 17:41:22 2011] [debug] proxy_util.c(2011): proxy: AJP: has acquired connection for (127.0.0.1)
[Thu Mar 31 17:41:22 2011] [debug] proxy_util.c(2067): proxy: connecting ajp://127.0.0.1:8009/examples/jsp/ to 127.0.0.1:8009
[Thu Mar 31 17:41:22 2011] [debug] proxy_util.c(2193): proxy: connected /examples/jsp/ to 127.0.0.1:8009
[Thu Mar 31 17:41:22 2011] [debug] ajp_utils.c(31): Into ajp_handle_cping_cpong
[Thu Mar 31 17:41:22 2011] [debug] ajp_utils.c(102): ajp_handle_cping_cpong: Done
[Thu Mar 31 17:41:22 2011] [debug] ajp_header.c(224): Into ajp_marshal_into_msgb
[Thu Mar 31 17:41:22 2011] [debug] ajp_header.c(290): ajp_marshal_into_msgb: Header[0] [Host] = [localhost:8888]
[Thu Mar 31 17:41:22 2011] [debug] ajp_header.c(290): ajp_marshal_into_msgb: Header[1] [Connection] = [keep-alive]
[Thu Mar 31 17:41:22 2011] [debug] ajp_header.c(290): ajp_marshal_into_msgb: Header[2] [Referer] = [http://localhost:8888/]
[Thu Mar 31 17:41:22 2011] [debug] ajp_header.c(290): ajp_marshal_into_msgb: Header[3] [Cache-Control] = [max-age=0]
[Thu Mar 31 17:41:22 2011] [debug] ajp_header.c(290): ajp_marshal_into_msgb: Header[4] [User-Agent] = [Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16]
[Thu Mar 31 17:41:22 2011] [debug] ajp_header.c(290): ajp_marshal_into_msgb: Header[5] [Accept] = [application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5]
[Thu Mar 31 17:41:22 2011] [debug] ajp_header.c(290): ajp_marshal_into_msgb: Header[6] [Accept-Encoding] = [gzip,deflate,sdch]
[Thu Mar 31 17:41:22 2011] [debug] ajp_header.c(290): ajp_marshal_into_msgb: Header[7] [Accept-Language] = [en-GB,en-US;q=0.8,en;q=0.6]
[Thu Mar 31 17:41:22 2011] [debug] ajp_header.c(290): ajp_marshal_into_msgb: Header[8] [Accept-Charset] = [ISO-8859-1,utf-8;q=0.7,*;q=0.3]
[Thu Mar 31 17:41:22 2011] [debug] ajp_header.c(290): ajp_marshal_into_msgb: Header[9] [If-None-Match] = [W/"403-1301580712000"]
[Thu Mar 31 17:41:22 2011] [debug] ajp_header.c(290): ajp_marshal_into_msgb: Header[10] [If-Modified-Since] = [Thu, 31 Mar 2011 14:11:52 GMT]
[Thu Mar 31 17:41:22 2011] [debug] ajp_header.c(450): ajp_marshal_into_msgb: Done
[Thu Mar 31 17:41:22 2011] [debug] mod_proxy_ajp.c(265): proxy: APR_BUCKET_IS_EOS
[Thu Mar 31 17:41:22 2011] [debug] mod_proxy_ajp.c(270): proxy: data to read (max 8186 at 4)
[Thu Mar 31 17:41:22 2011] [debug] mod_proxy_ajp.c(285): proxy: got 0 bytes of data
[Thu Mar 31 17:41:22 2011] [debug] ajp_header.c(687): ajp_read_header: ajp_ilink_received 04
[Thu Mar 31 17:41:22 2011] [debug] ajp_header.c(697): ajp_parse_type: got 04
[Thu Mar 31 17:41:22 2011] [debug] ajp_header.c(516): ajp_unmarshal_response: status = 304
[Thu Mar 31 17:41:22 2011] [debug] ajp_header.c(537): ajp_unmarshal_response: Number of headers is = 2
[Thu Mar 31 17:41:22 2011] [debug] ajp_header.c(599): ajp_unmarshal_response: Header[0] [ETag] = [W/"403-1301580712000"]
[Thu Mar 31 17:41:22 2011] [debug] ajp_header.c(599): ajp_unmarshal_response: Header[1] [Content-Length] = [0]
[Thu Mar 31 17:41:22 2011] [debug] ajp_header.c(687): ajp_read_header: ajp_ilink_received 05
[Thu Mar 31 17:41:22 2011] [debug] ajp_header.c(697): ajp_parse_type: got 05
[Thu Mar 31 17:41:22 2011] [debug] mod_proxy_ajp.c(568): proxy: got response from 127.0.0.1:8009 (127.0.0.1)
[Thu Mar 31 17:41:22 2011] [debug] proxy_util.c(2029): proxy: AJP: has released connection for (127.0.0.1)
[Thu Mar 31 17:41:22 2011] [debug] mod_proxy_cluster.c(1735): cluster: Found value 3E926E44BF6BFB351E3F283783D39C80.tomcat6-1 for stickysession JSESSIONID|jsessionid
[Thu Mar 31 17:41:22 2011] [debug] mod_proxy_cluster.c(2064): cluster: Using route tomcat6-1
[Thu Mar 31 17:41:22 2011] [error] proxy: CLUSTER: (balancer://mycluster). All workers are in error state for route (tomcat6-1)
[Thu Mar 31 17:41:23 2011] [debug] mod_proxy_cluster.c(1735): cluster: Found value 3E926E44BF6BFB351E3F283783D39C80.tomcat6-1 for stickysession JSESSIONID|jsessionid
{code}

Comment 1 Jean-Frederic Clere 2011-04-01 06:46:17 UTC
I can't tell what is wrong, I would need a bigger trace... From the CONFIG/STATUS till the error at least.


Comment 2 Michal Karm Babacek 2011-04-01 08:49:37 UTC
@Jean I confirm the aforementioned results. It's actually the same problem that I reported earlier.
The same ill behaviour takes place with "undeploy web app" and "stop web app" scenarios as well;
in other words, it seems that fail over doesn't work at all.
What kind of log data you would like to have (different from those I provided earlier)?
If the setting "LogLevel debug" within the httpd instance is sufficient,
I would zip-and-attach logs from runs https://tcms.engineering.redhat.com/run/19248/ and https://tcms.engineering.redhat.com/run/19037/

Comment 3 Radoslav Husar 2011-04-06 11:53:41 UTC
Related JBPAPP-6257 but not exactly.

Comment 4 Radoslav Husar 2011-04-06 11:53:41 UTC
Link: Added: This issue is related to JBPAPP-6257


Comment 5 Jean-Frederic Clere 2011-04-07 13:09:04 UTC
See JBPAPP-6262


Note You need to log in before you can comment on or make changes to this bug.