Jboss cluster cannot start in win 2003

[sam.gu]

      I setup the cluster envir in jboss as 7. using two servers in one group.and using full-ha profile.

     This method is always worked in windows 2008 r2 server,but now it's cannot start in windows 2003 sp2.and the log is not any error.

I have change the loglevel to debug,but i don't found any problem,who can give me some advice??

the version:   jboss as 7 final 7.1.1

the attach is debug log

[wdfink]

Do you start the same configuration in win2008 and win2003?

Maybe you use the JGroups tests to check whether the multicast will work. There is a wiki how to setup such tests.

[sam.gu]

    Yes,the both of configuration is same complete.

    Coudle you gieve me some advice? or how to get ride of the JGroups tests?

[sam.gu]

      I have tested JGroups using jgroups.jar ,the everything is ok.

      Now , we have found the  reason.the major reason is the modcluster.like blew: the valid config is only the first .other config canot worked.

1 This config is ok,the server of jboss cluster can  be started sucessfully.

            </subsystem>

            <subsystem xmlns="urn:jboss:domain:modcluster:1.0">

                <mod-cluster-config proxy-list="127.0.0.1:6666">

                    <dynamic-load-provider>

                        <load-metric type="busyness"/>

                    </dynamic-load-provider>

                </mod-cluster-config>

            </subsystem>

2 This config cannot work,the server of jboss cluster cannot  be started sucessfully.

    </subsystem>

            <subsystem xmlns="urn:jboss:domain:modcluster:1.0">

                <mod-cluster-config advertise-socket="modcluster"  proxy-list="127.0.0.1:6666">

                    <dynamic-load-provider>

                        <load-metric type="busyness"/>

                    </dynamic-load-provider>

                </mod-cluster-config>

            </subsystem>

3 This config also cannot work,the server of jboss cluster cannot  be started sucessfully.

    </subsystem>

            <subsystem xmlns="urn:jboss:domain:modcluster:1.0">

                <mod-cluster-config >

                    <dynamic-load-provider>

                        <load-metric type="busyness"/>

                    </dynamic-load-provider>

                </mod-cluster-config>

            </subsystem>

[rhusar]

That config will not use advertizing, but will directly register with load-balancer at address 127.0.0.1:6666.

The 2nd config might fail if you do not have the "modcluster" socket binding defined.

The 3rd config will be default use advertizing over UDP multicast but does not have socket binding defined, IIRC will pick the default address/port.

If you are still having problems, can you paste the stack traces?

[sam.gu]

             I have uploaded the debug server.log(the first floor),there is no any related error.

            At the same time,the jconsole and jvisuim cannot connect the java pid when the server cannot start,so i cannot do threaddump.

            i don't know you said  what's stack straces?

[sam.gu]

That config will not use advertizing, but will directly register with load-balancer at address 127.0.0.1:6666.

   if not use advertizing,how to communicate the between httpd and jboss modcluster?

[rhusar]

   if not use advertizing,how to communicate the between httpd and jboss modcluster?

Advertizing is a way for the LB and AS to automatically discover each other using UDP multicast. If you do not want to use that feature, you can setup the LB address from the AS configuration using proxy-list attribute. AS uses HTTP-based mod_cluster management protocol to register with the LB and regularly update load-balancing factor, web application lifecycle information, etc.

You may read on some basic documents or pages, such as http://www.jboss.org/mod_cluster or https://community.jboss.org/wiki/ModClusterDesign