RE: OutOfMemory / JMeter / Profiler questions

2005-03-03 Thread Flisch, Alan
You probably have either very large or very many sessions which Tomcat is 
attempting to reload on startup.  Tomcat serialises sessions into files called 
SESSIONS.ser (in the application directories under the work dir) and then when 
it is restarted it attempts to reload them all.  I presume this behaviour can 
be turned off.  

In terms of testing your app, you want to figure out whether you have a memory 
leak issue with your app, or simply that your max heap size is set too low for 
the load you are running.  To check for memory leaks, you could run jmeter 
reasonably (although not too hard) excercising as much of your app as you can, 
repetitively and for an extended period.  If it eventually keels over then you 
may need to investigate memory leaks with a profiler.

Another possibility is that you may not be invalidating sessions and they are 
just being left to expire naturally.  This can use up a lot of memory if you 
aren't careful and I supect is a quite likely source of your problems.

Cheers!


-Original Message-
From: Guillaume Lahitette [mailto:[EMAIL PROTECTED]
Sent: 03 March 2005 09:51
To: tomcat-user@jakarta.apache.org
Subject: OutOfMemory / JMeter / Profiler questions


Hello Tomcat'oids!

We've started performance testing one of our REMOTE web apps using JMeter. 
We're gathering benchmark data before doing further fine
tuning.

Details:
Win2K
only have ssh + cygwin access to this remote server
JDK 1.4.1_03
Tomcat 4.1.26, running as a service:
  a.. Use security manager 1
  b.. Security policy file D:\Tomcat4\conf\catalina.policy
  c.. Initial heap 256
  d.. Max heap 512
  e.. Stack size 256
  f.. JVM server
Issue:
We are getting OutOfMemory errors with very few threads simulated (as low as 
5). More problematic, we've seen the OOM just after a
Tomcat service restart!
>From the stack trace below, you can see we get the OOM before any of our code 
>is executed :(

Questions:
  a.. Anyone has seen this behavior upon Tomcat start up?
  b.. Anything particular to watch for in our JMeter test plan?
  c.. Would a profiler help? Could it profile a remote Tomcat installation? Any 
+/- feedback on Eclipse Profiler plug in
(http://eclipsecolorer.sourceforge.net/index_profiler.html)?
We'll work on gathering more data (e.g. periodic free / allocated memory 
dumps). Untill then, thank you for sharing your
experiences, suggestions, code,...!

Cheers,
Guillaume

javax.servlet.ServletException: Servlet execution threw an exception
 at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
 at 
org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:98)
 at 
org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:176)
 at java.security.AccessController.doPrivileged(Native Method)
 at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:172)
 at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256)
 at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
 at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
 at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
 at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2416)
 at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
 at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
 at 
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
 at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
 at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
 at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
 at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:577)
 at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
 at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
 at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
 at org.apache.catalina.core.ContainerBase.inv

RE: jasper error compiling jsp

2004-10-22 Thread Flisch, Alan



I wouldn't think 
so.  The changes necessary to the app are likely to be pretty trivial, 
although you never know what else might be lurking in there.

  -Original Message-From: Sarath PS 
  [mailto:[EMAIL PROTECTED]Sent: 22 October 2004 
  11:06To: Tomcat Users ListSubject: Re: jasper error 
  compiling jspThanks alan,    So 
  you say it's not possible to run the app in my current configuration ? (tomcat 
  4, j2sdk1.4.2_03)    regards,Sarath Flisch, 
  Alan wrote: 
  It's not Tomcat that is objecting, its javac, the java compiler.  Perhaps some other version of the compiler was more forgiving at some point.  I think getting the application fixed somehow, is your best option.

-Original Message-
From: Sarath PS [mailto:[EMAIL PROTECTED]]
Sent: 22 October 2004 09:43
To: Tomcat Users List
Subject: Re: jasper error compiling jsp


