mod_cluster-issues June 2011

mod_cluster-issues@lists.jboss.org

1 participants
33 discussions

[JBoss JIRA] Created: (MODCLUSTER-240) mod_cluster does not work with Tomcat 7 due to API Change in Connector

by C Giess (JIRA)

mod_cluster does not work with Tomcat 7 due to API Change in Connector ---------------------------------------------------------------------- Key: MODCLUSTER-240 URL: https://issues.jboss.org/browse/MODCLUSTER-240 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.2.Final Environment: Tomcat 7.0.14 Reporter: C Giess Assignee: Jean-Frederic Clere Priority: Critical The method "isAvailable* is no longer available in Tomcats Connector-Class. {code} Jun 6, 2011 4:14:16 PM org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor processChildren SEVERE: Exception invoking periodic operation: java.lang.NoSuchMethodError: org.apache.catalina.connector.Connector.isAvailable()Z at org.jboss.modcluster.catalina.CatalinaConnector.isAvailable(CatalinaConnector.java:154) at org.jboss.modcluster.ModClusterService.status(ModClusterService.java:488) at org.jboss.modcluster.catalina.CatalinaEventHandlerAdapter.lifecycleEvent(CatalinaEventHandlerAdapter.java:323) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:89) at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1233) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1391) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1380) at java.lang.Thread.run(Thread.java:662) {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-239) Failover triggers 500 Internal Server Error

by Jean-Frederic Clere (JIRA)

Failover triggers 500 Internal Server Error ------------------------------------------- Key: MODCLUSTER-239 URL: https://issues.jboss.org/browse/MODCLUSTER-239 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.2.Final , 1.0.10 Environment: failover tests killing nodes with -9 Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere Fix For: MOD_CLUSTER_1_0_10_GA_CP01, 1.1.3.Final the access_log contains errors like: 10.16.89.42 - - [24/May/2011:13:54:52 -0500] "GET /st/SessionTestServlet? HTTP/1.1" 500 608 "-" "Jakarta Commons-HttpClient/3.1" error_log in debug shows the corresponding error: +++ [Tue May 24 13:54:52 2011] [debug] mod_proxy_cluster.c(1245): proxy: byrequests balancer DONE (ajp://10.16.88.180:8009) [Tue May 24 13:54:52 2011] [debug] mod_proxy.c(1015): Running scheme balancer handler (attempt 0) [Tue May 24 13:54:52 2011] [debug] mod_proxy_http.c(1955): proxy: HTTP: declining URL ajp://10.16.88.180:8009/st/SessionTestServlet? [Tue May 24 13:54:52 2011] [debug] mod_proxy_ajp.c(668): proxy: AJP: serving URL ajp://10.16.88.180:8009/st/SessionTestServlet? [Tue May 24 13:54:52 2011] [debug] proxy_util.c(2011): proxy: AJP: has acquired connection for (10.16.88.180) [Tue May 24 13:54:52 2011] [debug] proxy_util.c(2067): proxy: connecting ajp://10.16.88.180:8009/st/SessionTestServlet? to 10.16.88.180:8009 [Tue May 24 13:54:52 2011] [debug] proxy_util.c(2193): proxy: connected /st/SessionTestServlet? to 10.16.88.180:8009 [Tue May 24 13:54:52 2011] [debug] ajp_utils.c(31): Into ajp_handle_cping_cpong [Tue May 24 13:54:52 2011] [debug] ajp_utils.c(102): ajp_handle_cping_cpong: Done [Tue May 24 13:54:52 2011] [debug] ajp_header.c(224): Into ajp_marshal_into_msgb [Tue May 24 13:54:52 2011] [debug] ajp_header.c(290): ajp_marshal_into_msgb: Header[0] [User-Agent] = [Jakarta Commons-HttpClient/3.1] [Tue May 24 13:54:52 2011] [debug] ajp_header.c(290): ajp_marshal_into_msgb: Header[1] [Host] = [dev66:8888] [Tue May 24 13:54:52 2011] [debug] ajp_header.c(450): ajp_marshal_into_msgb: Done [Tue May 24 13:54:52 2011] [debug] mod_proxy_ajp.c(265): proxy: APR_BUCKET_IS_EOS [Tue May 24 13:54:52 2011] [debug] mod_proxy_ajp.c(270): proxy: data to read (max 8186 at 4) [Tue May 24 13:54:52 2011] [debug] mod_proxy_ajp.c(285): proxy: got 0 bytes of data [Tue May 24 13:54:52 2011] [debug] ajp_header.c(687): ajp_read_header: ajp_ilink_received 09 [Tue May 24 13:54:52 2011] [debug] ajp_header.c(697): ajp_parse_type: got 09 [Tue May 24 13:54:52 2011] [debug] mod_proxy_ajp.c(555): proxy: Processing of request failed backend: 1, output: 0 [Tue May 24 13:54:52 2011] [error] proxy: dialog to 10.16.88.180:8009 (10.16.88.180) failed +++ In fact it is due to failing cping/cpong a lot earlier: +++ [Tue May 24 13:52:30 2011] [error] ajp_cping_cpong: apr_socket_recv failed [Tue May 24 13:52:35 2011] [error] ajp_cping_cpong: apr_socket_recv failed +++ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

3
21
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-217) request hang with a node is stop in EC2

by Jean-Frederic Clere (JIRA)

request hang with a node is stop in EC2 --------------------------------------- Key: MODCLUSTER-217 URL: https://issues.jboss.org/browse/MODCLUSTER-217 Project: mod_cluster Issue Type: Bug Environment: EC2 Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere Priority: Minor Fix For: 1.0.10, 1.1.2.Final Once stopping the EC2 the socket is closed so the cping doesn't wait for ping but connectiontimeout which default to nodeTimeout and/or server timeout. That affects only the first request (per process) once the node has been cleaned. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
8
0 / 0

← Newer
1
2
3
4
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues June 2011