7 Replies Latest reply on Apr 4, 2006 3:54 PM by Mick Knutson

    Help with testing jboss cluster

    Mick Knutson Newbie

      I have 2 QA machines clustered, and I want to test to make sure that if I go to web1 and login, my session login information will get replicated to web2 and will not force me to login again.

      I go to web1i:8090/index.jsp, I login and see this on web1i:

      2006-04-03 14:26:35,940 INFO [com.visionstudio.web.common.Database] DB POOL STATUS: NumActive=0, NumIdle=0
      2006-04-03 14:26:38,352 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheManager] check to see if needs to store and replicate session with id j6fTvP010Eb20H3p8Uj7Pg**
      2006-04-03 14:26:38,352 DEBUG [org.jboss.web.tomcat.tc5.session.ClusteredSession] processSessionRepl(): session is dirty. Will increment version from: 16 and replicate.
      2006-04-03 14:26:38,377 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheService] nodeDirty(): session in-memory data is invalidated with id: j6fTvP010Eb20H3p8Uj7Pg** and verion id: 16
      2006-04-03 14:26:38,378 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheService] nodeDirty(): session in-memory data is invalidated with id: j6fTvP010Eb20H3p8Uj7Pg** and verion id: 17
      2006-04-03 14:27:35,958 INFO [com.visionstudio.web.common.Database] DB POOL STATUS: NumActive=0, NumIdle=1
      2006-04-03 14:28:35,976 INFO [com.visionstudio.web.common.Database] DB POOL STATUS: NumActive=0, NumIdle=0
      


      Then, I go to web2 and try to go to web2/view.jsp, and it forwards me to login.jsp instead.

      Here is what I got:




      
      006-04-03 14:26:38,354 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheService] nodeDirty(): session in-memory data is invalidated with id: j6fTvP010Eb20H3p8Uj7Pg** and verion id: 16
      2006-04-03 14:26:38,354 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheService] nodeDirty(): session in-memory data is invalidated with id: j6fTvP010Eb20H3p8Uj7Pg** and verion id: 16
      2006-04-03 14:26:38,355 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheService] nodeDirty(): session in-memory data is invalidated with id: j6fTvP010Eb20H3p8Uj7Pg** and verion id: 17
      2006-04-03 14:26:38,355 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheService] nodeDirty(): session in-memory data is invalidated with id: j6fTvP010Eb20H3p8Uj7Pg** and verion id: 17
      2006-04-03 14:27:08,877 INFO [com.visionstudio.web.common.Database] DB POOL STATUS: NumActive=0, NumIdle=0
      2006-04-03 14:28:08,894 INFO [com.visionstudio.web.common.Database] DB POOL STATUS: NumActive=0, NumIdle=0
      2006-04-03 14:29:08,914 INFO [com.visionstudio.web.common.Database] DB POOL STATUS: NumActive=0, NumIdle=0
      2006-04-03 14:30:08,931 INFO [com.visionstudio.web.common.Database] DB POOL STATUS: NumActive=0, NumIdle=0
      2006-04-03 14:30:11,142 DEBUG [org.jboss.web.tomcat.tc5.session.ClusteredSession] The session has expired with id: j6fTvP010Eb20H3p8Uj7Pg** is it local? true
      2006-04-03 14:30:11,142 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheManager] Removing session from local store with id: j6fTvP010Eb20H3p8Uj7Pg**
      2006-04-03 14:30:11,142 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheService] Remove session from my own distributed store only. Fqn: /JSESSION//j6fTvP010Eb20H3p8Uj7Pg**
      2006-04-03 14:30:11,144 DEBUG [org.jboss.web.tomcat.tc5.session.ClusteredSession] The session has expired with id: j6fTvP010Eb20H3p8Uj7Pg** is it local? true
      2006-04-03 14:30:11,144 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheManager] Removing session from local store with id: j6fTvP010Eb20H3p8Uj7Pg**
      2006-04-03 14:30:11,144 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheService] Remove session from my own distributed store only. Fqn: /JSESSION//j6fTvP010Eb20H3p8Uj7Pg**
      2006-04-03 14:31:08,948 INFO [com.visionstudio.web.common.Database] DB POOL STATUS: NumActive=0, NumIdle=0
      
      
      
      


        • 2. Re: Help with testing jboss cluster
          Mick Knutson Newbie

          We are actually not using the FORM Jaas authentication. it is a home grown form based authentication. Will that still effect te jira you sent? I think maybe not.

          we have also removed the ./all server, and only run the ./default, will clustering still work if we copy the tc_clustering file and 2 lib's into the correct dir?


          • 3. Re: Help with testing jboss cluster
            Brian Stansberry Master

            I didn't look closely enough at your second set of logs. It looks like your session expired on the 2nd server.

            How long is your session timeout?

            I expect that's not the problem, but should ask. This is more likely the issue:

            http://jira.jboss.com/jira/browse/JBAS-2403.

            If you download 4.0.4.CR2 or 4.0.4.RC1, and your problem goes away, JBAS-2403 is what it was.

            • 4. Re: Help with testing jboss cluster
              Mick Knutson Newbie

              Hmmm. We are 4.0.2 in production, and not sure how easily it will be to upgrade.
              Is this an easy upgrade to the newest version?



              "bstansberry@jboss.com" wrote:
              I didn't look closely enough at your second set of logs. It looks like your session expired on the 2nd server.

              How long is your session timeout?

              I expect that's not the problem, but should ask. This is more likely the issue:

              http://jira.jboss.com/jira/browse/JBAS-2403.

              If you download 4.0.4.CR2 or 4.0.4.RC1, and your problem goes away, JBAS-2403 is what it was.


              • 5. Re: Help with testing jboss cluster
                Mick Knutson Newbie

                I also wanted to make sure I have the cfg files I need as the person before me deleted the ./server/all, and we only have ./server/default:

                ./server/default/lib/jboss-cache.jar
                ./server/default/lib/jgroups.jar


                ./server/default/deploy/tc5-cluster-service.xml

                ./server/default/deploy/jbossweb-tomcat55.sar/server.xml
                ./server/default/deploy/jbossweb-tomcat55.sar/META-INF/jboss-service.xml

                In my WAR:
                --------------
                /WEB-INF/web.xml
                /WEB-INF/jboss-web.xml


                Or is there something I am missing to get Clustering in the default server?

                • 6. Re: Help with testing jboss cluster
                  Brian Stansberry Master

                  If all you want is HttpSession replication, what you listed should be sufficient. If you want any other clustering features, you should start from the all config, which you can get by downloading 4.0.2.

                  Re: upgrading to 4.0.4, first it's only at a release candidate stage; the final release s/b end of the month.

                  Point releases within a major release are meant to be compatible, so upgrading should not be a huge problem. Here are some links to wiki pages that talk about issues:

                  http://wiki.jboss.org/wiki/Wiki.jsp?page=403UpgradeIssues
                  http://wiki.jboss.org/wiki/Wiki.jsp?page=404UpgradeIssues

                  • 7. Re: Help with testing jboss cluster
                    Mick Knutson Newbie

                    Now I seemed to have broken something with modifying the jboss-web.xml and server.xml:

                    12:52:59,391 DEBUG [URLDeploymentScanner] Watch URL for: file:/C:/jboss-4.0.2-looksmart/server/default/deploy/furl.ear -> file:/C:/jboss-4.0.2-looksm
                    rt/server/default/deploy/furl.ear
                    12:52:59,391 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
                    
                    --- Packages waiting for a deployer ---
                    org.jboss.deployment.DeploymentInfo@167b1fdb { url=file:/C:/jboss-4.0.2-looksmart/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/ }
                     deployer: null
                     status: Starting
                     state: INIT_WAITING_DEPLOYER
                     watch: file:/C:/jboss-4.0.2-looksmart/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
                     altDD: null
                     lastDeployed: 1144180352541
                     lastModified: 1139616827493
                     mbeans:
                    
                    org.jboss.deployment.DeploymentInfo@68b27343 { url=file:/C:/jboss-4.0.2-looksmart/server/default/deploy/selenium-0.6.war }
                     deployer: null
                     status: null
                     state: INIT_WAITING_DEPLOYER
                     watch: file:/C:/jboss-4.0.2-looksmart/server/default/deploy/selenium-0.6.war
                     altDD: null
                     lastDeployed: 1144180359888
                     lastModified: 1144180359888
                     mbeans:
                    
                    org.jboss.deployment.DeploymentInfo@bfe96821 { url=file:/C:/jboss-4.0.2-looksmart/server/default/tmp/deploy/tmp37905furl.ear-contents/looksmart-1.5.w
                    r }
                     deployer: null
                     status: Starting
                     state: START_SUBDEPLOYMENTS
                     watch: file:/C:/jboss-4.0.2-looksmart/server/default/tmp/deploy/tmp37905furl.ear-contents/looksmart-1.5.war
                     altDD: null
                     lastDeployed: 1144180378808
                     lastModified: 1144180371114
                     mbeans:
                    
                    org.jboss.deployment.DeploymentInfo@31e7fb0 { url=file:/C:/jboss-4.0.2-looksmart/server/default/tmp/deploy/tmp37905furl.ear-contents/nytimes-1.3.war
                    
                     deployer: null
                     status: Starting
                     state: START_SUBDEPLOYMENTS
                     watch: file:/C:/jboss-4.0.2-looksmart/server/default/tmp/deploy/tmp37905furl.ear-contents/nytimes-1.3.war
                     altDD: null
                     lastDeployed: 1144180379344
                     lastModified: 1144180374440
                     mbeans:
                    
                    --- Incompletely deployed packages ---
                    org.jboss.deployment.DeploymentInfo@abd58bfa { url=file:/C:/jboss-4.0.2-looksmart/server/default/deploy/tc5-cluster-service.xml }
                     deployer: org.jboss.deployment.SARDeployer@1e3cd51
                     status: null
                     state: FAILED
                     watch: file:/C:/jboss-4.0.2-looksmart/server/default/deploy/tc5-cluster-service.xml
                     altDD: null
                     lastDeployed: 1144180355032
                     lastModified: 1144180355017
                     mbeans:
                    
                    org.jboss.deployment.DeploymentInfo@68b27343 { url=file:/C:/jboss-4.0.2-looksmart/server/default/deploy/selenium-0.6.war }
                     deployer: null
                     status: null
                     state: INIT_WAITING_DEPLOYER
                     watch: file:/C:/jboss-4.0.2-looksmart/server/default/deploy/selenium-0.6.war
                     altDD: null
                     lastDeployed: 1144180359888
                     lastModified: 1144180359888
                     mbeans:
                    
                    --- MBeans waiting for other MBeans ---
                    ObjectName: jboss.web:service=WebServer
                     State: CONFIGURED
                     I Depend On:
                     jboss.security:service=JaasSecurityManager
                     jboss.cache:service=TomcatClusteringCache
                     jboss:service=TransactionManager
                     Depends On Me:
                     jboss.mq:service=InvocationLayer,type=HTTP
                    
                    ObjectName: jboss.mq:service=InvocationLayer,type=HTTP
                     State: CONFIGURED
                     I Depend On:
                     jboss.mq:service=Invoker
                     jboss.web:service=WebServer
                    
                    --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
                    ObjectName: jboss.cache:service=TomcatClusteringCache
                     State: NOTYETINSTALLED
                     Depends On Me:
                     jboss.web:service=WebServer
                    
                    
                    12:52:59,485 DEBUG [AbstractDeploymentScanner$ScannerThread] Notified that enabled: true
                    12:52:59,485 DEBUG [URLDeploymentScanner] Started jboss.deployment:flavor=URL,type=DeploymentScanner
                    12:52:59,485 DEBUG [ServiceController] Starting dependent components for: jboss.deployment:flavor=URL,type=DeploymentScanner dependent components: []
                    12:52:59,643 DEBUG [MainDeployer] End deployment start on package: jboss-service.xml
                    12:52:59,643 DEBUG [MainDeployer] Deployed package: file:/C:/jboss-4.0.2-looksmart/server/default/conf/jboss-service.xml
                    12:52:59,643 INFO [Server] JBoss (MX MicroKernel) [4.0.2 (build: CVSTag=JBoss_4_0_2 date=200505022023)] Started in 49s:32ms