March 2010 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] Created: (MODCLUSTER-133) STATUS should retry the worker even if there was an error before.

by Jean-Frederic Clere (JIRA)

STATUS should retry the worker even if there was an error before. ----------------------------------------------------------------- Key: MODCLUSTER-133 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-133 Project: mod_cluster Issue Type: Bug Environment: any Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere Fix For: 1.1.0.CR1 Once an error occurs a STATUS should retry but the moment we have: +++ [Thu Feb 25 16:49:24 2010] [debug] ajp_header.c(687): ajp_read_header: ajp_ilink_received 09 [Thu Feb 25 16:49:24 2010] [debug] ajp_header.c(697): ajp_parse_type: got 09 [Thu Feb 25 16:49:24 2010] [debug] mod_proxy_ajp.c(540): proxy: Processing of request failed backend: 1, output: 0 [Thu Feb 25 16:49:24 2010] [error] proxy: dialog to 192.168.100.150:8009 (192.168.100.150) failed [Thu Feb 25 16:49:24 2010] [debug] proxy_util.c(2017): proxy: AJP: has released connection for (192.168.100.150) [Thu Feb 25 16:49:24 2010] [debug] mod_proxy_cluster.c(1118): proxy: byrequests balancer FAILED [Thu Feb 25 16:49:24 2010] [error] proxy: CLUSTER: (balancer://mycluster). All workers are in error state [Thu Feb 25 16:49:26 2010] [debug] mod_manager.c(1416): manager_trans STATUS (/) [Thu Feb 25 16:49:26 2010] [debug] mod_manager.c(1929): manager_handler STATUS (/) processing: "JVMRoute=node3&Load=78" [Thu Feb 25 16:49:26 2010] [debug] proxy_util.c(1937): proxy: ajp: retrying the worker for (192.168.100.150) [Thu Feb 25 16:49:26 2010] [error] proxy: ajp: disabled connection for (192.168.100.150) [Thu Feb 25 16:49:26 2010] [debug] mod_proxy_cluster.c(1333): proxy_cluster_isup: pingpong failed [Thu Feb 25 16:49:26 2010] [debug] mod_manager.c(1970): manager_handler STATUS OK [Thu Feb 25 16:49:36 2010] [debug] mod_manager.c(1416): manager_trans STATUS (/) [Thu Feb 25 16:49:36 2010] [debug] mod_manager.c(1929): manager_handler STATUS (/) processing: "JVMRoute=node3&Load=77" [Thu Feb 25 16:49:36 2010] [debug] proxy_util.c(1937): proxy: ajp: retrying the worker for (192.168.100.150) [Thu Feb 25 16:49:36 2010] [error] proxy: ajp: disabled connection for (192.168.100.150) +++ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-115) mod_cluster Manual Technical Review

by Gary Meintjes (JIRA)

mod_cluster Manual Technical Review ----------------------------------- Key: MODCLUSTER-115 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-115 Project: mod_cluster Issue Type: Task Environment: JBoss AS Reporter: Gary Meintjes Assignee: Patrick Macdonald Patrick, Please assign someone perform a technical review on this mod_cluster publication as discussed. The link to the publication is: http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_App... Many thanx, Gary Meintjes -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

3
2
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-141) Use versioned docs

by Paul Ferraro (JIRA)

Use versioned docs ------------------ Key: MODCLUSTER-141 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-141 Project: mod_cluster Issue Type: Task Affects Versions: 1.1.0.CR1 Reporter: Paul Ferraro Assignee: Jean-Frederic Clere Priority: Minor Trying to maintain one copy of the documentation for multiple versions simultaneously is proving to be a pain in the @ss... Magnolia is very cumbersome as a documentation tool because of its treatment of "paragraphs", especially with respect to code fragments (of which our docs have many). I recommend we keep all of the documentation in subversion (using doxia, docbook or similar) so that it is versioned along with the source code. The download page would contain links to the docs along side binary and source distributions. This seems to be how most jboss.org projects are setup. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
6
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-139) Allow override of default clean shutdown behavior

by Paul Ferraro (JIRA)

