July 2009 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] Closed: (MODCLUSTER-37) Allow static content to be served from proxy's local filesystem.

by Jean-Frederic Clere (JIRA)

[ https://jira.jboss.org/jira/browse/MODCLUSTER-37?page=com.atlassian.jira.... ] Jean-Frederic Clere closed MODCLUSTER-37. ----------------------------------------- Resolution: Done Fixed in r2495 > Allow static content to be served from proxy's local filesystem. > ---------------------------------------------------------------- > > Key: MODCLUSTER-37 > URL: https://jira.jboss.org/jira/browse/MODCLUSTER-37 > Project: mod_cluster > Issue Type: Feature Request > Reporter: Jason Rupard > Assignee: Jean-Frederic Clere > Fix For: 1.0.1.GA > > > Allow web server to serve static content from local file system. > For example, /webapp1, is a web application in JBoss and is proxied through Apache via mod_cluster. All URLs /webapp1/* are proxied. Create Jboss/mod_cluster/Apache configuration to serve static content from the web server. Allow patterns (or globbing) for matching of URLs > Example URL patterns: > /webapp1/static/* > /webapp1/*.jpg > This is similar to what can be accomplished by JKMount in mod_jk. > BONUS Feature: > Create feature in such a way that URLs could be reverse proxied via mod_proxy to other web servers, /webapp1/static/ --> http://webserver/static/, instead of local file system. > -- 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

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-80) httpd crashes when you try to reach an application disabled via /mod_cluster-manager

by Jean-Frederic Clere (JIRA)

httpd crashes when you try to reach an application disabled via /mod_cluster-manager ------------------------------------------------------------------------------------ Key: MODCLUSTER-80 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-80 Project: mod_cluster Issue Type: Bug Affects Versions: 1.0.0.GA Environment: See http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242664#4242664 Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere Priority: Blocker It cores in hassession_byname because conf is null. -- 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

15 years, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-81) DISABLE application gets request without sessionid.

by Jean-Frederic Clere (JIRA)

DISABLE application gets request without sessionid. --------------------------------------------------- Key: MODCLUSTER-81 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-81 Project: mod_cluster Issue Type: Bug Environment: Any Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere Fix For: 1.0.0.GA Configure 2 nodes. Use mod_cluster-manager to disable an application in the first node displayed in the mod_cluster-manager page, try requests without sessionid some of the requests will go to the wrong node. -- 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

15 years, 5 months

1
4
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-78) Add support for JBossAS 4.2.x

by Jean-Frederic Clere (JIRA)

Add support for JBossAS 4.2.x ----------------------------- Key: MODCLUSTER-78 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-78 Project: mod_cluster Issue Type: Feature Request Environment: May be that is just doco to use it like with Tomcat. Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere mod_cluster works for Tomcat and JBossAS 5.x would be nice to have it also for 4.2.x and 4.3.x -- 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

15 years, 5 months

1
4
0 / 0

[JBoss JIRA] Updated: (MODCLUSTER-50) mod_cluster-manager: disabling a worker / domain

by Jean-Frederic Clere (JIRA)

