February 2012 - mod_cluster-issues

[JBoss JIRA] Created: (MODCLUSTER-208) ClassCastException on updateClusterStatus()

by Bela Ban (JIRA)

ClassCastException on updateClusterStatus() ------------------------------------------- Key: MODCLUSTER-208 URL: https://issues.jboss.org/browse/MODCLUSTER-208 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.0.Final Environment: JBoss AS 6.0.0.final Reporter: Bela Ban Assignee: Jean-Frederic Clere 13:55:36,731 ERROR [org.apache.catalina.core.ContainerBase] Exception invoking periodic operation: : java.lang.ClassCastException: org.jboss.modcluster.ha.rpc.DefaultRpcResponse cannot be cast to org.jboss.modcluster.ha.rpc.RpcResponse at org.jboss.modcluster.ha.HAModClusterService$ClusteredModClusterService.updateClusterStatus(HAModClusterService.java:1222) [:1.1.0.Final] at org.jboss.modcluster.ha.HAModClusterService$ClusteredModClusterService.status(HAModClusterService.java:1167) [:1.1.0.Final] at org.jboss.modcluster.ha.HAModClusterService.status(HAModClusterService.java:359) [:1.1.0.Final] at org.jboss.modcluster.catalina.CatalinaEventHandlerAdapter.lifecycleEvent(CatalinaEventHandlerAdapter.java:314) [:1.1.0.Final] at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:115) [:6.0.0.Final] at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1335) [:6.0.0.Final] at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1599) [:6.0.0.Final] at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1588) [:6.0.0.Final] at java.lang.Thread.run(Thread.java:662) [:1.6.0_23] -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

4
11
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-227) mod_proxy code for old httpd versions needs to be updated.

by Jean-Frederic Clere (JIRA)

mod_proxy code for old httpd versions needs to be updated. ---------------------------------------------------------- Key: MODCLUSTER-227 URL: https://issues.jboss.org/browse/MODCLUSTER-227 Project: mod_cluster Issue Type: Bug Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere the code is old (pre 2.2.15). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
4
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-248) Missing Documentation For mod_cluster with JBoss AS5

by Stefan Negrea (JIRA)

Missing Documentation For mod_cluster with JBoss AS5 ---------------------------------------------------- Key: MODCLUSTER-248 URL: https://issues.jboss.org/browse/MODCLUSTER-248 Project: mod_cluster Issue Type: Bug Reporter: Stefan Negrea Assignee: Jean-Frederic Clere On the current mod_cluster website there is no documentation on installing mod_cluster on a JBoss AS5 server. The documentation says that mod_cluster is distributed with the server and implies there is no additional configuration required. However, it does not include details like adding Listeners to <Server> tag and configuring the JMX MBean and dependencies. The documentation from the mod_cluster module delivered with the JBoss AS5 points to a website that is no longer valid (http://www.jboss.org/mod_cluster/java/config.html) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
4
0 / 0

[JBoss JIRA] (MODCLUSTER-273) sticky-session-force change requires httpd restart

by Christoph Gostner (Created) (JIRA)

sticky-session-force change requires httpd restart -------------------------------------------------- Key: MODCLUSTER-273 URL: https://issues.jboss.org/browse/MODCLUSTER-273 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.4.Final Reporter: Christoph Gostner Assignee: Jean-Frederic Clere The change of the {{sticky-session-force}} attribute requires a httpd restart. Environment: Apache with {{mod_cluster}} and two JBoss AS7 (standalone mode but with ha configuration). Initial setting: # {{sticky-session=true}} # {{sticky-session-force=false}} Example output: {quote} 27 28520f70 Switch to node c178529b 28 c178529b took 2 seconds 29 c178529b {quote} The documentation for {{sticky-session-force}} says: {quote} Indicates whether the httpd proxy should return an error in the event that the balancer is unable to route a request to the node to which it is stuck. This property is ignored if stickySession is false. {quote} We change {{sticky-session-force}} to {{true}}. Now I expect an 503 error ... But nothing happens... {quote} 5 28520f70 Switch to node c178529b 6 c178529b 7 c178529b {quote} ... after a restart of httpd and JBoss the expected error happens: {quote} 3 28520f70 Failed to open "http://ci.objectbay.com:8000/demo7/". Error code - 503. Broken between 3 and 0 for 0 seconds. Failed to open "http://ci.objectbay.com:8000/demo7/". Error code - 503. Broken between 0 and 0 for 1 seconds. {quote} It seems that the change in the settings requires a complete restart of the cluster environment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
2
0 / 0