Allow override of default clean shutdown behavior ------------------------------------------------- Key: MODCLUSTER-139 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-139 Project: mod_cluster Issue Type: Feature Request Affects Versions: 1.1.0.CR1 Reporter: Paul Ferraro Assignee: Paul Ferraro Priority: Minor Fix For: 1.1.0.CR2 By default, if a web-app is declared <distributable/>, we will only wait until there are no pending requests and all sessions are safely replicated. Only if a web-app is not <distributable/>, do we wait until there are no more active sessions, since there is no session replication. We need the ability to allow the user to override this default behavior, and use session draining even for <distributable/> apps, to avoid overloading remaining servers with failover requests. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-135) update zlib to 1.2.4

by Jean-Frederic Clere (JIRA)

update zlib to 1.2.4 --------------------- Key: MODCLUSTER-135 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-135 Project: mod_cluster Issue Type: Feature Request Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
5
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-128) INFO and mod_cluster_manager/ displays milliseconds and DUMP second

by Jean-Frederic Clere (JIRA)

INFO and mod_cluster_manager/ displays milliseconds and DUMP second ------------------------------------------------------------------- Key: MODCLUSTER-128 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-128 Project: mod_cluster Issue Type: Bug Environment: any Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere Priority: Optional It is just a problem of display or documentation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
5
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-137) Add a solaris10 64 bits sparc in the bundles.

by Jean-Frederic Clere (JIRA)

Add a solaris10 64 bits sparc in the bundles. --------------------------------------------- Key: MODCLUSTER-137 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-137 Project: mod_cluster Issue Type: Feature Request Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere Fix For: 1.1.0.CR2 Add a solaris10 64 bits sparc in the bundles. Note it needs some cflags like -m64 -xmemalign=8s -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
7
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-138) Allow configuration of stopContextTimeout units

by Paul Ferraro (JIRA)

Allow configuration of stopContextTimeout units ----------------------------------------------- Key: MODCLUSTER-138 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-138 Project: mod_cluster Issue Type: Feature Request Affects Versions: 1.1.0.CR1 Reporter: Paul Ferraro Assignee: Paul Ferraro Priority: Minor Fix For: 1.1.0.CR2 Currently, the value specified in stopContextTimeout configuration property is specified in seconds. For completions sake, we should add a second property to define the units of this property, with default of TimeUnit.SECONDS. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-142) Use UUID for auto-generated jvmRoute

by Paul Ferraro (JIRA)

Use UUID for auto-generated jvmRoute ------------------------------------ Key: MODCLUSTER-142 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-142 Project: mod_cluster Issue Type: Feature Request Affects Versions: 1.1.0.CR1 Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 1.1.0.CR2 Currently, auto-generated jvm-routes are of the form: bind-address:port:engine-name This exposes internal addresses/ports and is not appropriate for production systems. To fix that, we can use UUIDs. e.g. InetAddress connectorAddress; int connectorPort; String engineName; int addressBytes = connectorAddress.getAddress().length; int intBytes = Integer.SIZE / Byte.SIZE; int charBytes = Character.SIZE / Byte.SIZE; ByteBuffer buffer = ByteBuffer.allocate(addressBytes + intBytes + (engineName.length() * charBytes)); buffer.put(connectorAddress.getAddress()); buffer.putInt(connectorPort); buffer.asCharBuffer().put(engine); String jvmRoute = UUID.nameUUIDFromBytes(buffer.array()).toString(); I can think of 2 disadvantages: 1. UUID jvm-routes will be, on average, longer than the current default, i.e. 36 characters as opposed to ~28. Not a significant difference there. 2. For development, exposing the address and port via the jvm route might be useful. To satisfy this requirement, we can make the use of UUIDs configurable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

3
4
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-109) 503 Service Temporarily Unavailable

by Karl Max (JIRA)

503 Service Temporarily Unavailable ------------------------------------ Key: MODCLUSTER-109 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-109 Project: mod_cluster Issue Type: Bug Affects Versions: 1.0.2.GA Environment: httpd+modcluster,seam 2.2.0GA,JBoss 5.1.0.GA Reporter: Karl Max Assignee: Jean-Frederic Clere When I use mod_cluster on startup/either node is failover sometimes I get 503 Service Temporarily Unavailable error -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues March 2010