[ https://jira.jboss.org/jira/browse/MODCLUSTER-50?page=com.atlassian.jira.... ] Jean-Frederic Clere updated MODCLUSTER-50: ------------------------------------------ Fix Version/s: 1.0.1.GA > mod_cluster-manager: disabling a worker / domain > ------------------------------------------------ > > Key: MODCLUSTER-50 > URL: https://jira.jboss.org/jira/browse/MODCLUSTER-50 > Project: mod_cluster > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Jean-Frederic Clere > Fix For: 1.0.1.GA > > > In mod-jk, we had the ability to disable and/or stop a worker. Disabling a wroker W meant that existing sessions would be served, but new sessions would not be created on W, until W was enabled again. > I'd like to have the same capability in mod-cluster. It would be good to have > * this capability added to /mod_cluster-manager and possibly > * provide a script (in jboss/bin ?) which allows an admin to do the > same thing, e.g. "./disable-worker.sh node2" or "./disable-domain D3" > The functionality should include > * Disabling a worker W > * Stopping a worker W. Note that we can achive this by shutting W > down, but 'stopping a worker' merely removes W from httpd's worker > list, but doesn't require a shutdown of W (W would also not > register with httpd at this point) > * Starting a worker W. The opposite of stopping W. Have W resume > registering with httpd > * Enabling a worker W. Allows for new sessions to be created on W > * Disabling / stopping / starting / enabling a domain D. Same as > above, but for all workers in a given domain D. > * It would be nice to be notified when all sessions in a disabled > domain have expired -- 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

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Work started: (MODCLUSTER-50) mod_cluster-manager: disabling a worker / domain

by Jean-Frederic Clere (JIRA)

[ https://jira.jboss.org/jira/browse/MODCLUSTER-50?page=com.atlassian.jira.... ] Work on MODCLUSTER-50 started by Jean-Frederic Clere. > mod_cluster-manager: disabling a worker / domain > ------------------------------------------------ > > Key: MODCLUSTER-50 > URL: https://jira.jboss.org/jira/browse/MODCLUSTER-50 > Project: mod_cluster > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Jean-Frederic Clere > Fix For: 1.0.1.GA > > > In mod-jk, we had the ability to disable and/or stop a worker. Disabling a wroker W meant that existing sessions would be served, but new sessions would not be created on W, until W was enabled again. > I'd like to have the same capability in mod-cluster. It would be good to have > * this capability added to /mod_cluster-manager and possibly > * provide a script (in jboss/bin ?) which allows an admin to do the > same thing, e.g. "./disable-worker.sh node2" or "./disable-domain D3" > The functionality should include > * Disabling a worker W > * Stopping a worker W. Note that we can achive this by shutting W > down, but 'stopping a worker' merely removes W from httpd's worker > list, but doesn't require a shutdown of W (W would also not > register with httpd at this point) > * Starting a worker W. The opposite of stopping W. Have W resume > registering with httpd > * Enabling a worker W. Allows for new sessions to be created on W > * Disabling / stopping / starting / enabling a domain D. Same as > above, but for all workers in a given domain D. > * It would be nice to be notified when all sessions in a disabled > domain have expired -- 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

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-79) View in memory mod_proxy and mod_proxy_balancer configuration

by Ben Schofield (JIRA)

View in memory mod_proxy and mod_proxy_balancer configuration ------------------------------------------------------------- Key: MODCLUSTER-79 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-79 Project: mod_cluster Issue Type: Feature Request Affects Versions: 1.0.0.GA Environment: All Reporter: Ben Schofield Assignee: Jean-Frederic Clere To facilitate debugging and troubleshooting it would be helpful to be able to easily view the in memory configuration of mod_proxy and mod_proxy_balancer. Maybe have config files that stay in sync with the in memory changes or an option in the mod_cluster-manager to dump the current configuration. -- 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

15 years, 5 months

2
9
0 / 0

[JBoss JIRA] Updated: (MODCLUSTER-54) Use slotmems from httpd-trunk

by Jean-Frederic Clere (JIRA)

[ https://jira.jboss.org/jira/browse/MODCLUSTER-54?page=com.atlassian.jira.... ] Jean-Frederic Clere updated MODCLUSTER-54: ------------------------------------------ Priority: Minor (was: Major) > Use slotmems from httpd-trunk > ----------------------------- > > Key: MODCLUSTER-54 > URL: https://jira.jboss.org/jira/browse/MODCLUSTER-54 > Project: mod_cluster > Issue Type: Feature Request > Environment: mod_cluster httpd-trunk > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Priority: Minor > > My old code of httpd-proxy-scoreboard has been moved to httpd-trunk we should stop using our own "forked" version of slotmems. -- 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

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-74) Simplifiy the slotmem logic to use httpd-trunk one

by Jean-Frederic Clere (JIRA)

Simplifiy the slotmem logic to use httpd-trunk one -------------------------------------------------- Key: MODCLUSTER-74 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-74 Project: mod_cluster Issue Type: Feature Request Environment: Code Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere The slomem in httpd-trunk is quite different from the one we use. We should try to use common code. httpd doesn't use a alloc/free logic. httpd lock should be remove (dev list decision and it makes sense). -- 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

15 years, 5 months

1
1
0 / 0

[JBoss JIRA] Updated: (MODCLUSTER-37) Allow static content to be served from proxy's local filesystem.

by Jean-Frederic Clere (JIRA)

[ https://jira.jboss.org/jira/browse/MODCLUSTER-37?page=com.atlassian.jira.... ] Jean-Frederic Clere updated MODCLUSTER-37: ------------------------------------------ Fix Version/s: 1.0.1.GA > Allow static content to be served from proxy's local filesystem. > ---------------------------------------------------------------- > > Key: MODCLUSTER-37 > URL: https://jira.jboss.org/jira/browse/MODCLUSTER-37 > Project: mod_cluster > Issue Type: Feature Request > Reporter: Jason Rupard > Assignee: Jean-Frederic Clere > Fix For: 1.0.1.GA > > > Allow web server to serve static content from local file system. > For example, /webapp1, is a web application in JBoss and is proxied through Apache via mod_cluster. All URLs /webapp1/* are proxied. Create Jboss/mod_cluster/Apache configuration to serve static content from the web server. Allow patterns (or globbing) for matching of URLs > Example URL patterns: > /webapp1/static/* > /webapp1/*.jpg > This is similar to what can be accomplished by JKMount in mod_jk. > BONUS Feature: > Create feature in such a way that URLs could be reverse proxied via mod_proxy to other web servers, /webapp1/static/ --> http://webserver/static/, instead of local file system. > -- 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

15 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues July 2009