4 Replies Latest reply on Oct 13, 2003 7:52 AM by kbk

    Using jboss ahead of time very slow

    kbk

      Hi,

      env:
      RH7.3/WIN2000
      JBossWeb 3.0.7
      Struts
      JWS

      we are just about to go-live and one of our requirements in the acceptance test is to turn back time on the server to some date last year, and see what happens. Under normal circumstances everything runs smoothly and fast but funny things happens duing this exercise. Suddenly things start to get extremely slow. I haven't been able to pin-point what excatly get's slow (JBoss/Jetty/Struts).
      Actually I don't think it is JBoss-core because the java-clients (using jws) don't seem to be affected by this time-roll-back but sure enough the web pages do :-(
      Under normal conditions the web pages come alive in 2-3 seconds (first run). With time rolled back we're talking 40-50 secs.(first run). Second time the page gets activated:
      normal: immediately
      time rolled back: 40-50 secs. !!!
      Anybody experience this?? Is there a switch in JBossWeb (or maybe java..) where I can turn off this time-check?

        • 1. Re: Using jboss ahead of time very slow

          It's called JSP compilation. Precompile your pages.

          -- Juha

          • 2. Re: Using jboss ahead of time very slow
            kbk

            Are you saying that the JSP precompilation performed by the servlet-engine get's lost and I need to manually precompile my pages when the time has been set back compared to the ear's timestamp.
            whereas in normal cases this is not nessesary.??
            Doesn't make much sence do you think?

            • 3. Re: Using jboss ahead of time very slow
              raja05

              When u change the time, the lastmodified time will be different and the JSP Compiler thinks that the file has changed(due to timestamp difference) and recompiles it. I Think thats what Juha meant.

              -Raj

              • 4. Re: Using jboss ahead of time very slow
                kbk

                Ok now I see what you mean. But how to avoid that?. Would the JSP compiler not touch the generated files if they are pre-compiled, whereas it would if the JSP compiler should compile them?. Seen from the JSP compiler point of view there should be no difference??