April 2009 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] Created: (MODCLUSTER-72) Management operation to disable then stop node or webapp

by Brian Stansberry (JIRA)

Management operation to disable then stop node or webapp -------------------------------------------------------- Key: MODCLUSTER-72 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-72 Project: mod_cluster Issue Type: Feature Request Reporter: Brian Stansberry A common use case is to try to drain sessions from a server before taking it offline. With mod_cluster you can partially do that by invoking the JMX operation to disable a node, but then you need to manually monitor the # of active sessions so you can know when to stop the node. We should simplify this by adding an operation that tells the node to do the full disable-monitor session count-stop operation itself. -- 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, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-67) httpd crashes on windows when you kill JBoss AS

by Brian Stansberry (JIRA)

httpd crashes on windows when you kill JBoss AS ----------------------------------------------- Key: MODCLUSTER-67 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-67 Project: mod_cluster Issue Type: Bug Affects Versions: 1.0.0.CR1 Environment: Windows XP SP3 mod_cluster 1.0.0.CR1 using mod_proxy_ajp and mod_advertise 2 node cluster running an AS build that is approx AS 5.1.0.Beta1 Reporter: Brian Stansberry Assignee: Jean-Frederic Clere When playing with 1.0.0.CR1 on my windows laptop I decided to see how it would react to hard killing an AS instance. I was using the demo client, sending about 40 req / sec to a 2 node cluster. I used Windows Task Manager to kill one of the AS processes. Twice in a row this immediately resulted in httpd crashing. Windows asked if I wanted to send an error report; I agreed hoping I'd be able to extract some info to include with this report. It gave me a ton of likely useful stuff, but sadly puts it in a GUI dialog where there's no way to cut and paste it. -- 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, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-73) Advertise worker thread can throw NullPointerException on AdvertiseListener.destroy()

by Paul Ferraro (JIRA)

Advertise worker thread can throw NullPointerException on AdvertiseListener.destroy() ------------------------------------------------------------------------------------- Key: MODCLUSTER-73 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-73 Project: mod_cluster Issue Type: Bug Affects Versions: 1.0.0.CR1 Reporter: Paul Ferraro Assignee: Paul Ferraro Priority: Minor Fix For: 1.0.0.CR2 AdvertiseListenerImpl can throw a NullPointerException if AdvertiseListener.destroy() completes before the worker thread is done with the socket. +++ [java] Test DONE [java] Exception in thread "Thread-30" java.lang.NullPointerException [java] at org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl$AdvertiseListenerWorker.run(AdvertiseListenerImpl.java:422) +++ -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-69) Add ability to disable/enable all/individual apps on a worker from mod_cluster-manager status page

by Paul Ferraro (JIRA)

Add ability to disable/enable all/individual apps on a worker from mod_cluster-manager status page -------------------------------------------------------------------------------------------------- Key: MODCLUSTER-69 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-69 Project: mod_cluster Issue Type: Feature Request Affects Versions: 1.0.0.CR1 Reporter: Paul Ferraro Assignee: Jean-Frederic Clere Fix For: 1.0.0.CR2 Request from Bela. -- 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, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-70) openssl doesn't build on platfrom

by Jean-Frederic Clere (JIRA)

openssl doesn't build on platfrom --------------------------------- Key: MODCLUSTER-70 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-70 Project: mod_cluster Issue Type: Bug Environment: hudson build Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere Since the change to the lastest version openssl the ssl is not build on most of the supported plaforms -- 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, 8 months

1
4
0 / 0

[JBoss JIRA] Commented: (MODCLUSTER-1) Could The Web Tier Tell JBoss About Itself Via HTTP?

by Jean-Frederic Clere (JIRA)

[ https://jira.jboss.org/jira/browse/MODCLUSTER-1?page=com.atlassian.jira.p... ] Jean-Frederic Clere commented on MODCLUSTER-1: ---------------------------------------------- The would mean to add a logic in httpd mod_cluster to receive the multicast from the other httpd server and add a message/response to MCMP to request and forward that information to the nodes. But that means you have to define the first httpd proxy the cluster should find that goes against the automatic discovery and you have proxyList to specify the proxy the node can use. > Could The Web Tier Tell JBoss About Itself Via HTTP? > ---------------------------------------------------- > > Key: MODCLUSTER-1 > URL: https://jira.jboss.org/jira/browse/MODCLUSTER-1 > Project: mod_cluster > Issue Type: Feature Request > Reporter: Jimmy Wilson > Assignee: Paul Ferraro > Priority: Minor > > In cases where there is a firewall between Apache and JBoss, could the web tier use multicast to either tell the other Apache servers about itself or to retrieve the names of the JBoss servers from another Apache instance so that it (or another Apache instance) could use an HTTP request to tell the JBoss nodes about itself gaining automatic configuration even in the firewall case? -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (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 commented on MODCLUSTER-50: ----------------------------------------------- Note that MODCLUSTER-69 partially fix this one. > 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 > > 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, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-68) Add ability to disable/enable individual webapp via JMX

by Paul Ferraro (JIRA)

Add ability to disable/enable individual webapp via JMX ------------------------------------------------------- Key: MODCLUSTER-68 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-68 Project: mod_cluster Issue Type: Feature Request Affects Versions: 1.0.0.CR1 Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 1.0.0.CR2 Currently, JMX interface allows enabling/disabling *all* webapps on an AS node, but not individual webapps. Allowing webapp granularity allows session draining prior to undeploy of an individual webapp. e.g. enable(String host, String contextPath) disable(String host, String contextPath) -- 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, 8 months

2
3
0 / 0

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

by Brian Stansberry (JIRA)

Handle multiple versions of the same webapp ------------------------------------------- Key: MODCLUSTER-71 URL: https://jira.jboss.org/jira/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 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, 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 2009