3 Replies Latest reply on Apr 27, 2009 1:39 PM by Sami Kallio

    Localhost slow after upgrade to Seam 2.1.0.CR1

    Karl Larsson Newbie

      Hi!


      I have a problem with Localhost after I upgraded to Seam 2.1.0.CR1. The performance running my application with localhost is really bad. It takes up top a 30s to load a page. As I said, this occured after the upgrade but my co-worker do not have this problem and the application is running perfectly or even better then before on our customer web server. I have been trying for 2 days to improve my situatuion without any luck. I have tried to change JBoss server, Java jdk and experimenting with JBoss run.bat file. I have also compared my enviroment and settings with my co-worker and copied his server instance without success.


      The point is that this problem may not be tied to the upgrade even if the timing is perfect. Is there anyone that might have a solution to my problem or maybe experinceing the same problem as I am. The log file isn't really telling me anything but it seems that every request made to the webserver have to wait for as couple of seconds before the request gets through since Waiting for localhost... is shown 90% of the total processing time.


      Is there anyone that can give me any pointers on have to solve this problem?


      My current setup:


      Windows XP
      JBoss 4.2.2.GA (tried with 4.2.3.GA)
      JDK 1.5 (tried with 1.6)
      Netbeans 6.1
      Seam 2.1.0.CR1


      Best regards,
      Kalle

        • 1. Re: Localhost slow after upgrade to Seam 2.1.0.CR1
          Sheldon s Newbie

          have you found out why? I have very similar config as yours: XP/JBoss 4.2.2/JDK5/Seam 2.1.1GA, localhost much slower than using Seam 2.0.1.

          • 2. Re: Localhost slow after upgrade to Seam 2.1.0.CR1
            Ingo Jobling Master

            Try disabling Seam debug in components.xml


            <core:init debug="false" ... >


            • 3. Re: Localhost slow after upgrade to Seam 2.1.0.CR1
              Sami Kallio Newbie

              I migrated our portal application from Seam 2.0 to Seam 2.1 and the performance seems much worse than before, although it was already bad with Seam 2.0.


              My performance test walks through some of the application pages 50 times each. There is nothing special, just short lists of less than 10 elements and single element information pages.


              With Seam 2.0 the average response is 140ms, with Seam 2.1 1500ms, ie. ten times more.


              After disabling Seam debug, I am able to get 1000ms responses.


              It seems that Seam 2.1 is slower all over the application not depending what the page is actually doing, for example, the signout is 8 times slower with Seam 2.1. The application is the same in both cases, except for the api changes and security rules cause by Seam 2.1 migration. There are the following version differences:


              Seam 2.0 and JBoss Portal 2.6.6.GA


                <properties>
                  <seam>2.0.2.SP1</seam>
                  <seam.version>2.0.2.SP1</seam.version>
                  <portletbridge.version>1.0.0.B4</portletbridge.version>
                  <jsf.version>1.2_07</jsf.version>
                  <richfaces.version>3.2.2.GA</richfaces.version>
                </properties>




              Seam 2.1 and JBoss Portal 2.7.2


                <properties>
                  <seam.version>2.1.1.GA</seam.version>
                  <portletbridge.version>1.0.0.CR1</portletbridge.version>
                  <jsf.version>1.2_12</jsf.version>
                  <richfaces.version>3.3.0.GA</richfaces.version>
                </properties>




              Is this to do with Seam version, JBoss portal version, JBoss Portletbridge version or something else? Any ideas? Is there something wrong with my tests? In each case I am running same JMeter test plan against the application deployed to localhost.