mod_cluster-issues December 2010

mod_cluster-issues@lists.jboss.org

1 participants
34 discussions

[JBoss JIRA] Created: (MODCLUSTER-202) the STATUS MCMP message is send before the connector is started

by Jean-Frederic Clere (JIRA)

the STATUS MCMP message is send before the connector is started --------------------------------------------------------------- Key: MODCLUSTER-202 URL: https://issues.jboss.org/browse/MODCLUSTER-202 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.0.Final, 1.0.5 Environment: any Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere Priority: Minor If you have an application slow to start the STATUS messages are sent before the connectors are started which causes error messages to be written in the log. Additionally that can delay the availability of the application to httpd. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
6
0 / 0

[JBoss JIRA] Updated: (MODCLUSTER-201) update mod_cluster to use HTTP/1.1

by Samuel Mendenhall (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-201?page=com.atlassian.jira.pl... ] Samuel Mendenhall updated MODCLUSTER-201: ----------------------------------------- Fix Version/s: 1.1.1.Final Affects Version/s: 1.1.0.Final > update mod_cluster to use HTTP/1.1 > ---------------------------------- > > Key: MODCLUSTER-201 > URL: https://issues.jboss.org/browse/MODCLUSTER-201 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.1.0.Final > Reporter: Samuel Mendenhall > Assignee: Jean-Frederic Clere > Priority: Minor > Fix For: 1.1.1.Final > > > Certain technologies like siteminder require the host header which is not present in HTTP/1.0 so siteminder won't work out of the box with HTTP/1.0 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-195) mod_cluster-manager does not update when a node is taken down

by Samuel Mendenhall (JIRA)

mod_cluster-manager does not update when a node is taken down ------------------------------------------------------------- Key: MODCLUSTER-195 URL: https://jira.jboss.org/browse/MODCLUSTER-195 Project: mod_cluster Issue Type: Bug Affects Versions: 1.0.4.GA Environment: mod_cluster 1.0.4.GA EAP 5.0.1.GA Reporter: Samuel Mendenhall Assignee: Jean-Frederic Clere Priority: Minor Fix For: 1.0.5 The mod_cluster-manager status page does not get updated on failover, the node still shows up as active and available balancer: [1] Name: mycluster Sticky: 1 [JSESSIONID]/[jsessionid] remove: 0 force: 0 Timeout: 0 Maxtry: 1 node: [1:1],Balancer: mycluster,JVMRoute: node01,Domain: [],Host: 10.0.242.204,Port: 8009,Type: ajp,flushpackets: 0,flushwait: 10,ping: 10,smax: 1,ttl: 60,timeout: 0 node: [2:2],Balancer: mycluster,JVMRoute: node02,Domain: [],Host: 10.0.242.205,Port: 8009,Type: ajp,flushpackets: 0,flushwait: 10,ping: 10,smax: 1,ttl: 60,timeout: 0 host: 1 [localhost] vhost: 1 node: 1 host: 2 [localhost] vhost: 1 node: 2 context: 1 [/load-demo] vhost: 1 node: 1 status: 1 context: 2 [/thespike] vhost: 1 node: 1 status: 1 context: 3 [/load-demo] vhost: 1 node: 2 status: 1 context: 4 [/thespike] vhost: 1 node: 2 status: 1 This behaviour is already fixed in mod_cluster 1.1.x, just needs to be backported to 1.0.x and included in the EAP. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
2
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-196) Incorrect routing of requests when one context root is the prefix of another

by Ben Schofield (JIRA)

Incorrect routing of requests when one context root is the prefix of another ---------------------------------------------------------------------------- Key: MODCLUSTER-196 URL: https://jira.jboss.org/browse/MODCLUSTER-196 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.0.Final Environment: Apache 2.2.9 mod_cluster 1.1.0 JBoss EAP 5.0.1 Reporter: Ben Schofield Assignee: Jean-Frederic Clere JBoss instance A hosts application A which has a context root of /abc. JBoss instance B hosts application B which has a context root of /abc/xyz A and B are not in the same cluster. The behavior is the requests meant for application B are getting routed to application A on JBoss instance A and the result is an http error 404. A request to /abc/xyz/my.jsp should correctly go to application B on JBoss instance B. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
4
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 December 2010