-
1. Re: modcluster + JBoss AS 7.1.1 cannot detect nodes
pferraro Mar 22, 2012 11:37 AM (in response to keiji13)Is httpd configured to use mod_advertise? I will need more details (e.g. relevant bit from your configuration) in order to diagnose the problem.
-
2. Re: modcluster + JBoss AS 7.1.1 cannot detect nodes
keiji13 Mar 22, 2012 9:31 PM (in response to pferraro)I'm using the same configurations that I have when I was still using jboss 7.1.0. The only difference is that the nodes using JBoss 7.1.0 can be detected, whereas the nodes using 7.1.1 cannot.
When i try putting a proxy-list inside the modcluster subsystem, the node can be detected but is undefined. And when I start the second machine, I get this error and then the node is removed:
[Server:server-three] 09:24:28,815 ERROR [org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Error [MEM: MEM: Can't read node: {4}] sending command STATUS to proxy 10.128.50.149/10.128.50.149:10001, configuration will be reset
I have this configuration inside my httpd.conf:
ManagerBalancerName other-server-group
KeepAliveTimeout 60 MaxKeepAliveRequests 0 AdvertiseFrequency 5 EnableMCPMReceive AllowDisplay On -
3. Re: modcluster + JBoss AS 7.1.1 cannot detect nodes
ranga033 Mar 29, 2012 8:06 AM (in response to keiji13)Keiji, are you running both the JBoss AS7 server instances in the same machine ? I am also facing a similar problem. Still figuring out how to how to set the node name. I think that might solve the problem.
-
4. Re: modcluster + JBoss AS 7.1.1 cannot detect nodes
ranga033 Mar 29, 2012 8:20 AM (in response to ranga033)Update : adding instance-id="${jboss.node.name}" to <subsystem xmlns="urn:jboss:domain:web:1.1... solves this issue.
Personally I feel this could be a JBoss issue, but it does work when you add the above.
More about this in - https://community.jboss.org/message/727174 -
5. Re: modcluster + JBoss AS 7.1.1 cannot detect nodes
rhusar Mar 29, 2012 8:22 AM (in response to ranga033)Yes, this is a known issue, see : https://issues.jboss.org/browse/JBPAPP-8451