14 Replies Latest reply on Jun 9, 2003 8:04 PM by Kevin

    Unable to get clustering to work

    rf360 Newbie

      I have 2 JBoss servers set up and I am trying to get clustering to work with them. I am using the W2K machines and an Oracle database.

      Whenever I attempt to start JBoss I get the following error. This is actually one a several errors I get, but it's the first one that occurs. I'm hoping that fixing it may also fix later ones.

      I am using the 'all' server for this.

      If I try starting the server in default setting everything works fine. I have bought the JBoss Clustering manual, but I can find anything in it that relates to this problem.

      Any help would be greatly appreciated.

      Thanks!
      -Russell

      16:11:06,828 ERROR [FarmMemberService] MBeanException: Exception in MBean operat
      ion 'checkIncompleteDeployments()'
      Cause: Incomplete Deployment listing:
      Packages waiting for a deployer:
      [org.jboss.deployment.DeploymentInfo@2dc53683 { url=file:/C:/jboss-3.2.0_tomcat-
      4.1.24/server/all/deploy/jbossha-httpsession.sar/ClusteredHttpSessionEB.jar/ }
      deployer: null
      status: Starting
      state: INIT_WAITING_DEPLOYER
      watch: file:/C:/jboss-3.2.0_tomcat-4.1.24/server/all/deploy/jbossha-httpsessio
      n.sar/ClusteredHttpSessionEB.jar/
      lastDeployed: 1050523859421
      lastModified: 1050415091000
      mbeans:
      , org.jboss.deployment.DeploymentInfo@6d27d9c0 { url=file:/C:/jboss-3.2.0_tomcat
      -4.1.24/server/all/farm/JBossTest.jar }
      deployer: null
      status: null
      state: INIT_WAITING_DEPLOYER
      watch: file:/C:/jboss-3.2.0_tomcat-4.1.24/server/all/farm/JBossTest.jar
      lastDeployed: 1050523866796
      lastModified: 1050523866781
      mbeans:
      ]Incompletely deployed packages:
      [org.jboss.deployment.DeploymentInfo@6d27d9c0 { url=file:/C:/jboss-3.2.0_tomcat-
      4.1.24/server/all/farm/JBossTest.jar }
      deployer: null
      status: null
      state: INIT_WAITING_DEPLOYER
      watch: file:/C:/jboss-3.2.0_tomcat-4.1.24/server/all/farm/JBossTest.jar
      lastDeployed: 1050523866796
      lastModified: 1050523866781
      mbeans:
      ]MBeans waiting for classes:

      MBeans waiting for other MBeans:
      [ObjectName: jboss.ejb:service=EJBDeployer
      state: CONFIGURED
      I Depend On: jboss:service=TransactionManager
      jboss:service=WebService

      Depends On Me: , ObjectName: jboss:service=invoker,type=jrmp
      state: CONFIGURED
      I Depend On: jboss:service=TransactionManager

      Depends On Me: jboss.jmx:type=adaptor,name=Invoker,invoker=JRMP
      , ObjectName: jboss:service=invoker,type=local
      state: CONFIGURED
      I Depend On: jboss:service=TransactionManager

      Depends On Me: , ObjectName: jboss:service=invoker,type=pooled
      state: CONFIGURED
      I Depend On: jboss:service=TransactionManager

      Depends On Me: , ObjectName: jboss:service=ClusteredHttpSession
      state: CONFIGURED
      I Depend On: jboss.j2ee:service=EJB,jndiName=clustering/HTTPSession

      Depends On Me: , ObjectName: jboss.mq:service=InvocationLayer,type=HTTP
      state: CONFIGURED
      I Depend On: jboss.mq:service=Invoker
      jboss.web:service=WebServer

      Depends On Me: , ObjectName: jboss.jmx:type=adaptor,name=Invoker,invoker=JRMP
      state: CONFIGURED
      I Depend On: jboss:service=invoker,type=jrmp

      Depends On Me: , ObjectName: jboss.jca:service=LocalTxCM,name=DefaultDS
      state: CONFIGURED
      I Depend On: jboss.jca:service=ManagedConnectionPool,name=DefaultDS
      jboss.jca:service=CachedConnectionManager
      jboss:service=TransactionManager

      Depends On Me: , ObjectName: jboss.mq:service=ServerSessionPoolMBean,name=StdJM
      SPool
      state: CONFIGURED
      I Depend On: jboss:service=XidFactory

      Depends On Me: , ObjectName: jboss.jca:service=TxCM,name=JmsXA
      state: CONFIGURED
      I Depend On: jboss.jca:service=ManagedConnectionPool,name=JmsXA
      jboss.jca:service=CachedConnectionManager
      jboss.security:service=JaasSecurityManager
      jboss:service=TransactionManager

      Depends On Me: , ObjectName: jboss.jca:service=LocalTxCM,name=OracleDS
      state: CONFIGURED
      I Depend On: jboss.jca:service=ManagedConnectionPool,name=OracleDS
      jboss.jca:service=CachedConnectionManager
      jboss:service=TransactionManager

        • 1. Re: Unable to get clustering to work
          rf360 Newbie

          After doing more testing I have found that this problem only occurs when I place my ejb jar file in the farm directory and then start JBoss. If I start JBoss and then place the ejb jar file in the Farm directory it deploys and works properly.

          Is this a bug, or am I not setting something somwehere?

          Thanks!
          -Russell

          • 2. Re: Unable to get clustering to work
            Juha Lindfors Master

            There is something wrong I guess. Can you add a bug report on SF.net please and give detailed information. Thank you. Cheers,


            sacha

            • 3. Re: Unable to get clustering to work
              Paul Newbie

              Has anything been resolved about this issue? I am getting the same results when deploying an ejb to the /farm directory. If I copy an ejb there while the server is running it gets deployed across the cluster properly, but if I restart the node after deployment the ejb is not deployed on startup.

              Also, if my ejb is inside an .ear file it never gets deployed if I copy the .ear file to the /farm directory.

              I have added the true line to each ejb in the jboss.xml

              The ejb deploys correctly if I drop the .ear in the /deploy directory.

              Thanks,
              Paul.

              • 4. Re: Unable to get clustering to work
                Paul Newbie

                Has anything been resolved about this issue? I am getting the same results when deploying an ejb to the /farm directory. If I copy an ejb there while the server is running it gets deployed across the cluster properly, but if I restart the node after deployment the ejb is not deployed on startup.

                Also, if my ejb is inside an .ear file it never gets deployed if I copy the .ear file to the /farm directory.

                I have added the true line to each ejb in the jboss.xml

                The ejb deploys correctly if I drop the .ear in the /deploy directory.

                Thanks,
                Paul.

                • 5. Re: Unable to get clustering to work
                  Paul Newbie

                  Has anything been resolved about this issue? I am getting the same results when deploying an ejb to the /farm directory. If I copy an ejb there while the server is running it gets deployed across the cluster properly, but if I restart the node after deployment the ejb is not deployed on startup.

                  Also, if my ejb is inside an .ear file it never gets deployed if I copy the .ear file to the /farm directory.

                  I have added the true line to each ejb in the jboss.xml

                  The ejb deploys correctly if I drop the .ear in the /deploy directory.

                  Thanks,
                  Paul.

                  • 6. Re: Unable to get clustering to work
                    Paul Newbie

                    Has anything been resolved about this issue? I am getting the same results when deploying an ejb to the /farm directory. If I copy an ejb there while the server is running it gets deployed across the cluster properly, but if I restart the node after deployment the ejb is not deployed on startup.

                    Also, if my ejb is inside an .ear file it never gets deployed if I copy the .ear file to the /farm directory.

                    I have added the true line to each ejb in the jboss.xml

                    The ejb deploys correctly if I drop the .ear in the /deploy directory.

                    Thanks,
                    Paul.

                    • 7. Re: Unable to get clustering to work
                      Paul Newbie

                      PS. The use of these boards would be a lot more intuitive if the threads were updated in realtime. The ability to delete one's accidental duplicate posts would also be nice. :-)

                      • 8. Re: Unable to get clustering to work
                        Darran Lofthouse Master

                        I was looking at SF .net yesterday and it looks as if a bug has now been raised for this to be fixed.

                        • 10. Re: Unable to get clustering to work
                          Kevin Newbie

                          Has this issue been fixed in the latest available build of jboss (3.2.1_?)??

                          • 11. Re: Unable to get clustering to work
                            Kevin Newbie

                            Question on this as well, if I drop the .ear files into each node of a partition in the /all/deploy folder, will that still work? Is this only related to farming in that dropping the .ear file into the /farm dir does not work, but manually dropping it into each nodes /deploy dir does work?

                            • 12. Re: Unable to get clustering to work
                              Sacha Labourey Master

                              /deploy will work

                              the problem with farm is that the farm folder is a service itself. So, depending on what you deploy in it (services or apps), it may be deployed to early/late, that is what is causing all this. I will try to find time to solve this for the app scenario at least. Sorry for the delay.

                              • 13. Re: Unable to get clustering to work
                                Sacha Labourey Master

                                can you check with a fresh Branch_3_2 checkout? I've fixed something.

                                • 14. Re: Unable to get clustering to work
                                  Kevin Newbie

                                  Gees, ask and you shall receive heh? Nice going Sacha! I haven't quite figured out the startup of it all yet. I just got RH 9 installed and java/jboss 3.2.1. I downloaded the 3.2.1 .zip file, but that is dated May 4th. Where do I find this latest one? I am not building the src, so I need the binary.

                                  While we are on the subject, I have read the doco of clustering. I wanted to understand more about how this RMI proxy thing works where by any client making a call to the EJB server has a client/proxy that can load-balance to any node within a partition. Is that all automatically done, or do I have to do something to activate that feature? If it is done automatically, then I take it by simply specifying multiple JNDI servers that it will automatically round-robin (or first available) to the JNDI server?

                                  I am still working on starting JBoss on the redhat 9 server, and windows. It seems easy enough, just reading through the docs again (and again) to get it down. My job is to figure out and learn it well how to cluster jboss and all that is involved, from rmi, session beans, web sessions, etc.

                                  By the way, what is a good setup? I wrote a chapter in a book a while back (based on my Orion clustering experience) and the optimal setup was a 3 node partition, where by each would have 3x memory. This would allow new partitions (or islands as they called it) to be added to scale vertically, as well as would provide the optimum in each partition so that if one server failed, the other two still balanced each other out while the 3rd (dead) one was being fixed. With only two per partition, you run the risk of a full load being handled by one computer should one fail. The idea of 3 is also that you load test it to within 66% of peak load, so that should one fail, the other two can handle the brunt of the 100% load without slowing down too bad. Should more users come online, you add a second partition with 3 more servers. Does that sound pretty good?