hi,
Thanks for the replay . But this not an application i develop. I 
just want to deploy it on my tomcat. It seems the app is developed for 
some other container.
Is there any work around to run it on tomcat ?

regards,
Sarath PS
  
Roland Carlsson wrote:

  
Hi!


I'm not sure but I don't think you can import classes from the root-level.

Try to create a package and then
import mypackage.Account;
Or 
import mypackage.*;

Regards
Roland Carlsson



Den 04-10-22 09.03, skrev "Sarath PS" <[EMAIL PROTECTED]>:

 


  hi all ,
  I get an an error  like this.


org.apache.jasper.JasperException: Unable to compile class for JSP

An error occurred at line: -1 in the jsp file: null

Generated servlet error:
   [javac] Compiling 1 source file

/usr/java/tomcat-5.0.25/work/Catalina/localhost/qwe/org/apache/jsp/index_jsp.j
ava:6: '.' expected
import Account;
 ^
1 error


org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.
java:83)

   

  org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:315>
)
 


  org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:406)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:463)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:442)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:430)

   

  org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:511>
)
 

org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:274>
)
 


  org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)


at line 6 of index_jsp.java there is an import statement like this.

import Account;

The class Account is very much there. I tried to put it in WEB-INF/classes,
WEB-INF/lib (after making a jar)

But nothing worked. What must be wrong ?



thanks in advance,

Sar




*
*

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
   

  -
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

 



  
Any opinions expressed in this E-mail may be those of the individual and not necessarily the company. This E-mail and any files transmitted with it are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that you have received this E-mail in error and that any use or copying is strictly prohibited. If you have received this E-mail in error please notify the beCogent postmaster at [EMAIL PROTECTED]
Unless expressly stated, opinions in this email are those of the individual sender and not beCogent Ltd. You must take full responsibility for virus checking this email and any attachments.
Please note that the content of this email or any of its attachments may contain data that falls within the scope of the Data Protection Acts and that you must ensure that any handling or processing of such data by you is fully compliant with the terms and provisions of the Data Protection Act 1984 and 1998.


  
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Any opinions expressed in this E-mail may be those of the individual and not 
necessarily the company. This E-mail and any files transmitted with it are 
confidential and solely for the use of the intended recipient. If you are not the 
intended recipient or the person responsible for delivering to the intended recipient, 
be advised that you have received this E-mail in error and that any use or copying is 
strictly prohibited. If you have received this E-mail in error please notify the 
beCo

RE: jasper error compiling jsp

2004-10-22 Thread Flisch, Alan
It's not Tomcat that is objecting, its javac, the java compiler.  Perhaps some other 
version of the compiler was more forgiving at some point.  I think getting the 
application fixed somehow, is your best option.

-Original Message-
From: Sarath PS [mailto:[EMAIL PROTECTED]
Sent: 22 October 2004 09:43
To: Tomcat Users List
Subject: Re: jasper error compiling jsp


hi,
Thanks for the replay . But this not an application i develop. I 
just want to deploy it on my tomcat. It seems the app is developed for 
some other container.
Is there any work around to run it on tomcat ?

regards,
Sarath PS
  
Roland Carlsson wrote:

>Hi!
>
>
>I'm not sure but I don't think you can import classes from the root-level.
>
>Try to create a package and then
> import mypackage.Account;
>Or 
> import mypackage.*;
>
>Regards
>Roland Carlsson
>
>
>
>Den 04-10-22 09.03, skrev "Sarath PS" <[EMAIL PROTECTED]>:
>
>  
>
>>hi all ,
>>   I get an an error  like this.
>>
>>
>>org.apache.jasper.JasperException: Unable to compile class for JSP
>>
>>An error occurred at line: -1 in the jsp file: null
>>
>>Generated servlet error:
>>[javac] Compiling 1 source file
>>
>>/usr/java/tomcat-5.0.25/work/Catalina/localhost/qwe/org/apache/jsp/index_jsp.j
>>ava:6: '.' expected
>>import Account;
>>  ^
>>1 error
>>
>>
>>org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.
>>java:83)
>>
>>
>>
>org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:315>
>)
>  
>
>>org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:406)
>>org.apache.jasper.compiler.Compiler.compile(Compiler.java:463)
>>org.apache.jasper.compiler.Compiler.compile(Compiler.java:442)
>>org.apache.jasper.compiler.Compiler.compile(Compiler.java:430)
>>
>>
>>
>org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:511>
>)
>  
>
>org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:274>
>)
>  
>
>>org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
>>org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
>>javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
>>
>>
>>at line 6 of index_jsp.java there is an import statement like this.
>>
>>import Account;
>>
>>The class Account is very much there. I tried to put it in WEB-INF/classes,
>>WEB-INF/lib (after making a jar)
>>
>>But nothing worked. What must be wrong ?
>>
>>
>>
>>thanks in advance,
>>
>>Sar
>>
>>
>>
>>
>>*
>>*
>>
>>-
>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>  
>