[JBoss JIRA] (MODCLUSTER-277) load-demo /heap servlet throws 500 with AS7

by Radoslav Husar (JIRA)

Radoslav Husar created MODCLUSTER-277: ----------------------------------------- Summary: load-demo /heap servlet throws 500 with AS7 Key: MODCLUSTER-277 URL: https://issues.jboss.org/browse/MODCLUSTER-277 Project: mod_cluster Issue Type: Bug Affects Versions: 1.2.0.Beta4 Reporter: Radoslav Husar Assignee: Jean-Frederic Clere Sending load generation request http://localhost:8080/mod_cluster-demo-server-1.2.0.Beta4-SNAPSHOT/heap?d... java.io.IOException: Server returned HTTP response code: 500 for URL: http://localhost:8080/mod_cluster-demo-server-1.2.0.Beta4-SNAPSHOT/heap?d... at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1436) at org.jboss.modcluster.demo.client.ModClusterDemo$8.run(ModClusterDemo.java:871) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
3
0 / 0

[JBoss JIRA] (MODCLUSTER-278) CatalinaConnector.setAddress not working with Tomcat <= 6.0.14

by Stefano Nichele (JIRA)

Stefano Nichele created MODCLUSTER-278: ------------------------------------------ Summary: CatalinaConnector.setAddress not working with Tomcat <= 6.0.14 Key: MODCLUSTER-278 URL: https://issues.jboss.org/browse/MODCLUSTER-278 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.3.Final Environment: Tomcat 6.0.13 + jdk 1.6 Reporter: Stefano Nichele Assignee: Jean-Frederic Clere If in the server.xml file the "address" property is not specified, mod-cluster calls IntrospectionUtils.setProperty(this.connector.getProtocolHandler(), "address", address.getHostAddress()); in order to set the address automatically. This calls doesn't work with tomcat <= 6.0.14 (CatalinaConnector.setAddress throws a NoSuchMethodError) since the signature of IntrospectionUtils.setProperty has been changed in tomcat 6.0.15. As a fix, I would like to suggest this small changes in CatalinaConnector.setAddress: try { IntrospectionUtils.setProperty(this.connector.getProtocolHandler(), "address", address.getHostAddress()); } catch (NoSuchMethodError err) { // this works on Tomcat <= 6.0.14 this.connector.getProtocolHandler().setAttribute("address", address.getHostAddress()); } instead of just: IntrospectionUtils.setProperty(this.connector.getProtocolHandler(), "address", address.getHostAddress()); -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-256) mod_cluster management console/Status does not show exact mod_cluster version

by Radoslav Husar (JIRA)

mod_cluster management console/Status does not show exact mod_cluster version ----------------------------------------------------------------------------- Key: MODCLUSTER-256 URL: https://issues.jboss.org/browse/MODCLUSTER-256 Project: mod_cluster Issue Type: Bug Reporter: Radoslav Husar Assignee: Jean-Frederic Clere It is standard to show the version of the Apache mod, just like mod_jk status page shows. The status page says: {code} mod_cluster/1.1.x Auto Refresh show DUMP output show INFO output ... {code} I think the motivation was to show the MCMP protocol generation/version, however ideally the whole version should be printed out, to make live easier for customers and GSS. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues February 2012