|
Home > Archive > WebSphere Application Server > March 2004 > Precompile JSP option doesn't work?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Precompile JSP option doesn't work?
|
|
| Steven Hugg 2004-03-19, 11:35 am |
| Hi all,
Anyone had trouble getting the "Precompile JSP" option to work properly?
When I deploy a WAR, I check it, and it seems to compile all my JSPs. But
then, pages are really sloooow the first time I hit them (and CPU spikes up)
as if its trying to compile them again.
If this option doesn't work -- I'm gonna have to run a spider on my site
everytime I update...
Thanks!
Steve
| |
| Todd Kaplinger 2004-03-19, 11:35 am |
| A quick way to check if they are being recompiled is to check the
following locations.
1) After deployment and precompile is selected, the JSPs are compiled to
<WAR_ROOT>/WEB-INF/classes
2) Runtime compiles (ie browser or batch compilation), are compiled to
<WAS_INSTALL_ROOT>/temp.
I would suggest verifying that the JSPs are being compiled successfully
during precompile.
Steven Hugg wrote:
> Hi all,
>
> Anyone had trouble getting the "Precompile JSP" option to work properly?
> When I deploy a WAR, I check it, and it seems to compile all my JSPs. But
> then, pages are really sloooow the first time I hit them (and CPU spikes up)
> as if its trying to compile them again.
>
> If this option doesn't work -- I'm gonna have to run a spider on my site
> everytime I update...
>
> Thanks!
> Steve
>
>
| |
| shlomo 2004-03-21, 10:33 am |
| You can use:
call "d:\Program Files\WebSphere\AppServer\bin\JspBatchCo
mpiler.bat"
-enterpriseapp.name <Appname> -server.name server1 -node.name LILIAC
-cell.name LILIAC
After deployment. This way the EAR is deployed even if there are
errors in JSP compilation.
Todd Kaplinger <kaplinger@alum.bentley.edu> wrote in message news:<405B153A.4050901@alum.bentley.edu>...[color=darkred]
> A quick way to check if they are being recompiled is to check the
> following locations.
> 1) After deployment and precompile is selected, the JSPs are compiled to
> <WAR_ROOT>/WEB-INF/classes
> 2) Runtime compiles (ie browser or batch compilation), are compiled to
> <WAS_INSTALL_ROOT>/temp.
>
> I would suggest verifying that the JSPs are being compiled successfully
> during precompile.
>
>
> Steven Hugg wrote:
| |
| Steven Hugg 2004-03-29, 11:35 am |
| The weird thing is -- the files are in both places. The JSPs have all been
compiled into WEB-INF/classes. There are also files being compiled at
runtime into WAS_INSTALL_ROOT/temp (they have very recent timestamps).
"Todd Kaplinger" <kaplinger@alum.bentley.edu> wrote in message
news:405B153A.4050901@alum.bentley.edu...
> A quick way to check if they are being recompiled is to check the
> following locations.
> 1) After deployment and precompile is selected, the JSPs are compiled to
> <WAR_ROOT>/WEB-INF/classes
> 2) Runtime compiles (ie browser or batch compilation), are compiled to
> <WAS_INSTALL_ROOT>/temp.
>
> I would suggest verifying that the JSPs are being compiled successfully
> during precompile.
>
| |
| Todd Kaplinger 2004-03-29, 11:35 am |
| Compare the timestamps of JSP class files are in both WEB-INF/classes
and the temp directory if a JSP has been compiled to both directories.
If the JSP has been modified POST installation (precompile option during
app install), the the jsp class file will be put in the temp dir.
Steven Hugg wrote:
> The weird thing is -- the files are in both places. The JSPs have all been
> compiled into WEB-INF/classes. There are also files being compiled at
> runtime into WAS_INSTALL_ROOT/temp (they have very recent timestamps).
>
>
> "Todd Kaplinger" <kaplinger@alum.bentley.edu> wrote in message
> news:405B153A.4050901@alum.bentley.edu...
>
>
>
>
| |
| Steven Hugg 2004-03-29, 11:35 am |
| The timestamps in the WEB-INF/classes directory are the same as the original
JSP files -- expected, I guess.
The timestamps in the temp directory are all post-installation -- I
installed the app a week ago, and I am getting new files added to temp as
recently as today.
"Todd Kaplinger" <kaplinger@alum.bentley.edu> wrote in message
news:40684913.1010909@alum.bentley.edu...
> Compare the timestamps of JSP class files are in both WEB-INF/classes
> and the temp directory if a JSP has been compiled to both directories.
> If the JSP has been modified POST installation (precompile option during
> app install), the the jsp class file will be put in the temp dir.
>
>
> Steven Hugg wrote:
been[color=darkred]
>
| |
| Todd Kaplinger 2004-03-29, 11:35 am |
| If the timestamp is later than the time of application install, the JSP
has been modified. You can compare the timestamp of these JSPs that are
compiled in temp to verify this. WebSphere sets the last mofified
timestamp of the class files equal to the .jsp file so if the file is
more recent, it has to have been modified somehow.
Steven Hugg wrote:
> The timestamps in the WEB-INF/classes directory are the same as the original
> JSP files -- expected, I guess.
>
> The timestamps in the temp directory are all post-installation -- I
> installed the app a week ago, and I am getting new files added to temp as
> recently as today.
>
>
>
> "Todd Kaplinger" <kaplinger@alum.bentley.edu> wrote in message
> news:40684913.1010909@alum.bentley.edu...
>
> been
>
>
>
|
|
|
|
|