8 Replies Latest reply on Jun 5, 2003 4:57 AM by slaboure

    clustering problem

    turkuaz

      My HA-JNDI property string is something like this: java.naming.provier.url=A:1100,B:1100,C:1100

      If A is not working (or the machine not turned on) what will be happen.

        • 1. Re: clustering problem
          slaboure

          if A is not available, it will try B, then C and if no one answers, it will try to discover another server on the same subnet.

          Cheers,


          sacha

          • 2. Re: clustering problem
            turkuaz

            But in my side, if A is not available( amin the server machine power off), it just waiting.However if the machine power on but the application server has not been started yet, then everything is ok.It just try others.
            In cluster-service.xml there is some settings about PING. Something may be wrong about this. I tried to decrease the PING timeout but it did not worked.

            ( also it starts from C not A. If C is not avalibale then it is trying B and C. Is it interesting)

            • 3. Re: clustering problem
              turkuaz

              little Corection:

              ( it starts from C not A. If C is not avalibale then it is trying B and A)

              • 4. Re: clustering problem
                slaboure

                I am not sure I understand. If/when it hangs generate a thread dump and post it.

                • 5. Re: clustering problem
                  volkanyildiz

                  sacha,
                  I noticed that it just waiting too much, it is not locked. After some times ( almost 5 minutes), it switch the second app and everything become normal.There is no genereted thread dump because it just waiting in that time. No action.

                  • 6. Re: clustering problem
                    slaboure

                    even if it is just waiting, there are threads => thread dump. Let's see where it hangs.

                    • 7. Re: clustering problem
                      volkanyildiz

                      It is the last view. It waits just after the succesfull deploy message. When the next server become active, then application start and other messages come.

                      10:35:27,393 INFO [EjbModule] Created
                      10:35:27,399 INFO [EjbModule] Starting
                      10:35:44,243 INFO [EjbModule] Started
                      10:35:44,244 INFO [MainDeployer] Deployed package: file:/usr/local/jboss/jboss-3.0.6/server/all/deploy/ejb-bs4c.jar

                      • 8. Re: clustering problem
                        slaboure

                        ok, so when it waits, press (on Windows) CTRL+BREAK and this will generate a thread dump: we need it.