Any opinions expressed in this E-mail may be those of the individual and not 
necessarily the company. This E-mail and any files transmitted with it are 
confidential and solely for the use of the intended recipient. If you are not the 
intended recipient or the person responsible for delivering to the intended recipient, 
be advised that you have received this E-mail in error and that any use or copying is 
strictly prohibited. If you have received this E-mail in error please notify the 
beCogent postmaster at [EMAIL PROTECTED]
Unless expressly stated, opinions in this email are those of the individual sender and 
not beCogent Ltd. You must take full responsibility for virus checking this email and 
any attachments.
Please note that the content of this email or any of its attachments may contain data 
that falls within the scope of the Data Protection Acts and that you must ensure that 
any handling or processing of such data by you is fully compliant with the terms and 
provisions of the Data Protection Act 1984 and 1998.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: jsp precompiling using staging server

2004-07-20 Thread Flisch, Alan
Apparently this is resolved in Tomcat 5.0.27 - it detects and reloads modified class 
files in the work directory.

cheers!

-Original Message-
From: Robert Krüger [mailto:[EMAIL PROTECTED]
Sent: 19 July 2004 15:25
To: Tomcat Users List
Subject: Re: jsp precompiling using staging server



Alan,

I've noticed too that the algorithm in Jasper, which detects JSP file 
modifications is not terribly robust as far as manual modifications to 
generated files are concerned. What you could do is assemble a small 
test application with steps to reproduce the behaviour and file a bug 
report in bugzilla with your test case and hope that the guy who's in 
charge of the jasper core thinks it's a valid requirement to have manual 
  changes to generated files detected. He has been very helpful and 
responsive with my jasper bug reports, so I can only encourage you to 
try your luck. You can always look at the source yourself and suggest a 
patch, however my impression was that you cannot look at the jasper 
source and expect to understand what's going on in a few minutes but YMMV.

Regards,

Robert


Flisch, Alan wrote:

> Hi,
> 
> Thanks or your suggestion, but I was hoping to avoid having to bounce the context.  
> Also, I have looked at using ANT, but there were a variety of limitations that 
> caused problems.  I found I couldn't specify a fileset but could only compile a 
> whole directory and as I said I was hoping to be able to avoid editing the web.xml 
> file and bouncing the context.
> 
> My current approach (using a staging server and the precompilation directive) works 
> quite well apart from the problem I detailed below.  I am a bit worried that its a 
> showstopper for me.
> 
> Thanks,
> Alan
> 
> 
> 
> -Original Message-
> From: Tim Funk [mailto:[EMAIL PROTECTED]
> Sent: 19 July 2004 14:54
> To: Tomcat Users List
> Subject: Re: jsp precompiling using staging server
> 
> 
> This message contains a ant build.xml snippet to precompile all jsps's into a 
> jar. If you implement this - then all your need to do is replace the jar file 
>   of precompiled JSP's (1 file) and reload the server.
> 
> http://marc.theaimsgroup.com/?l=tomcat-user&m=108999588415291&w=2
> 
> 
> -Tim
> 
> Flisch, Alan wrote:
> 
>>I hope you can help me with this...
>>
>>I am trying to devise a precompiling procedure to reduce load on our production 
>>servers.  I am precompiling the jsps on a staging server and then copying over the 
>>.jsp files to the appropriate webapp directory and the .java and .class files to the 
>>work directory.  It works great the first time (it spots the new JSP and notices a 
>>newer compiled version in the work directory and loads that without any 
>>compilation), but it does not work when I am trying to copy over new versions of 
>>existing JSPs - it continues to serve the old one even though the .jsp file is new 
>>and the .class and .jsp files are new.  I'm not sure what it does - it seems that it 
>>must be comparing the modified time of the .jsp file with that of the .class file 
>>and if the class file is newer it does nothing even if they are both newer than the 
>>loaded class file.
>>
>>Does anybody have any idea how I can prompt it to load the new class in the work 
>>directory to replace the existing one - is this even possible?
>>
>>Any help would be much appreciated.
>>
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 
> 
> 
> Any opinions expressed in this E-mail may be those of the individual and not 
> necessarily the company. This E-mail and any files transmitted with it are 
> confidential and solely for the use of the intended recipient. If you are not the 
> intended recipient or the person responsible for delivering to the intended 
> recipient, be advised that you have received this E-mail in error and that any use 
> or copying is strictly prohibited. If you have received this E-mail in error please 
> notify the beCogent postmaster at [EMAIL PROTECTED]
> Unless expressly stated, opinions in this email are those of the individual sender 
> and not beCogent Ltd. You must take full responsibility for virus checking this 
> email and any attachments.
> Please note that the content of this email or any of its attachments may contain 
> data that falls within the scope of the Data Protection Acts and that you must 
> ensure that any handling or processing of such data by you is fully compliant with 
> the terms and provisions of th

RE: jsp precompiling using staging server

2004-07-19 Thread Flisch, Alan
Hi Robert,

Thanks! I'll do that.
Seems like my approach is not going to work then.  It also seems that precompilation 
of JSPs will always require a context bounce whatever the approach whether its to 
reload the contents of the work directory or reload the web.xml file and corresponding 
servlets.

Regards,
Alan

-Original Message-
From: Robert Krüger [mailto:[EMAIL PROTECTED]
Sent: 19 July 2004 15:25
To: Tomcat Users List
Subject: Re: jsp precompiling using staging server



Alan,

I've noticed too that the algorithm in Jasper, which detects JSP file 
modifications is not terribly robust as far as manual modifications to 
generated files are concerned. What you could do is assemble a small 
test application with steps to reproduce the behaviour and file a bug 
report in bugzilla with your test case and hope that the guy who's in 
charge of the jasper core thinks it's a valid requirement to have manual 
  changes to generated files detected. He has been very helpful and 
responsive with my jasper bug reports, so I can only encourage you to 
try your luck. You can always look at the source yourself and suggest a 
patch, however my impression was that you cannot look at the jasper 
source and expect to understand what's going on in a few minutes but YMMV.

Regards,

Robert


Flisch, Alan wrote:

> Hi,
> 
> Thanks or your suggestion, but I was hoping to avoid having to bounce the context.  
> Also, I have looked at using ANT, but there were a variety of limitations that 
> caused problems.  I found I couldn't specify a fileset but could only compile a 
> whole directory and as I said I was hoping to be able to avoid editing the web.xml 
> file and bouncing the context.
> 
> My current approach (using a staging server and the precompilation directive) works 
> quite well apart from the problem I detailed below.  I am a bit worried that its a 
> showstopper for me.
> 
> Thanks,
> Alan
> 
> 
> 
> -Original Message-
> From: Tim Funk [mailto:[EMAIL PROTECTED]
> Sent: 19 July 2004 14:54
> To: Tomcat Users List
> Subject: Re: jsp precompiling using staging server
> 
> 
> This message contains a ant build.xml snippet to precompile all jsps's into a 
> jar. If you implement this - then all your need to do is replace the jar file 
>   of precompiled JSP's (1 file) and reload the server.
> 
> http://marc.theaimsgroup.com/?l=tomcat-user&m=108999588415291&w=2
> 
> 
> -Tim
> 
> Flisch, Alan wrote:
> 
>>I hope you can help me with this...
>>
>>I am trying to devise a precompiling procedure to reduce load on our production 
>>servers.  I am precompiling the jsps on a staging server and then copying over the 
>>.jsp files to the appropriate webapp directory and the .java and .class files to the 
>>work directory.  It works great the first time (it spots the new JSP and notices a 
>>newer compiled version in the work directory and loads that without any 
>>compilation), but it does not work when I am trying to copy over new versions of 
>>existing JSPs - it continues to serve the old one even though the .jsp file is new 
>>and the .class and .jsp files are new.  I'm not sure what it does - it seems that it 
>>must be comparing the modified time of the .jsp file with that of the .class file 
>>and if the class file is newer it does nothing even if they are both newer than the 
>>loaded class file.
>>
>>Does anybody have any idea how I can prompt it to load the new class in the work 
>>directory to replace the existing one - is this even possible?
>>
>>Any help would be much appreciated.
>>
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 
> 
> 
> Any opinions expressed in this E-mail may be those of the individual and not 
> necessarily the company. This E-mail and any files transmitted with it are 
> confidential and solely for the use of the intended recipient. If you are not the 
> intended recipient or the person responsible for delivering to the intended 
> recipient, be advised that you have received this E-mail in error and that any use 
> or copying is strictly prohibited. If you have received this E-mail in error please 
> notify the beCogent postmaster at [EMAIL PROTECTED]
> Unless expressly stated, opinions in this email are those of the individual sender 
> and not beCogent Ltd. You must take full responsibility for virus checking this 
> email and any 

RE: jsp precompiling using staging server

2004-07-19 Thread Flisch, Alan
Hi,

Thanks or your suggestion, but I was hoping to avoid having to bounce the context.  
Also, I have looked at using ANT, but there were a variety of limitations that caused 
problems.  I found I couldn't specify a fileset but could only compile a whole 
directory and as I said I was hoping to be able to avoid editing the web.xml file and 
bouncing the context.

My current approach (using a staging server and the precompilation directive) works 
quite well apart from the problem I detailed below.  I am a bit worried that its a 
showstopper for me.

Thanks,
Alan



-Original Message-
From: Tim Funk [mailto:[EMAIL PROTECTED]
Sent: 19 July 2004 14:54
To: Tomcat Users List
Subject: Re: jsp precompiling using staging server


This message contains a ant build.xml snippet to precompile all jsps's into a 
jar. If you implement this - then all your need to do is replace the jar file 
  of precompiled JSP's (1 file) and reload the server.

http://marc.theaimsgroup.com/?l=tomcat-user&m=108999588415291&w=2


-Tim

Flisch, Alan wrote:
> I hope you can help me with this...
> 
> I am trying to devise a precompiling procedure to reduce load on our production 
> servers.  I am precompiling the jsps on a staging server and then copying over the 
> .jsp files to the appropriate webapp directory and the .java and .class files to the 
> work directory.  It works great the first time (it spots the new JSP and notices a 
> newer compiled version in the work directory and loads that without any 
> compilation), but it does not work when I am trying to copy over new versions of 
> existing JSPs - it continues to serve the old one even though the .jsp file is new 
> and the .class and .jsp files are new.  I'm not sure what it does - it seems that it 
> must be comparing the modified time of the .jsp file with that of the .class file 
> and if the class file is newer it does nothing even if they are both newer than the 
> loaded class file.
> 
> Does anybody have any idea how I can prompt it to load the new class in the work 
> directory to replace the existing one - is this even possible?
> 
> Any help would be much appreciated.
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Any opinions expressed in this E-mail may be those of the individual and not 
necessarily the company. This E-mail and any files transmitted with it are 
confidential and solely for the use of the intended recipient. If you are not the 
intended recipient or the person responsible for delivering to the intended recipient, 
be advised that you have received this E-mail in error and that any use or copying is 
strictly prohibited. If you have received this E-mail in error please notify the 
beCogent postmaster at [EMAIL PROTECTED]
Unless expressly stated, opinions in this email are those of the individual sender and 
not beCogent Ltd. You must take full responsibility for virus checking this email and 
any attachments.
Please note that the content of this email or any of its attachments may contain data 
that falls within the scope of the Data Protection Acts and that you must ensure that 
any handling or processing of such data by you is fully compliant with the terms and 
provisions of the Data Protection Act 1984 and 1998.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

jsp precompiling using staging server

2004-07-19 Thread Flisch, Alan
I hope you can help me with this...

I am trying to devise a precompiling procedure to reduce load on our production 
servers.  I am precompiling the jsps on a staging server and then copying over the 
.jsp files to the appropriate webapp directory and the .java and .class files to the 
work directory.  It works great the first time (it spots the new JSP and notices a 
newer compiled version in the work directory and loads that without any compilation), 
but it does not work when I am trying to copy over new versions of existing JSPs - it 
continues to serve the old one even though the .jsp file is new and the .class and 
.jsp files are new.  I'm not sure what it does - it seems that it must be comparing 
the modified time of the .jsp file with that of the .class file and if the class file 
is newer it does nothing even if they are both newer than the loaded class file.

Does anybody have any idea how I can prompt it to load the new class in the work 
directory to replace the existing one - is this even possible?

Any help would be much appreciated.
Any opinions expressed in this E-mail may be those of the individual and not 
necessarily the company. This E-mail and any files transmitted with it are 
confidential and solely for the use of the intended recipient. If you are not the 
intended recipient or the person responsible for delivering to the intended recipient, 
be advised that you have received this E-mail in error and that any use or copying is 
strictly prohibited. If you have received this E-mail in error please notify the 
beCogent postmaster at [EMAIL PROTECTED]
Unless expressly stated, opinions in this email are those of the individual sender and 
not beCogent Ltd. You must take full responsibility for virus checking this email and 
any attachments.
Please note that the content of this email or any of its attachments may contain data 
that falls within the scope of the Data Protection Acts and that you must ensure that 
any handling or processing of such data by you is fully compliant with the terms and 
provisions of the Data Protection Act 1984 and 1998.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

includes with JspC

2004-07-15 Thread Flisch, Alan
Does anybody know if there is a way to specify includes and excludes for 
org.apache.jasper.JspC as an Ant task as below.



  
  
  
  
  
  
  
  
  
   
  

  

Cheers,
Alan
Any opinions expressed in this E-mail may be those of the individual and not 
necessarily the company. This E-mail and any files transmitted with it are 
confidential and solely for the use of the intended recipient. If you are not the 
intended recipient or the person responsible for delivering to the intended recipient, 
be advised that you have received this E-mail in error and that any use or copying is 
strictly prohibited. If you have received this E-mail in error please notify the 
beCogent postmaster at [EMAIL PROTECTED]
Unless expressly stated, opinions in this email are those of the individual sender and 
not beCogent Ltd. You must take full responsibility for virus checking this email and 
any attachments.
Please note that the content of this email or any of its attachments may contain data 
that falls within the scope of the Data Protection Acts and that you must ensure that 
any handling or processing of such data by you is fully compliant with the terms and 
provisions of the Data Protection Act 1984 and 1998.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]