April 2013 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] (MODCLUSTER-334) mod_cluster core when use ProxyPass / balancer://bal and CreateBalancers 1

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-334?page=com.atlassian.jira.pl... ] Jean-Frederic Clere resolved MODCLUSTER-334. -------------------------------------------- Resolution: Done Fix by 08be77c8c393d421ca9c1abb7145fd006165df70 > mod_cluster core when use ProxyPass / balancer://bal and CreateBalancers 1 > -------------------------------------------------------------------------- > > Key: MODCLUSTER-334 > URL: https://issues.jboss.org/browse/MODCLUSTER-334 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.2.4.Final > Environment: Any > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Fix For: 1.2.5.Final > > > Use something like: > ProxyPass / balancer://neo5 > CreateBalancers 1 > When the first STATUS is received from a node using the balancer (neo5) httpd will dump a core. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-334) mod_cluster core when use ProxyPass / balancer://bal and CreateBalancers 1

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-334?page=com.atlassian.jira.pl... ] Jean-Frederic Clere commented on MODCLUSTER-334: ------------------------------------------------ the work-around is easy use: ProxyPass / balancer://neo5 stickysession=JSESSIONID|jsessionid > mod_cluster core when use ProxyPass / balancer://bal and CreateBalancers 1 > -------------------------------------------------------------------------- > > Key: MODCLUSTER-334 > URL: https://issues.jboss.org/browse/MODCLUSTER-334 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.2.4.Final > Environment: Any > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Fix For: 1.2.5.Final > > > Use something like: > ProxyPass / balancer://neo5 > CreateBalancers 1 > When the first STATUS is received from a node using the balancer (neo5) httpd will dump a core. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-334) mod_cluster core when use ProxyPass / balancer://bal and CreateBalancers 1

by Aaron Ogburn (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-334?page=com.atlassian.jira.pl... ] Aaron Ogburn updated MODCLUSTER-334: ------------------------------------ > mod_cluster core when use ProxyPass / balancer://bal and CreateBalancers 1 > -------------------------------------------------------------------------- > > Key: MODCLUSTER-334 > URL: https://issues.jboss.org/browse/MODCLUSTER-334 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.2.4.Final > Environment: Any > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Fix For: 1.2.5.Final > > > Use something like: > ProxyPass / balancer://neo5 > CreateBalancers 1 > When the first STATUS is received from a node using the balancer (neo5) httpd will dump a core. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-334) mod_cluster core when use ProxyPass / balancer://bal and CreateBalancers 1

by Jean-Frederic Clere (JIRA)

