JSP Deployment Issues

Question

Guys:
          I saw your names posted in the weblogic jsp news group. I thought you
          might be able to help me with a jsp deployment problem. A number of our
          jsps take a long time to compile. As a result, the first user who
          accesses our jsps after deployment pays a significant latency penalty.
          To get around this problem, we manually "touch" each jsp as part of
          deployment. That way when users access the site, they get reasonalble
          response time.
          The problem we face is that we are now in a clustered environment in
          production and staging. As a result, it can take a long time to
          manually "touch" each jsp. There is also a secondary issue. Our
          staging and production environments are hosted by an extenal service
          provider. We are uncomfortable with deploying source code -- e.g., jsps
          -- in these environments.
          Here is what I have done to date:
          I have written a unix script that invokes the weblogic.jspc compiler for
          each jsp. The intent is to pre-compile the JSPs ahead of time. In our
          testing this script we still notice that Weblogic (e.g., 4.5.1) still
          attempts to recompile the jsps on-demand when they are first accessed
          from the browser by the first user after jsp deployment. (This defeats
          the purpose of pre-compiling the jsps.)
          What are we doing wrong and what can we do so that the jsp-s are
          pre-compiled and not re-compiled on demand. Again, at a minimum we want
          to avoid the latency problems associated with the first user. Best case
          scenario, we would like to ship a jar file that contains the compiled
          jsp servlet classes.
          Your recommendations are most appreciated.
          Mark C. Berman
          Javelin Solutions
          [email protected]
          

Answer 1

I've never tried this, but I don't see any reason why it wouldn't
          work... Don't even register the JSPServlet. Build the JSPs (servlets)
          and deploy them like any other servlet. You can register them with a
          .jsp extension or you could give them a different alias altogether.
          The WL JSP compiler (weblogic.jspc) may be used to compile the jsps
          into servlets during the normal build process and there are options
          that may be used to modify the package, install dir, etc.
          Hope that helps.
          Jason
          On Tue, 26 Dec 2000 17:09:25 -0600, mark berman
          <[email protected]> wrote:
          >Guys:
          >
          >I saw your names posted in the weblogic jsp news group. I thought you
          >might be able to help me with a jsp deployment problem. A number of our
          >jsps take a long time to compile. As a result, the first user who
          >accesses our jsps after deployment pays a significant latency penalty.
          >To get around this problem, we manually "touch" each jsp as part of
          >deployment. That way when users access the site, they get reasonalble
          >response time.
          >
          >The problem we face is that we are now in a clustered environment in
          >production and staging. As a result, it can take a long time to
          >manually "touch" each jsp. There is also a secondary issue. Our
          >staging and production environments are hosted by an extenal service
          >provider. We are uncomfortable with deploying source code -- e.g., jsps
          >-- in these environments.
          >
          >Here is what I have done to date:
          >
          >I have written a unix script that invokes the weblogic.jspc compiler for
          >each jsp. The intent is to pre-compile the JSPs ahead of time. In our
          >testing this script we still notice that Weblogic (e.g., 4.5.1) still
          >attempts to recompile the jsps on-demand when they are first accessed
          >from the browser by the first user after jsp deployment. (This defeats
          >the purpose of pre-compiling the jsps.)
          >
          >What are we doing wrong and what can we do so that the jsp-s are
          >pre-compiled and not re-compiled on demand. Again, at a minimum we want
          >to avoid the latency problems associated with the first user. Best case
          >scenario, we would like to ship a jar file that contains the compiled
          >jsp servlet classes.
          >
          >Your recommendations are most appreciated.
          >
          >Mark C. Berman
          >Javelin Solutions
          >[email protected]
          >