RE: Compilation of JSP at time of deployment?
JBoss/Tomcat (which I assume you are referring to) has default behaviour whereby the compiled JSPs get deleted on graceful server shutdown. Killing the process hard gets round this issue, or there is a config setting which disables this. You need to edit the tomcat config file ($JBOSS\server\default\deploy\jbossweb-tomcat41.sar\META-INF\jboss-service.x ml) and add: false Between 2000 & With this change you'll only have poor performance the very first time a page is accessed, regardless of reboots etc. Paul > -Original Message- > From: Mike Elliott [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 28, 2004 12:50 AM > To: Struts Users Mailing List > Subject: Compilation of JSP at time of deployment? > > > I have a neglected Ultra 1, now running Solaris 9, which I've rescued > to use as a web application server. It's running JBoss just fine and > when my web application is loaded and run the response time, while > slow (on the order of a second or two per page) is still reasonable. > > The problem comes about after redeploy, or reboot, or JBoss restart, > or whatever, which causes JBoss to forget all the compiled servlets > for the application. When the first user encounters such a page the > page is, of course, compiled and made ready for use -- but this can > take tens of seconds to accomplish, leaving a less than sparkling > impression for the user. > > Is there a way to force all the JSPs and ActionForms, etc., to be > compiled and ready to go at the time of deployment? Even if it takes > several minutes to achieve this, it would be worth it rather than > delaying until the first user/victim accesses the page. > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > ** Axios Email Confidentiality Footer Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message, and notify us immediately. If you or your employer does not consent to Internet email messages of this kind, please advise us immediately. Opinions, conclusions and other information expressed in this message are not given or endorsed by my Company or employer unless otherwise indicated by an authorised representative independent of this message. WARNING: While Axios Systems Ltd takes steps to prevent computer viruses from being transmitted via electronic mail attachments we cannot guarantee that attachments do not contain computer virus code. You are therefore strongly advised to undertake anti virus checks prior to accessing the attachment to this electronic mail. Axios Systems Ltd grants no warranties regarding performance use or quality of any attachment and undertakes no liability for loss or damage howsoever caused. ** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Compilation of JSP at time of deployment?
Look at jspc for pre-compiling your JSPs when building the archive for deployment. -Original Message- From: Mike Elliott [mailto:[EMAIL PROTECTED] Sent: 28 September 2004 00:50 To: Struts Users Mailing List Subject: Compilation of JSP at time of deployment? I have a neglected Ultra 1, now running Solaris 9, which I've rescued to use as a web application server. It's running JBoss just fine and when my web application is loaded and run the response time, while slow (on the order of a second or two per page) is still reasonable. The problem comes about after redeploy, or reboot, or JBoss restart, or whatever, which causes JBoss to forget all the compiled servlets for the application. When the first user encounters such a page the page is, of course, compiled and made ready for use -- but this can take tens of seconds to accomplish, leaving a less than sparkling impression for the user. Is there a way to force all the JSPs and ActionForms, etc., to be compiled and ready to go at the time of deployment? Even if it takes several minutes to achieve this, it would be worth it rather than delaying until the first user/victim accesses the page. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] *** This e-mail and its attachments are confidential and are intended for the above named recipient only. If this has come to you in error, please notify the sender immediately and delete this e-mail from your system. You must take no action based on this, nor must you copy or disclose it or any part of its contents to any person or organisation. Statements and opinions contained in this email may not necessarily represent those of Littlewoods. Please note that e-mail communications may be monitored. The registered office of Littlewoods Limited and its subsidiaries is 100 Old Hall Street, Liverpool, L70 1AB. Registered number of Littlewoods Limited is 262152. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Compilation of JSP at time of deployment?
I'm not completely sure about JBoss-- but for resin, we change everything in the resin.conf file. We add the following directives: - code snippit - /code snippit to the jsp tag in the server conf file. I'd imagine JBoss has similar directives... You probably should be posting this question in a JBoss forum as it is more related to JBoss than it is related to struts. Looks like this question oftentimes gets crossposted... Regards and good luck, -- -=G. Class=- Developer Spam Arrest LLC - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Compilation of JSP at time of deployment?
I have a neglected Ultra 1, now running Solaris 9, which I've rescued to use as a web application server. It's running JBoss just fine and when my web application is loaded and run the response time, while slow (on the order of a second or two per page) is still reasonable. The problem comes about after redeploy, or reboot, or JBoss restart, or whatever, which causes JBoss to forget all the compiled servlets for the application. When the first user encounters such a page the page is, of course, compiled and made ready for use -- but this can take tens of seconds to accomplish, leaving a less than sparkling impression for the user. Is there a way to force all the JSPs and ActionForms, etc., to be compiled and ready to go at the time of deployment? Even if it takes several minutes to achieve this, it would be worth it rather than delaying until the first user/victim accesses the page. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