Jean-Frederic Clere created MODCLUSTER-334: ---------------------------------------------- Summary: mod_cluster core when use ProxyPass / balancer://bal and CreateBalancers 1 Key: MODCLUSTER-334 URL: https://issues.jboss.org/browse/MODCLUSTER-334 Project: mod_cluster Issue Type: Feature Request Affects Versions: 1.2.4.Final Environment: Any Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere Fix For: 1.2.5.Final Use something like: ProxyPass / balancer://neo5 CreateBalancers 1 When the first STATUS is received from a node using the balancer (neo5) httpd will dump a core. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-168) mod_cluster should use hostname provided in address instead a IP address

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-168?page=com.atlassian.jira.pl... ] Jean-Frederic Clere updated MODCLUSTER-168: ------------------------------------------- Fix Version/s: 1.2.5.Final (was: 1.2.4.Final) > mod_cluster should use hostname provided in address instead a IP address > ------------------------------------------------------------------------ > > Key: MODCLUSTER-168 > URL: https://issues.jboss.org/browse/MODCLUSTER-168 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.1.0.CR3 > Environment: any > Reporter: Jean-Frederic Clere > Assignee: Paul Ferraro > Fix For: 1.2.5.Final > > > The CONFIG message contains something like: > JVMRoute=51ec121e-2976-3d75-bfd9-9e662bbb4bcd&Host=10.33.144.3&Port=8009&Type=ajp > Even if the Connector is defined like: > <Connector port="8009" address= "jfcpc" protocol="AJP/1.3" redirectPort="8443" /> > There are 2 ways to fix: > - Use the String (Change the Connector.java in mod_cluster). > - Use parameters.put("Host", connector.getAddress().getHostName()); when building the CONFIG message. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-329) Add ModClusterService methods to obtain status of a context

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-329?page=com.atlassian.jira.pl... ] Jean-Frederic Clere updated MODCLUSTER-329: ------------------------------------------- Fix Version/s: 1.2.5.Final (was: 1.2.4.Final) > Add ModClusterService methods to obtain status of a context > ----------------------------------------------------------- > > Key: MODCLUSTER-329 > URL: https://issues.jboss.org/browse/MODCLUSTER-329 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.2.3.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 1.2.5.Final > > > In order for AS7 management operations like "stop-context" to figure out how to properly rollback, they need to know the initial status of the context. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-330) Demo webapp doesn't work on AS7

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-330?page=com.atlassian.jira.pl... ] Jean-Frederic Clere updated MODCLUSTER-330: ------------------------------------------- Fix Version/s: 1.2.5.Final (was: 1.2.4.Final) > Demo webapp doesn't work on AS7 > ------------------------------- > > Key: MODCLUSTER-330 > URL: https://issues.jboss.org/browse/MODCLUSTER-330 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.3.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 1.2.5.Final > > > The demo webapp contains references to org.apache.catalina classes, but does not properly include these dependencies in its MANIFEST.MF. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-331) Add mod_cluster container SPI implementation for undertow

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-331?page=com.atlassian.jira.pl... ] Jean-Frederic Clere updated MODCLUSTER-331: ------------------------------------------- Fix Version/s: 1.2.5.Final (was: 1.2.4.Final) > Add mod_cluster container SPI implementation for undertow > --------------------------------------------------------- > > Key: MODCLUSTER-331 > URL: https://issues.jboss.org/browse/MODCLUSTER-331 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.2.3.Final > Reporter: Paul Ferraro > Assignee: Radoslav Husar > Fix For: 1.2.5.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-332) Add Engine.getExecutor() to container SPI

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-332?page=com.atlassian.jira.pl... ] Jean-Frederic Clere updated MODCLUSTER-332: ------------------------------------------- Fix Version/s: 1.2.5.Final (was: 1.2.4.Final) > Add Engine.getExecutor() to container SPI > ----------------------------------------- > > Key: MODCLUSTER-332 > URL: https://issues.jboss.org/browse/MODCLUSTER-332 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.2.3.Final > Reporter: Paul Ferraro > Assignee: Jean-Frederic Clere > Fix For: 1.2.5.Final > > > This is required to expose some mechanism to configure the STATUS interval. Currently, the web subsystem in AS7 has no mechanism to configure the background process period of the Engine. An Engine.getExecutor() container SPI method would allow the mod_cluster subsystem to configure its own executor to control this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-71) Handle multiple versions of the same webapp

by Dominique CLAIRAC (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-71?page=com.atlassian.jira.plu... ] Dominique CLAIRAC commented on MODCLUSTER-71: --------------------------------------------- We have the same problem. On JBoss side, we have two server groups (A and B) with two JBoss Full-HA servers in each group. On mod_cluster side: - Each server of a same server group is declared in an unique "load-balancing-group", so we have 2 LBGroup with 2 nodes in each. - Requests are routed to goup A or Group B, depending on the load and session affinity. During an application update: - We disable the Node B to drain sessions to the node A. - We then update the application with the new version on server group B with autoEnableContexts = false (It should be better to have stopped status than disabled when autoEnableContexts is false, because application is still accessible for someone with node JVM_ROOT in an old JSESSION_ID). Then we would like administrators to test the application before draining requests from A to B (new version activation). After reflection, I would suggest something like this: Choice 1: On JBoss side, possibility that the application is declared as STOPPED rather than DISABLED on deployment On cluster_manager UI: ability to generate a token associated with a server or LB group, which will be stored in a cookie. On request with this token, mod_cluster must send the request to the node or the LB group associated to the token, even if the application is marked as STOPPED on it. Choice 2: Ability to declare an IP range as the test network in mod_cluster apache configuration (eg: mod_cluster_test_network = 192.168.174.0) Have a property (eg "test_mode") in the mod_cluster subsystem on jboss side. If test_mode is true, only requests from the mod_cluster_test_network network can reach the server in question) Whith this solution, we juste have to change the value of "test_mode" on jboss conf to achieve our goal > Handle multiple versions of the same webapp > ------------------------------------------- > > Key: MODCLUSTER-71 > URL: https://issues.jboss.org/browse/MODCLUSTER-71 > Project: mod_cluster > Issue Type: Feature Request > Reporter: Brian Stansberry > Assignee: Jean-Frederic Clere > > This is a big picture future roadmap kind of thing. > Assume the AS develops the ability to host two versions of the same webapp concurrently. Imagine a workflow like this: > 1) Version 1 is running, handling requests > 2) Version 2 is deployed, is allowed to receive a low workload to validate that it works properly. > 3) Version 2 is shifted to allow full workload > 4) Version 1 is put into disabled mode to drain sessions > 5) Version 1. is undeployed. > Obviously making this work requires a lot of currently non-existent stuff in the AS. Point of this JIRA is think about how to deal with it at the mod_cluster level. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues April 2013