mod_advertise: Invalid ServerAdvertise Address too often
--------------------------------------------------------
Key: MODCLUSTER-172
URL: https://jira.jboss.org/browse/MODCLUSTER-172
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.1.0.CR3
Environment: any
Reporter: Jean-Frederic Clere
Assignee: Jean-Frederic Clere
Priority: Minor
Fix For: 1.1.0.Final
The configuration:
<VirtualHost *:6666>
ServerName titi.toto.com
Gives:
[Fri Jun 25 15:22:16 2010] [crit] (22)Invalid argument: mod_advertise: Invalid ServerAdvertise Address titi.toto.com:0
Configuration Failed
but we should be able to guess the port from the VirtualHost...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
CLONE -ManagerBalancerName doesn't work
---------------------------------------
Key: MODCLUSTER-163
URL: https://jira.jboss.org/browse/MODCLUSTER-163
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.0.3.GA, 1.1.0.CR2
Environment: any
Reporter: Jean-Frederic Clere
Assignee: Jean-Frederic Clere
Fix For: 1.0.4.GA, 1.1.0.CR3
mycluster is used whatever value you put in ManagerBalancerName
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Fix class name of MBeanAttributeRatioLoadMetric in MC config
------------------------------------------------------------
Key: MODCLUSTER-174
URL: https://jira.jboss.org/browse/MODCLUSTER-174
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.1.0.CR3
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Fix For: 1.1.0.Final
The MBeanAttributeRatioLoadMetric is erroneously using MBeanAttributeLoadMetric as its class name. Even though this bean is not demanded/used normally, the MC in AS6 still parses its constructor, which has the wrong number of parameters.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Demo servlets throw InstanceNotFoundException against EAP5
----------------------------------------------------------
Key: MODCLUSTER-170
URL: https://jira.jboss.org/browse/MODCLUSTER-170
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.1.0.CR3
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Fix For: 1.1.0.Final
Thanks to MODCLUSTER-161, now running demo in EAP5 causes:
javax.management.InstanceNotFoundException: jboss.web:type=Server is not registered.
So, make sure we handle both cases.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Current have Pause and Active, but where is an immediate stop server requests option
------------------------------------------------------------------------------------
Key: MODCLUSTER-166
URL: https://jira.jboss.org/browse/MODCLUSTER-166
Project: mod_cluster
Issue Type: Feature Request
Affects Versions: 1.0.3.GA
Environment: All
Reporter: Jim Tyrrell
Assignee: Jean-Frederic Clere
Currently it appears that mod_cluster only supports the idea of having a server be active, or one that is not accepting any new connections. Should it not support the idea of immediately getting rid of a node from handling any processing.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Support org.jboss.security.plugins.JaasSecurityDomain for defining SSL configurations
-------------------------------------------------------------------------------------
Key: MODCLUSTER-164
URL: https://jira.jboss.org/browse/MODCLUSTER-164
Project: mod_cluster
Issue Type: Feature Request
Affects Versions: 1.1.0.CR2
Reporter: Ben Schofield
Assignee: 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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
ManagerBalancerName doesn't work
--------------------------------
Key: MODCLUSTER-153
URL: https://jira.jboss.org/jira/browse/MODCLUSTER-153
Project: mod_cluster
Issue Type: Bug
Environment: any
Reporter: Jean-Frederic Clere
Assignee: Jean-Frederic Clere
mycluster is used whatever value you put in ManagerBalancerName
--
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
Update docs to include basic iptables rules to allow mod_cluster multicast traffic
----------------------------------------------------------------------------------
Key: MODCLUSTER-154
URL: https://jira.jboss.org/jira/browse/MODCLUSTER-154
Project: mod_cluster
Issue Type: Task
Affects Versions: 1.1.0.CR1, 1.0.3.GA
Reporter: Samuel Mendenhall
Assignee: Jean-Frederic Clere
Priority: Minor
Fix For: 1.0.4.GA, 1.1.0.CR3
By default RHEL/Fedora iptables rules blocks multicast traffic. At least on a single JBoss node with Apache and JBoss on the same machine the following iptables rule allows multicast traffic. If this rule isn't in place http://localhost/mod_cluster-manager will not show any nodes as multicast is blocked and Apache<->JBoss won't communicate
/sbin/iptables -I INPUT 5 -p udp -d 224.0.1.0/24 -j ACCEPT
/etc/init.d/iptables save
It may also be helpful to note the iptables rules when running in a cluster also as seen here: http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5....
--
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