[ https://jira.jboss.org/jira/browse/MODCLUSTER-79?page=com.atlassian.jira.... ] Work on MODCLUSTER-79 started by 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

[ https://jira.jboss.org/jira/browse/MODCLUSTER-79?page=com.atlassian.jira.... ] Jean-Frederic Clere updated MODCLUSTER-79: ------------------------------------------ Fix Version/s: 1.0.1.GA -- 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

[ https://jira.jboss.org/jira/browse/MODCLUSTER-79?page=com.atlassian.jira.... ] Jean-Frederic Clere commented on MODCLUSTER-79: ----------------------------------------------- Ok but that is just writing the same information in a different format. -- 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

[ https://jira.jboss.org/jira/browse/MODCLUSTER-79?page=com.atlassian.jira.... ] Ben Schofield commented on MODCLUSTER-79: ----------------------------------------- True, but the context in which the information is presented becomes more meaningful. Here are the events and train of thought I took when I originally suggested this on the forum. I configured a 2 node cluster behind one balancer using sticky sessions. Hit the web application to create a session and validated I remained on node x. I then disabled the context for the web app on node x anticipating the next request would be routed to node y. The next request returned a blank page. (caused by a seg fault in the apache worker but hadn't notice this yet) My first thought was I must have something configured on the server side incorrectly. I validated these configs and they looked good. Second thought was to understand how the disable function on the mod_cluster-manager page worked in regards to configuring mod_proxy. Maybe disable simply takes the context out of service but the balancer is not suppose to re-route the request to the available node? It was at this point I started looking for something to give more detail on the lower level configuration and posted on the forum. Having the configuration in the mod_proxy/mod_proxy_balancer modules configuration formats would have allowed me to look at the mod_proxy/mod_proxy_balancer documentation and be able to say that yes my http request should have been routed to node y. Fortunately I noticed the seg fault while tailing the apache logs. Otherwise i would still be scratching my head thinking I had something misconfigured in mod_cluster. Personally I don't have the time to contribute code so the best I can do is test and provide feedback. If you feel that the information on mod_cluster-manager page is sufficient then please go ahead and close this issue. -- 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

[ https://jira.jboss.org/jira/browse/MODCLUSTER-79?page=com.atlassian.jira.... ] Jean-Frederic Clere closed MODCLUSTER-79. ----------------------------------------- Resolution: Done Allowing INFO and DUMP brings the same information... -- 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