6 Replies Latest reply on Aug 4, 2010 3:39 PM by Chris Laprun

    Start up time

    Nic Essling Newbie

      All,

       

      one thing that is really annoying is the long start up time of the portal. It takes me normally 4-5 minutes to start up which is especially frustrating while developing and testing little pieces. Is there a way to boost the speed by e.g. removing unneeded jars/wars/ears?

      Also in a productive environment without having a cluster a 5 minute downtime everytime is not so nice. Any best practices for these two scenarios?

        • 1. Re: Start up time
          Matt Wringe Master

          There are two versions of GateIn, are you running the Tomcat version of the JBoss version?

           

          If you start the server without GateIn, what is the time difference? Is it GateIn which is causing the server to start too slow or is it server itself which is slow to start?

          • 2. Re: Start up time
            Nic Essling Newbie

            I'm running it on JBoss.

             

            Test with gatein.ear: 4m:38s:653ms

            Test without gatein.ear: 1m:6s:89ms

             

            I'm using the default configuration of JBoss AS. Maybe I could remove some other ears in there or switch to another configuration folder?

            • 3. Re: Start up time
              Matt Wringe Master

              You could try and remove the sample portal and the sample extensions, this gives me a slight increase in speed. I am not sure how easily it would be to remove some of the other GateIn services that you may not need.

               

              In terms of making the JBoss AS part start faster, I am sure there are guides out there for removing non-essential services to speed up AS itself.

               

              Maybe we need documentation on how to create a lighter weight setup with some of the default services removed/disabled.

              • 4. Re: Start up time
                Julien Viet Apprentice

                Remove this and you will save some time:


                deploy/admin-console.war
                deploy/cache-invalidation-service.xml
                deploy/http-invoker.sar
                deploy/jms-ra.rar
                deploy/jmx-invoker-service.xml
                deploy/jmx-remoting.sar
                deploy/jsr88-service.xml
                deploy/legacy-invokers-service.xml
                deploy/mail-ra.rar
                deploy/mail-service.xml
                deploy/management
                deploy/messaging
                deploy/monitoring-service.xml
                deploy/quartz-ra.rar
                deploy/schedule-manager-service.xml
                deploy/scheduler-service.xml
                deploy/xnio-provider.jar
                deployers/webbeans.deployer
                deployers/seam.deployer
                deployers/messaging-definitions-jboss-beans.xml
                deployers/xnio.deployer

                • 5. Re: Start up time
                  Nic Essling Newbie

                  Anything within gatein.ear I could leave out?

                   

                  E.g. if I do not want to use gadgets. Can I just remove eXoGadgets.war and eXoGadgetServer.war? But I guess these are tightly interwoven into the whole portal platform so I would have to touch several other config files and potentially break everything.

                  • 6. Re: Start up time
                    Chris Laprun Master

                    If you're not using WSRP, you can also remove:

                    $GATEIN_HOME/wsrp-admin-gui.war

                    $GATEIN_HOME/wsrp-producer.war

                    $GATEIN_HOME/lib/wsrp-common-$WSRP_VERSION.jar

                    $GATEIN_HOME/lib/wsrp-consumer-$WSRP_VERSION.jar

                    $GATEIN_HOME/lib/wsrp-integration-api-$WSRP_VERSION.jar

                    $GATEIN_HOME/lib/wsrp-producer-lib-$WSRP_VERSION.jar

                    $GATEIN_HOME/lib/wsrp-wsrp1-ws-$WSRP_VERSION.jar<

                    $GATEIN_HOME/lib/gatein.portal.component.wsrp-$PORTAL_VERSION.jar

                     

                    where $GATEIN_HOME is the path to gatein.ear and $WSRP_VERSION and $PORTAL_VERSION correspond to component version numbers for your current GateIn install.