2 Replies Latest reply on Feb 14, 2006 6:54 AM by jatin4882

    Jboss slow after new release/ depolyment

    jatin4882

      We have jboss 3.2.6 running on our production environment, and the way the project is executed, we launch a new application release every friday. However, the day we do the launch, the website is extremely slow, and pings out for most users (as the load increases), and causes DNS to switch (primarily cause the site text cannot be read).

      However, after 2-3 hours of peak load, the site settles down and jboss starts behaving normally. Could this be a caching issue? or is there something big that i'm missing?

      Any help would be greatly appreciated.

      Thanks,
      Jatin

        • 1. Re: Jboss slow after new release/ depolyment
          acoliver

          If I had to guess I'd bet you use JSP (Java Server Pages) and don't precompile them (very naughty) which means that each page must be compiled first. Without knowing more about the specifics of your application (like what forms of caching it uses and where), I cannot say for sure.

          • 2. Re: Jboss slow after new release/ depolyment
            jatin4882

            Thanks for the input, we are not precompiling our jsp files during our release. What do you think would be the best way to do that? Is there a we can precompile these jsp's without including the compiled class files in our ear. We would prefer that the precompilation occurs when we start our jboss server.

            Thanks for all your help.
            Jatin