Reloadable Hangs
Dear all, I have installed Java is 1.4.1 Tomcat 5.0.28 in Windows 2000 sp1 with 1GB Ram Tomcat is running as a service. Context Reloadable == true When we compile .java into .class, Tomcat will not serve page anymore. We have to restart Tomcat inside Services or from the Monitor Tomcat menu. We have no problen with lower versions of Tomcat. What do i need to reconfigure? Edward - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Reloadable Hangs
Hi, Context Reloadable == true When we compile .java into .class, Tomcat will not serve page anymore. We have to restart Tomcat inside Services or from the Monitor Tomcat menu. We have seen same here. Tomcat = 5.0.28 hangs, there seems to be a ThreadDeath exception sometimes when reload is going on. Environment is Windows XP and JDK 1.4.2. We have no problen with lower versions of Tomcat. I think that 5.0.25 used to work me. Aro S- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Reloadable Hangs
Hello How did you deploy the application ? with a WAR file ? or by installing an unpacked directory ? I read in the Professional Apache Tomcat5 book that the relaod attribute work fine only with an application installed from an unpacked directory not with a WAR file Jean-Claude -Message d'origine- De : edward see [mailto:[EMAIL PROTECTED] Envoyé : vendredi 27 mai 2005 11:32 À : tomcat-user@jakarta.apache.org Objet : Reloadable Hangs Dear all, I have installed Java is 1.4.1 Tomcat 5.0.28 in Windows 2000 sp1 with 1GB Ram Tomcat is running as a service. Context Reloadable == true When we compile .java into .class, Tomcat will not serve page anymore. We have to restart Tomcat inside Services or from the Monitor Tomcat menu. We have no problen with lower versions of Tomcat. What do i need to reconfigure? Edward - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: Reloadable Hangs
Hi, the thread death is caused by log4j. You have to shutdown log4j when the context is destroyed: see http://issues.apache.org/bugzilla/show_bug.cgi?id=26372 for more details. Cheers Bernhard -Ursprüngliche Nachricht- Von: Ari Suutari [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 27. Mai 2005 13:53 An: tomcat-user@jakarta.apache.org Betreff: Re: Reloadable Hangs Hi, Context Reloadable == true When we compile .java into .class, Tomcat will not serve page anymore. We have to restart Tomcat inside Services or from the Monitor Tomcat menu. We have seen same here. Tomcat = 5.0.28 hangs, there seems to be a ThreadDeath exception sometimes when reload is going on. Environment is Windows XP and JDK 1.4.2. We have no problen with lower versions of Tomcat. I think that 5.0.25 used to work me. Aro S- - 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]
RE: Classes are reloaded automatically even when reloadable is not set
Hi, I'm using Tomcat 5.0.28 on Win98. I've created a very simple web app consists of just two java files: Does your webapp have a web.xml? Where are HelloServlet and Biz located? writer.close(); This is an aside, and irrelevant to this thread, but you shouldn't close the writer. Other things (response wrappers, filters) might want to do stuff that depends on the writer. A good rule of thumb is if you didn't create it, don't terminate it: you didn't create or open the writer, so don't close it. Yoav This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Classes are reloaded automatically even when reloadable is not set
From: Shapira, Yoav [EMAIL PROTECTED] Does your webapp have a web.xml? Where are HelloServlet and Biz located? Sorry that I can't seem to reproduce this. Maybe it was indeed marked as reloadable in server.xml but later I deleted the context and created a new one in its own .xml file. This is an aside, and irrelevant to this thread, but you shouldn't close the writer. Other things (response wrappers, filters) might want to do stuff that depends on the writer. A good rule of thumb is if you didn't create it, don't terminate it: you didn't create or open the writer, so don't close it. Thanks for the tip! -- Kent Tong, Msc, MCSE, SCJP, CCSA, Delphi Certified Manager of IT Dept, CPTTM Authorized training for Borland, Cisco, Microsoft, Oracle, RedFlag RedHat - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Classes are reloaded automatically even when reloadable is not set
Hi,
I'm using Tomcat 5.0.28 on Win98. I've created a very
simple web app consists of just two java files:
public class HelloServlet extends HttpServlet {
protected void doGet(
HttpServletRequest request,
HttpServletResponse response)
throws ServletException, IOException {
PrintWriter writer = response.getWriter();
writer.println(Biz.getMsg());
writer.close();
}
}
public class Biz {
public static String getMsg(){
return Hello4!;
}
}
The context is NOT marked as reloadable. But if I change
the string returned by getMsg eg:
public class Biz {
public static String getMsg(){
return Hello5!;
}
}
and then reload the page in a browser, the updated message
is displayed. Any idea why this is happening?
Thanks!
--
Kent Tong, Msc, MCSE, SCJP, CCSA, Delphi Certified
Manager of IT Dept, CPTTM
Authorized training for Borland, Cisco, Microsoft, Oracle, RedFlag RedHat
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Deploy of single class into reloadable context throws LifecycleException with no recovery
Hi Guys, Version: 5.0.28 Scenario: One of our web applications has context reload=true set so that we can deploy single class patches (side question: is there a better way of hot-deploying single-class patching?) However, every time we copy the new class over the existing class, Tomcat begins to reload but throws the following exception stack trace about 6 times in a row (in stdout) and the UI presents error 503 application unavailable on requests. Tomcat never recovers from this and we have to restart the service. INFO: Reloading this Context has started 22-Sep-2004 10:02:25 org.apache.catalina.core.StandardContext reload SEVERE: Cannot find message associated with key standardContext.stoppingContext LifecycleException: Manager has not yet been started at org.apache.catalina.session.StandardManager.stop(StandardManager.java:680) at org.apache.catalina.core.StandardContext.stop(StandardContext.java:4474) at org.apache.catalina.core.StandardContext.reload(StandardContext.java:3015) at org.apache.catalina.core.StandardContext.backgroundProcess(StandardContext.java:4629) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1619) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1628) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1628) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1608) at java.lang.Thread.run(Unknown Source) 22-Sep-2004 10:02:25 org.apache.catalina.core.StandardContext start INFO: Container StandardContext[] has already been started 22-Sep-2004 10:02:36 org.apache.catalina.core.StandardContext reload Kind regards, Allistair. FONT SIZE=1 FACE=VERDANA,ARIAL COLOR=BLUE --- QAS Ltd. Developers of QuickAddress Software a href=http://www.qas.com;www.qas.com/a Registered in England: No 2582055 Registered in Australia: No 082 851 474 --- /FONT - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Deploy of single class into reloadable context throws LifecycleException with no recovery
Hi, One of our web applications has context reload=true set so that we can deploy single class patches (side question: is there a better way of hot- deploying single-class patching?) You could turn off reloadable and instead use the Manager app to reload your webapps. It's not necessarily better, there are pros and cons. Especially for development, your approach is fine. Tomcat never recovers from this and we have to restart the service. INFO: Reloading this Context has started 22-Sep-2004 10:02:25 org.apache.catalina.core.StandardContext reload SEVERE: Cannot find message associated with key standardContext.stoppingContext Hmm, I wonder if the resource is missing. Yup, sure like it. That's probably me being careless ;( Quick workaround: take $CATALINA_HOME/server/lib/catalina.jar, unpack it, edit org/apache/catalina/core/LocalStrings.properties, add a line for standardContext.stoppingContext to the file with whatever message you want, repack jar, put back in $CATALINA_HOME/server/lib, restart server. Let us know if that fixes the problem. Proper solution: I'll open a Bugzilla ticket for this and fix it right away, so that CVS and future Tomcat releases don't have this problem. Sorry about that, and thanks for reporting it. Yoav This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Deploy of single class into reloadable context throws LifecycleException with no recovery
Hi, Bugzilla ticket opened, http://issues.apache.org/bugzilla/show_bug.cgi?id=31364, fixing now ;) Yoav Shapira Millennium Research Informatics -Original Message- From: Shapira, Yoav Sent: Wednesday, September 22, 2004 11:08 AM To: Tomcat Users List Subject: RE: Deploy of single class into reloadable context throws LifecycleException with no recovery Hi, One of our web applications has context reload=true set so that we can deploy single class patches (side question: is there a better way of hot- deploying single-class patching?) You could turn off reloadable and instead use the Manager app to reload your webapps. It's not necessarily better, there are pros and cons. Especially for development, your approach is fine. Tomcat never recovers from this and we have to restart the service. INFO: Reloading this Context has started 22-Sep-2004 10:02:25 org.apache.catalina.core.StandardContext reload SEVERE: Cannot find message associated with key standardContext.stoppingContext Hmm, I wonder if the resource is missing. Yup, sure like it. That's probably me being careless ;( Quick workaround: take $CATALINA_HOME/server/lib/catalina.jar, unpack it, edit org/apache/catalina/core/LocalStrings.properties, add a line for standardContext.stoppingContext to the file with whatever message you want, repack jar, put back in $CATALINA_HOME/server/lib, restart server. Let us know if that fixes the problem. Proper solution: I'll open a Bugzilla ticket for this and fix it right away, so that CVS and future Tomcat releases don't have this problem. Sorry about that, and thanks for reporting it. Yoav This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Deploy of single class into reloadable context throws LifecycleException with no recovery
Hey no problem :) It's interesting that I cannot produce the same problem on my local instance of Tomcat; this was on the production server I was referrring to. The only difference between the two is that the production instance has no JSPs - they are all precompiled, but that's it .. they are both reloadable contexts. I will have a go at your fix on the production server after hours for obvious reasons! Cheers! Allistair -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: 22 September 2004 16:08 To: Tomcat Users List Subject: RE: Deploy of single class into reloadable context throws LifecycleException with no recovery Hi, One of our web applications has context reload=true set so that we can deploy single class patches (side question: is there a better way of hot- deploying single-class patching?) You could turn off reloadable and instead use the Manager app to reload your webapps. It's not necessarily better, there are pros and cons. Especially for development, your approach is fine. Tomcat never recovers from this and we have to restart the service. INFO: Reloading this Context has started 22-Sep-2004 10:02:25 org.apache.catalina.core.StandardContext reload SEVERE: Cannot find message associated with key standardContext.stoppingContext Hmm, I wonder if the resource is missing. Yup, sure like it. That's probably me being careless ;( Quick workaround: take $CATALINA_HOME/server/lib/catalina.jar, unpack it, edit org/apache/catalina/core/LocalStrings.properties, add a line for standardContext.stoppingContext to the file with whatever message you want, repack jar, put back in $CATALINA_HOME/server/lib, restart server. Let us know if that fixes the problem. Proper solution: I'll open a Bugzilla ticket for this and fix it right away, so that CVS and future Tomcat releases don't have this problem. Sorry about that, and thanks for reporting it. Yoav This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] FONT SIZE=1 FACE=VERDANA,ARIAL COLOR=BLUE --- QAS Ltd. Developers of QuickAddress Software a href=http://www.qas.com;www.qas.com/a Registered in England: No 2582055 Registered in Australia: No 082 851 474 --- /FONT - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
default for reloadable setting
Hello, The docs on http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/context.html do not mention the default setting of reloadable. Does anybody know what it is? Greetings, Ronald.
Re: default for reloadable setting
Ronald Klop wrote: The docs on http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/context.html do not mention the default setting of reloadable. Does anybody know what it is? Just try it! :-) IMHO reasonable default setting is false. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: default for reloadable setting
Hi, Ronald Klop wrote: The docs on http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/context.html do not mention the default setting of reloadable. Does anybody know what it is? Just try it! :-) IMHO reasonable default setting is false. The default is false, as you guessed, to avoid production systems overhead. I've updated the document (Context configuration reference page) to specify this information: the change will be visible in the next release. Yoav This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
reloadable
Hi, I've got a web application with reloadable=false. I start tomcat. I call a jsp file ( ex: toto.jsp ). The JSP is compiled in the work directory. I stop tomcat I update the jsp toto.jsp. I start tomcat. What does Tomcat ? Does it recompile the new jsp or does it use the old file in the work directory ? Thanks
RE: reloadable
Howdy, Tomcat will recompile the JSP. Reloadable affects only runtime performance. Yoav Shapira Millennium ChemInformatics -Original Message- From: Laurent Michenaud [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 18, 2003 10:42 AM To: [EMAIL PROTECTED] Subject: reloadable Hi, I've got a web application with reloadable=false. I start tomcat. I call a jsp file ( ex: toto.jsp ). The JSP is compiled in the work directory. I stop tomcat I update the jsp toto.jsp. I start tomcat. What does Tomcat ? Does it recompile the new jsp or does it use the old file in the work directory ? Thanks This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: reloadable
Hi, Would it be fair to say that especially with older versions of tomcat this cannot always be guaranteed to work correctly? I would recommend that if you are having any doubts that you delete the files from your work directory when you redeploy. Andoni. - Original Message - From: Shapira, Yoav [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Tuesday, November 18, 2003 3:43 PM Subject: RE: reloadable Howdy, Tomcat will recompile the JSP. Reloadable affects only runtime performance. Yoav Shapira Millennium ChemInformatics -Original Message- From: Laurent Michenaud [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 18, 2003 10:42 AM To: [EMAIL PROTECTED] Subject: reloadable Hi, I've got a web application with reloadable=false. I start tomcat. I call a jsp file ( ex: toto.jsp ). The JSP is compiled in the work directory. I stop tomcat I update the jsp toto.jsp. I start tomcat. What does Tomcat ? Does it recompile the new jsp or does it use the old file in the work directory ? Thanks This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - 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]
RE: reloadable
Howdy, It would be fair to say that nothing is always guaranteed to work correctly. Yoav Shapira Millennium ChemInformatics -Original Message- From: Andoni [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 18, 2003 11:24 AM To: Tomcat Users List Subject: Re: reloadable Hi, Would it be fair to say that especially with older versions of tomcat this cannot always be guaranteed to work correctly? I would recommend that if you are having any doubts that you delete the files from your work directory when you redeploy. Andoni. - Original Message - From: Shapira, Yoav [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Tuesday, November 18, 2003 3:43 PM Subject: RE: reloadable Howdy, Tomcat will recompile the JSP. Reloadable affects only runtime performance. Yoav Shapira Millennium ChemInformatics -Original Message- From: Laurent Michenaud [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 18, 2003 10:42 AM To: [EMAIL PROTECTED] Subject: reloadable Hi, I've got a web application with reloadable=false. I start tomcat. I call a jsp file ( ex: toto.jsp ). The JSP is compiled in the work directory. I stop tomcat I update the jsp toto.jsp. I start tomcat. What does Tomcat ? Does it recompile the new jsp or does it use the old file in the work directory ? Thanks This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - 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] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Reloadable Servlet?
Doh. 4.1.27. :-) The hotfix is available here: http://jakarta.apache.org/site/binindex.cgi Click on the Tomcat 4.1.27 link. It's hotfix 22096 apparently. Not sure what the bug number is, and I haven't worked out how to use the bugzilla search form properly yet. There was a discussion about it on this list a couple of weeks ago. Dave -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 13, 2003 2:42 PM To: Tomcat Users List Subject: RE: Reloadable Servlet? Howdy, If you're using tomcat 1.4.27 you might have more than just this problem ;) Also, if you're using Tomcat 1.4.27 then there's a bug which stops the reload from working properly. A hotfix is available from the jakarta website. What bug and fix are you referring to? Yoav Shapira Millennium ChemInformatics This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - 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]
RE: Reloadable Servlet?
Howdy, If you're using tomcat 1.4.27 you might have more than just this problem ;) Also, if you're using Tomcat 1.4.27 then there's a bug which stops the reload from working properly. A hotfix is available from the jakarta website. What bug and fix are you referring to? Yoav Shapira Millennium ChemInformatics This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JSP compilation problem with tc-4.1.27 if reloadable=true
Hi, I have just moved from tc-4.1.24 to 27 and have the following problem: In Context .../Context I set reloadable=true. After a Java class file re-compiled and I try to use any JSP pages I always get compilation error messages saying the some classes cannot be found in the classpath. When I restart tomcat everything works fine. I have been using 4.1.24 very long and have never had this problem. Any ideas? Zsolt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Reloadable Servlet?
Ahhh, I just ignored that file. Cool. :) Thanks! The newbie learned something. On Wednesday 13 August 2003 07:57, Shapira, Yoav wrote: Howdy, I see what you mean -- thanks ;) The actual URL for the hotfix is http://www.apache.org/dist/jakarta/tomcat-4/binaries / Yoav Shapira Millennium ChemInformatics -Original Message- From: Johnson, David [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 13, 2003 9:53 AM To: Tomcat Users List Subject: RE: Reloadable Servlet? Doh. 4.1.27. :-) The hotfix is available here: http://jakarta.apache.org/site/binindex.cgi Click on the Tomcat 4.1.27 link. It's hotfix 22096 apparently. Not sure what the bug number is, and I haven't worked out how to use the bugzilla search form properly yet. There was a discussion about it on this list a couple of weeks ago. Dave -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 13, 2003 2:42 PM To: Tomcat Users List Subject: RE: Reloadable Servlet? Howdy, If you're using tomcat 1.4.27 you might have more than just this problem ;) Also, if you're using Tomcat 1.4.27 then there's a bug which stops the reload from working properly. A hotfix is available from the jakarta website. What bug and fix are you referring to? Yoav Shapira Millennium ChemInformatics This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - 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] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- - John Blanco - Code Guru @ Rapture In Venice - http://members.bbnow.net/jblanco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Reloadable Servlet?
This is one heck of a crach course. :) OK, I found my way through the public_html problem...but now I have a question. I want my Servlet to be reloadable. But, when I recompile and make a minor change (changing the printed string), I get the dumb that follows below in my logs and a 503 return error. If I go to TomCat Manager and Stop and then Start (not Reload) my Servlet, everything works again until I recompile and change. My question is...does my Servlet need to explicitly support a reload? 2003-08-12 23:23:27 StandardContext[/HelloWorld]: Reloading this Context has started 2003-08-12 23:23:27 WebappLoader[/HelloWorld]: Reloading checks are enabled for this Context 2003-08-12 23:23:27 StandardWrapper[/HelloWorld:org.apache.catalina.INVOKER.HelloWorld]: Marking servlet org.apache.catalina.INVOKER.HelloWorld as unavailable 2003-08-12 23:23:27 StandardContext[/HelloWorld]: Servlet /HelloWorld threw load() exception javax.servlet.ServletException: Wrapper cannot find servlet class HelloWorld or a class it depends on at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:891) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:823) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3421) at org.apache.catalina.core.StandardContext.reload(StandardContext.java:2568) at org.apache.catalina.loader.WebappLoader$WebappContextNotifier.run(WebappLoader.java:1369) at java.lang.Thread.run(Thread.java:534) - Root Cause - java.lang.ClassNotFoundException: HelloWorld at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1444) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1289) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:885) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:823) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3421) at org.apache.catalina.core.StandardContext.reload(StandardContext.java:2568) at org.apache.catalina.loader.WebappLoader$WebappContextNotifier.run(WebappLoader.java:1369) at java.lang.Thread.run(Thread.java:534) -- - John Blanco - Code Guru @ Rapture In Venice - http://members.bbnow.net/jblanco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Reloadable Servlet?
Howdy, Your servlet doesn't need to explicitly be reloadable but your context does. Set reloadable=true in your context definition. Yoav Shapira Millennium ChemInformatics -Original Message- From: John Blanco [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 13, 2003 1:33 AM To: Tomcat Users List Subject: Reloadable Servlet? This is one heck of a crach course. :) OK, I found my way through the public_html problem...but now I have a question. I want my Servlet to be reloadable. But, when I recompile and make a minor change (changing the printed string), I get the dumb that follows below in my logs and a 503 return error. If I go to TomCat Manager and Stop and then Start (not Reload) my Servlet, everything works again until I recompile and change. My question is...does my Servlet need to explicitly support a reload? 2003-08-12 23:23:27 StandardContext[/HelloWorld]: Reloading this Context has started 2003-08-12 23:23:27 WebappLoader[/HelloWorld]: Reloading checks are enabled for this Context 2003-08-12 23:23:27 StandardWrapper[/HelloWorld:org.apache.catalina.INVOKER.HelloWorld]: Marking servlet org.apache.catalina.INVOKER.HelloWorld as unavailable 2003-08-12 23:23:27 StandardContext[/HelloWorld]: Servlet /HelloWorld threw load() exception javax.servlet.ServletException: Wrapper cannot find servlet class HelloWorld or a class it depends on at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.ja va:8 91) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:823) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext. java :3421) at org.apache.catalina.core.StandardContext.reload(StandardContext.java:25 68) at org.apache.catalina.loader.WebappLoader$WebappContextNotifier.run(Webap pLoa der.java:1369) at java.lang.Thread.run(Thread.java:534) - Root Cause - java.lang.ClassNotFoundException: HelloWorld at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoade r.ja va:1444) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoade r.ja va:1289) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.ja va:8 85) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:823) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext. java :3421) at org.apache.catalina.core.StandardContext.reload(StandardContext.java:25 68) at org.apache.catalina.loader.WebappLoader$WebappContextNotifier.run(Webap pLoa der.java:1369) at java.lang.Thread.run(Thread.java:534) -- - John Blanco - Code Guru @ Rapture In Venice - http://members.bbnow.net/jblanco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Reloadable Servlet?
Also, if you're using Tomcat 1.4.27 then there's a bug which stops the reload from working properly. A hotfix is available from the jakarta website. Dave -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 13, 2003 1:59 PM To: Tomcat Users List Subject: RE: Reloadable Servlet? Howdy, Your servlet doesn't need to explicitly be reloadable but your context does. Set reloadable=true in your context definition. Yoav Shapira Millennium ChemInformatics -Original Message- From: John Blanco [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 13, 2003 1:33 AM To: Tomcat Users List Subject: Reloadable Servlet? This is one heck of a crach course. :) OK, I found my way through the public_html problem...but now I have a question. I want my Servlet to be reloadable. But, when I recompile and make a minor change (changing the printed string), I get the dumb that follows below in my logs and a 503 return error. If I go to TomCat Manager and Stop and then Start (not Reload) my Servlet, everything works again until I recompile and change. My question is...does my Servlet need to explicitly support a reload? 2003-08-12 23:23:27 StandardContext[/HelloWorld]: Reloading this Context has started 2003-08-12 23:23:27 WebappLoader[/HelloWorld]: Reloading checks are enabled for this Context 2003-08-12 23:23:27 StandardWrapper[/HelloWorld:org.apache.catalina.INVOKER.HelloWorld]: Marking servlet org.apache.catalina.INVOKER.HelloWorld as unavailable 2003-08-12 23:23:27 StandardContext[/HelloWorld]: Servlet /HelloWorld threw load() exception javax.servlet.ServletException: Wrapper cannot find servlet class HelloWorld or a class it depends on at org.apache.catalina.core.StandardWrapper.loadServlet(Standard Wrapper.ja va:8 91) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper .java:823) at org.apache.catalina.core.StandardContext.loadOnStartup(Standa rdContext. java :3421) at org.apache.catalina.core.StandardContext.reload(StandardConte xt.java:25 68) at org.apache.catalina.loader.WebappLoader$WebappContextNotifier .run(Webap pLoa der.java:1369) at java.lang.Thread.run(Thread.java:534) - Root Cause - java.lang.ClassNotFoundException: HelloWorld at org.apache.catalina.loader.WebappClassLoader.loadClass(Webapp ClassLoade r.ja va:1444) at org.apache.catalina.loader.WebappClassLoader.loadClass(Webapp ClassLoade r.ja va:1289) at org.apache.catalina.core.StandardWrapper.loadServlet(Standard Wrapper.ja va:8 85) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper .java:823) at org.apache.catalina.core.StandardContext.loadOnStartup(Standa rdContext. java :3421) at org.apache.catalina.core.StandardContext.reload(StandardConte xt.java:25 68) at org.apache.catalina.loader.WebappLoader$WebappContextNotifier .run(Webap pLoa der.java:1369) at java.lang.Thread.run(Thread.java:534) -- - John Blanco - Code Guru @ Rapture In Venice - http://members.bbnow.net/jblanco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - 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]
RE: Reloadable Servlet?
Howdy, I see what you mean -- thanks ;) The actual URL for the hotfix is http://www.apache.org/dist/jakarta/tomcat-4/binaries/ Yoav Shapira Millennium ChemInformatics -Original Message- From: Johnson, David [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 13, 2003 9:53 AM To: Tomcat Users List Subject: RE: Reloadable Servlet? Doh. 4.1.27. :-) The hotfix is available here: http://jakarta.apache.org/site/binindex.cgi Click on the Tomcat 4.1.27 link. It's hotfix 22096 apparently. Not sure what the bug number is, and I haven't worked out how to use the bugzilla search form properly yet. There was a discussion about it on this list a couple of weeks ago. Dave -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 13, 2003 2:42 PM To: Tomcat Users List Subject: RE: Reloadable Servlet? Howdy, If you're using tomcat 1.4.27 you might have more than just this problem ;) Also, if you're using Tomcat 1.4.27 then there's a bug which stops the reload from working properly. A hotfix is available from the jakarta website. What bug and fix are you referring to? Yoav Shapira Millennium ChemInformatics This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - 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] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JSP compilation problem with tc-4.1.27 if reloadable=true
Probably this: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22096 -Tim Zsolt Koppany wrote: Hi, I have just moved from tc-4.1.24 to 27 and have the following problem: In Context .../Context I set reloadable=true. After a Java class file re-compiled and I try to use any JSP pages I always get compilation error messages saying the some classes cannot be found in the classpath. When I restart tomcat everything works fine. I have been using 4.1.24 very long and have never had this problem. Any ideas? Zsolt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Singleton and Reloadable Contexts.
Hello All!
Our team here has written a simple Connection Pool
class that is a singleton.
I've noticed that whenever Tomcat reloads my webapps
context (when I add a new class or something like
that), that it the next call to the Connection Pool
get instance method doesn't see the previous
singleton, and hence, it allocates a bunch of new
connections.
This would be fine, except that the old connections
are never closed (it seems that the Garbage Collector
doesn't eat them up) so I think that the old instance
of the singleton is still floating around in the JVM
somewhere.
This causes all the free sessions on the Database to
be eaten up, forcing a restart of tomcat. Once tomcat
is restarted, all the connections are closed out
(since the JVM terminated, I guess) and things are
fine again.
What do I need to do so that the old connections are
removed? This is on Tomcat 3.3.1a. Here is the
relevent code of the Singleton getInstance method:
public static synchronized ConnectionPool
getInstance(ConnectionPoolConstants c) throws
SQLException {
constants = c;
if (instance == null) {
// Determine which database url to connect
db_url = constants.getTestDBURL();
String line = ;
try {
Vector return_vec =
DelphiRuntime.execCommandWithOut(hostname);
Enumeration return_enum =
return_vec.elements();
while (return_enum.hasMoreElements())
{
line = (String)
return_enum.nextElement();
}
} catch (InterruptedException ire) {
} catch (IOException ioe) {
}
if
(line.equals(constants.getProductionServerHostname()))
{
db_url =
constants.getProductionDBURL();
}
instance = new ConnectionPool();
}
return instance;
}
Thanks for any insights!
Cheers!
__
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Singleton and Reloadable Contexts.
A singleton is only a singleton to the classloader it lives in. A webapp is
loaded in its own classloader, so when it is start/stopped or reloaded - a
new classloader is made. And so is a brand new set of singletons.
The easy workaround is to create a ServletContextListener which listens for
the webapp to be stopped. At that time - your can free the pool.
But I don't recall if ServletContextListener is available in the 2.2 servletapi.
-Tim
Matt E wrote:
Hello All!
Our team here has written a simple Connection Pool
class that is a singleton.
I've noticed that whenever Tomcat reloads my webapps
context (when I add a new class or something like
that), that it the next call to the Connection Pool
get instance method doesn't see the previous
singleton, and hence, it allocates a bunch of new
connections.
This would be fine, except that the old connections
are never closed (it seems that the Garbage Collector
doesn't eat them up) so I think that the old instance
of the singleton is still floating around in the JVM
somewhere.
This causes all the free sessions on the Database to
be eaten up, forcing a restart of tomcat. Once tomcat
is restarted, all the connections are closed out
(since the JVM terminated, I guess) and things are
fine again.
What do I need to do so that the old connections are
removed? This is on Tomcat 3.3.1a. Here is the
relevent code of the Singleton getInstance method:
public static synchronized ConnectionPool
getInstance(ConnectionPoolConstants c) throws
SQLException {
constants = c;
if (instance == null) {
// Determine which database url to connect
db_url = constants.getTestDBURL();
String line = ;
try {
Vector return_vec =
DelphiRuntime.execCommandWithOut(hostname);
Enumeration return_enum =
return_vec.elements();
while (return_enum.hasMoreElements())
{
line = (String)
return_enum.nextElement();
}
} catch (InterruptedException ire) {
} catch (IOException ioe) {
}
if
(line.equals(constants.getProductionServerHostname()))
{
db_url =
constants.getProductionDBURL();
}
instance = new ConnectionPool();
}
return instance;
}
Thanks for any insights!
Cheers!
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Faking ServletContextListener with Tomcat 3.3.1a? [Was: Singleton and Reloadable Contexts.]
After looking through the archives more (why is it
that you always find something after you've asked.) I
found this message:
http://mikal.org/interests/java/tomcat/archive/view?mesg=51529
That's exactly what I want to do. However the server
is running Tomcat 3.3.1a. Short of updating the
server, is there anyway to fake the
contextInitialized() and contextDestoryed() methods in
the Older Tomcat?
Cheers,
Matt G. Ellis
--- Matt E [EMAIL PROTECTED] wrote:
Hello All!
Our team here has written a simple Connection Pool
class that is a singleton.
I've noticed that whenever Tomcat reloads my webapps
context (when I add a new class or something like
that), that it the next call to the Connection Pool
get instance method doesn't see the previous
singleton, and hence, it allocates a bunch of new
connections.
This would be fine, except that the old connections
are never closed (it seems that the Garbage
Collector
doesn't eat them up) so I think that the old
instance
of the singleton is still floating around in the JVM
somewhere.
This causes all the free sessions on the Database to
be eaten up, forcing a restart of tomcat. Once
tomcat
is restarted, all the connections are closed out
(since the JVM terminated, I guess) and things are
fine again.
What do I need to do so that the old connections are
removed? This is on Tomcat 3.3.1a. Here is the
relevent code of the Singleton getInstance method:
public static synchronized ConnectionPool
getInstance(ConnectionPoolConstants c) throws
SQLException {
constants = c;
if (instance == null) {
// Determine which database url to
connect
db_url = constants.getTestDBURL();
String line = ;
try {
Vector return_vec =
DelphiRuntime.execCommandWithOut(hostname);
Enumeration return_enum =
return_vec.elements();
while
(return_enum.hasMoreElements())
{
line = (String)
return_enum.nextElement();
}
} catch (InterruptedException ire) {
} catch (IOException ioe) {
}
if
(line.equals(constants.getProductionServerHostname()))
{
db_url =
constants.getProductionDBURL();
}
instance = new ConnectionPool();
}
return instance;
}
Thanks for any insights!
Cheers!
__
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site
design software
http://sitebuilder.yahoo.com
-
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
__
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
reloadable='true' and MBean
Hi all, I'm using Tomcat 4.1.24 with some virtual users on it. I'd like to give my users the flexibility to change their Context properties on the fly ( like reloadable='false' for instance ), but I don't want to give them access to MBean application. Is it possible ? How can I do a 'wrapper' so I can customize my own application ? Thanks Renato - Brazil. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: reloadable='true' and MBean
Look at Tomcat5 and the JMXProxy servlet in the manager application. http://cvs.apache.org/viewcvs.cgi/jakarta-tomcat-catalina/webapps/manager/WEB-INF/classes/org/apache/catalina/manager/JMXProxyServlet.java?rev=1.4content-type=text/vnd.viewcvs-markup And you can write your own app to allow users to set only the properties you wish as well as any custom security constraints. -Tim webmaster wrote: Hi all, I'm using Tomcat 4.1.24 with some virtual users on it. I'd like to give my users the flexibility to change their Context properties on the fly ( like reloadable='false' for instance ), but I don't want to give them access to MBean application. Is it possible ? How can I do a 'wrapper' so I can customize my own application ? Thanks Renato - Brazil. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Clarification about reloadable=true in tomcat 4.1.16
I think the answer is yes, but do contexts configured in tomcat 4.1.16 default to reloadable=true? If that is the case, will this work for me...? I have a couple hundred vhosts all with a few contexts each. Right now, I don't have any default context configured, but I do have a default host. Can I specify reloadable=false for a default context in the default host and assume that all contexts that don't have any reloadable attributes set to become reloadable=false? Thanks! Brandon -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
reloadable
Hello, I set the attribute reloadable to true in a sample context tag(Context in the sever.xml) to monitor the the WEB-INF/classes. But it didn't affect. I make change in a sample class and the server don't load this class again. I am using jakarta-tomcat-4.0.6 in winow2000 server. Should I have to do other setting to make the reloadable work. Thanks, raja
Re: reloadable
Hi Raja, The default behaviour setting for the class reloading is a touch on the slow side, so include a Loader in the Context that looks like this one: Context path=/myapp docBase=myapp reloadable=true Loader className=org.apache.catalina.loader.WebappLoader loaderClass=org.apache.catalina.loader.WebappClassLoader checkInterval=1 / /Context And you'll find that it will now check every second, rather than the default 15 seconds. Cheers, -- jon Raja Nasrallah wrote: Hello, I set the attribute reloadable to true in a sample context tag(Context in the sever.xml) to monitor the the WEB-INF/classes. But it didn't affect. I make change in a sample class and the server don't load this class again. I am using jakarta-tomcat-4.0.6 in winow2000 server. Should I have to do other setting to make the reloadable work. Thanks, raja -- Jon Eaves [EMAIL PROTECTED] http://www.eaves.org/jon/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: reloadable
Hi, But I can't start Tomcat after I put the following to server.xml, and the error msg can't be logged. Context path=/test docBase=test reloadable=true Loader className=org.apache.catalina.loader.WebappLoader loaderClass=org.apache.catalina.loader.WebappClassLoader checkInterval=1 / /Context James - Original Message - From: Jon Eaves [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Monday, November 25, 2002 8:59 AM Subject: Re: reloadable Hi Raja, The default behaviour setting for the class reloading is a touch on the slow side, so include a Loader in the Context that looks like this one: Context path=/myapp docBase=myapp reloadable=true Loader className=org.apache.catalina.loader.WebappLoader loaderClass=org.apache.catalina.loader.WebappClassLoader checkInterval=1 / /Context And you'll find that it will now check every second, rather than the default 15 seconds. Cheers, -- jon Raja Nasrallah wrote: Hello, I set the attribute reloadable to true in a sample context tag(Context in the sever.xml) to monitor the the WEB-INF/classes. But it didn't affect. I make change in a sample class and the server don't load this class again. I am using jakarta-tomcat-4.0.6 in winow2000 server. Should I have to do other setting to make the reloadable work. Thanks, raja -- Jon Eaves [EMAIL PROTECTED] http://www.eaves.org/jon/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: reloadable [bayes][adr]
Hello, Thanks you, it works raja -Original Message- From: Jon Eaves [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 26, 2002 10:28 PM To: Tomcat Users List Subject: Re: reloadable [bayes][adr] Importance: Low Hi Raja, The default behaviour setting for the class reloading is a touch on the slow side, so include a Loader in the Context that looks like this one: Context path=/myapp docBase=myapp reloadable=true Loader className=org.apache.catalina.loader.WebappLoader loaderClass=org.apache.catalina.loader.WebappClassLoader checkInterval=1 / /Context And you'll find that it will now check every second, rather than the default 15 seconds. Cheers, -- jon Raja Nasrallah wrote: Hello, I set the attribute reloadable to true in a sample context tag(Context in the sever.xml) to monitor the the WEB-INF/classes. But it didn't affect. I make change in a sample class and the server don't load this class again. I am using jakarta-tomcat-4.0.6 in winow2000 server. Should I have to do other setting to make the reloadable work. Thanks, raja -- Jon Eaves [EMAIL PROTECTED] http://www.eaves.org/jon/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: reloadable [bayes][adr]
Hi, Raja: I am using Tomcat 4.1, it doesn't work for me. Did you change anything? Thanks for you help. James - Original Message - From: Raja Nasrallah [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Monday, November 25, 2002 9:32 AM Subject: RE: reloadable [bayes][adr] Hello, Thanks you, it works raja -Original Message- From: Jon Eaves [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 26, 2002 10:28 PM To: Tomcat Users List Subject: Re: reloadable [bayes][adr] Importance: Low Hi Raja, The default behaviour setting for the class reloading is a touch on the slow side, so include a Loader in the Context that looks like this one: Context path=/myapp docBase=myapp reloadable=true Loader className=org.apache.catalina.loader.WebappLoader loaderClass=org.apache.catalina.loader.WebappClassLoader checkInterval=1 / /Context And you'll find that it will now check every second, rather than the default 15 seconds. Cheers, -- jon Raja Nasrallah wrote: Hello, I set the attribute reloadable to true in a sample context tag(Context in the sever.xml) to monitor the the WEB-INF/classes. But it didn't affect. I make change in a sample class and the server don't load this class again. I am using jakarta-tomcat-4.0.6 in winow2000 server. Should I have to do other setting to make the reloadable work. Thanks, raja -- Jon Eaves [EMAIL PROTECTED] http://www.eaves.org/jon/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Negatives to reloadable=true
Are there any downsides/negatives to setting reloadable=true in a context? e.g. Are there security or performance implications? Thank you, Mike -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Negatives to reloadable=true
Hi, Yes. Significant performance implications can be assumed. Don't set reloadable=true in a production server. Yoav Shapira Millennium ChemInformatics -Original Message- From: Mike Millson [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 21, 2002 11:45 AM To: Tomcat Users List Subject: Negatives to reloadable=true Are there any downsides/negatives to setting reloadable=true in a context? e.g. Are there security or performance implications? Thank you, Mike -- To unsubscribe, e-mail: mailto:tomcat-user- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-user- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Cocoon 2.1 + Tomcat 4.1 + reloadable=true
Hi and sorry for the cross-posting, this might interest both lists although I think it may be purely a Tomcat-specific problem. Tomcat 4.1.12 - CATALINA_OPTS allow 128 MB of RAM (out of 512 physical), with catalina run command to see more console log. Cocoon 2.1-dev from CVS. JDK 1.3.1 Windows NT4 SP6 Few other apps running, at least memory is not fully used. Eclipse 2.0.1 to edit and compile java code. reloadable=true for my webapp (other webapps are defined in server.xml and also reloadable but I don't call their URI. Issue : I change some code in a java class, save so that it compiles automaticaly. After a few (3 to 6) compiles/reloads my webapp dies with ClassCastException, IllegalStateException, or Tomcat dies with OutOfMemoryError. When I was using Tomcat 4.0.5 and JBuilder 6 I had few problems with automatic reloads, at least not so many errors... Barbara -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Cocoon 2.1 + Tomcat 4.1 + reloadable=true
I am running Tomcat 3.3 on Win2k, and a recent snapshot of Cocoon from the HEAD of CVS. I am periodically having the same problems whereby Tomcat is running out of memory when either Tomcat or Cocoon are reloading some stuff. Is it possible that some cache collections are not being cleared? Also, given that I'm having a similar problem with Tomcat 3.3, is Cocoon a more plausible suspect? On another note, every once in a while upon auto-reloading some of the updated components either Tomcat or Cocoon hang up, and stop responding to requests. CPU usage spikes at first, but then goes down. Seems like a dead-lock. However, I have saved the full VM thread dump, and cannot see anything unusual there that would indicate a deadlock of any sort. (BTW, If you are interested, I can post the thread dump.) I can see from it that three Tomcat threads are waiting in ServerSocket.accept() calls, but I cannot connect to any of the ports that it is supposed to listen on either with the browser or with telnet. Calling Tomcat's shutdown.bat does nothing to stop the hung up process. Killing Tomcat's Java process is the only thing that helps. Does anyone have any idea on this and the OutOfMemory issues? Sorry for cross-replying, but... what she said. :-) -- Ilya Barbara Post wrote: Hi and sorry for the cross-posting, this might interest both lists although I think it may be purely a Tomcat-specific problem. Tomcat 4.1.12 - CATALINA_OPTS allow 128 MB of RAM (out of 512 physical), with catalina run command to see more console log. Cocoon 2.1-dev from CVS. JDK 1.3.1 Windows NT4 SP6 Few other apps running, at least memory is not fully used. Eclipse 2.0.1 to edit and compile java code. reloadable=true for my webapp (other webapps are defined in server.xml and also reloadable but I don't call their URI. Issue : I change some code in a java class, save so that it compiles automaticaly. After a few (3 to 6) compiles/reloads my webapp dies with ClassCastException, IllegalStateException, or Tomcat dies with OutOfMemoryError. When I was using Tomcat 4.0.5 and JBuilder 6 I had few problems with automatic reloads, at least not so many errors... Barbara -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
reloadable doesn't seem to work
I'm running 4.1.12, with reloadable='true' in my Context, however it won't reload any changed classes. It used to along time ago, 4.0.3, but doesn't anymore. I've basically have been restarting tomcat each time I make a change, which is becoming very annoying. I've tried to use the manager to stop, start, reload, etc my webapp, but it doesn't seem to help. Any idea? My webapp is part of the Apache-tomcat service if that helps. Thanks, John -- John Walstra [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Cannot get Tomcat to do reloadable=true
Adam, if your application name is brooklyn... Try to write docBase=brooklyn or docBase=c:\tomcatpath\webapps\brooklyn Good luck. - Original Message - From: Adam Greene [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Monday, September 30, 2002 4:43 PM Subject: Cannot get Tomcat to do reloadable=true I have tried everything, but Tomcat (4.1.10) simply will reload any class files that I change. I have to stop and restart Tomcat inorder for changes to be picked up. I even copied a working config from another computer that does work, and that still didn't fix it. Does anyone have any ideas what might be wrong?? Here is the code I tried using: Host className=org.apache.catalina.core.StandardHost appBase=creditunions autoDeploy=true configClass=org.apache.catalina.startup.ContextConfig contextClass=org.apache.catalina.core.StandardContext debug=0 deployXML=true errorReportValveClass=org.apache.catalina.valves.ErrorReportValve liveDeploy=true mapperClass=org.apache.catalina.core.StandardHostMapper name=adam unpackWARs=false Context className=org.apache.catalina.core.StandardContext cachingAllowed=true charsetMapperClass=org.apache.catalina.util.CharsetMapper cookies=true crossContext=false debug=0 displayName=Tapestry Tutorial docBase=victory/brooklyn mapperClass=org.apache.catalina.core.StandardContextMapper path=/brooklyn privileged=false reloadable=true swallowOutput=false useNaming=true wrapperClass=org.apache.catalina.core.StandardWrapper /Context -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
reloadable=true its OK
For somebody that was the same problem, i'll check the problem... I placed my driver in /WEB-INF/lib and /shared/lib, then, when i changed some class, my application didn´t connect with my database again. If you only place in /shared/lib, works! That´s all folks.
Cannot get Tomcat to do reloadable=true
I have tried everything, but Tomcat (4.1.10) simply will reload any class files that I change. I have to stop and restart Tomcat inorder for changes to be picked up. I even copied a working config from another computer that does work, and that still didn't fix it. Does anyone have any ideas what might be wrong?? Here is the code I tried using: Host className=org.apache.catalina.core.StandardHost appBase=creditunions autoDeploy=true configClass=org.apache.catalina.startup.ContextConfig contextClass=org.apache.catalina.core.StandardContext debug=0 deployXML=true errorReportValveClass=org.apache.catalina.valves.ErrorReportValve liveDeploy=true mapperClass=org.apache.catalina.core.StandardHostMapper name=adam unpackWARs=false Context className=org.apache.catalina.core.StandardContext cachingAllowed=true charsetMapperClass=org.apache.catalina.util.CharsetMapper cookies=true crossContext=false debug=0 displayName=Tapestry Tutorial docBase=victory/brooklyn mapperClass=org.apache.catalina.core.StandardContextMapper path=/brooklyn privileged=false reloadable=true swallowOutput=false useNaming=true wrapperClass=org.apache.catalina.core.StandardWrapper /Context -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Cannot get Tomcat to do reloadable=true
Actually I went through this just this weekend. I discovered that IE's caching was part of the problem, or at least it was for me. I was making very minute changes, like a string printing to the screen. When you reload the page, hold the shift key down. If that doesn't work, try clearing your browser cache. I've also noticed that occasionally with very minor changes it doesn't reload. I'm convinced that the issue relates more to browser caching than with Tomcat. Or, it might be sun spots. Stan Tomcat Users List tomcat- [EMAIL PROTECTED],[EMAIL PROTECTED] wrote: I have tried everything, but Tomcat (4.1.10) simply will reload any class files that I change. I have to stop and restart Tomcat inorder for changes to be picked up. I even copied a working config from another computer that does work, and that still didn't fix it. Does anyone have any ideas what might be wrong?? Here is the code I tried using: Host className=org.apache.catalina.core.StandardHost appBase=creditunions autoDeploy=true configClass=org.apache.catalina.startup.ContextConfig contextClass=org.apache.catalina.core.StandardContext debug=0 deployXML=true errorReportValveClass=org.apache.catalina.valves.Erro rReportValve liveDeploy=true mapperClass=org.apache.catalina.core.StandardHostMapp er name=adam unpackWARs=false Context className=org.apache.catalina.core.StandardContext cachingAllowed=true charsetMapperClass=org.apache.catalina.util.CharsetMa pper cookies=true crossContext=false debug=0 displayName=Tapestry Tutorial docBase=victory/brooklyn mapperClass=org.apache.catalina.core.StandardContextM apper path=/brooklyn privileged=false reloadable=true swallowOutput=false useNaming=true wrapperClass=org.apache.catalina.core.StandardWrapper /Context -- To unsubscribe, e-mail: mailto:tomcat-user- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
reloadable=true
Hi everybody! I set this property(reloadable=true) on my context in server.xml, but don´t works?! When i change any class, tomcat don't work until i restart it. Any idea about this problem? Thanks in advanced.
Re: reloadable=true
I have the same problem. I have changed any Context in web.xml and also checked the server.xml file for DefaultContext and stuff, but Tomcat just won't reload classes. I am using latest Tomcat 3.3 version, JDK1.3 IBM Linux Regards Danny On 27 Sep 2002, at 11:07, Lindomar wrote: Hi everybody! I set this property(reloadable=true) on my context in server.xml, but don´t works?! When i change any class, tomcat don't work until i restart it. Any idea about this problem? Thanks in advanced. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: reloadable=true
Have you tried using the Manager app? How are you updating your classes? Just deleting them and adding the new one? John -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Friday, September 27, 2002 10:55 AM To: Tomcat Users List Subject: Re: reloadable=true I have the same problem. I have changed any Context in web.xml and also checked the server.xml file for DefaultContext and stuff, but Tomcat just won't reload classes. I am using latest Tomcat 3.3 version, JDK1.3 IBM Linux Regards Danny On 27 Sep 2002, at 11:07, Lindomar wrote: Hi everybody! I set this property(reloadable=true) on my context in server.xml, but don´t works?! When i change any class, tomcat don't work until i restart it. Any idea about this problem? Thanks in advanced. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: reloadable=true
I tried the Manager app, updating and deleting and adding the new one, none works; but the exception is generated : No driver suitable ?! Regards, Lindomar. - Original Message - From: Turner, John [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Friday, September 27, 2002 11:48 AM Subject: RE: reloadable=true Quer ter seu próprio endereço na Internet? Garanta já o seu e ainda ganhe cinco e-mails personalizados. DomíniosBOL - http://dominios.bol.com.br Have you tried using the Manager app? How are you updating your classes? Just deleting them and adding the new one? John -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Friday, September 27, 2002 10:55 AM To: Tomcat Users List Subject: Re: reloadable=true I have the same problem. I have changed any Context in web.xml and also checked the server.xml file for DefaultContext and stuff, but Tomcat just won't reload classes. I am using latest Tomcat 3.3 version, JDK1.3 IBM Linux Regards Danny On 27 Sep 2002, at 11:07, Lindomar wrote: Hi everybody! I set this property(reloadable=true) on my context in server.xml, but don´t works?! When i change any class, tomcat don't work until i restart it. Any idea about this problem? Thanks in advanced. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
reloadable=true problems
I have been upgrading our applications to Tomcat version 4.1.9 - 4.1.10. It really seems to be something wrong with the reloadable=true attribute in context specification, as it doesn't do anything. The only way for me right now to get an change into a jsp page, is to stop tomcat, delete the work folder, and start tomcat again. is this a bug in those versions, has it been fixed in later releases (4.1.11-12) ? thank you, Reynir Þór Hübner [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
ROOT not reloadable?
jacob has been kindly helping me understand the restrictions of contexts in tomcat, but one problem that came up and i would like some feedback from tomcat developers. this is with the 4.1.9-beta version. why is the ROOT context not reloadable? i'm using a framework that i've heavily modified based on ActionServlet. it works fine (finds the templates properely) when invoked on a subdirectory, but it is unable to find the templates when invoked by a servlet in the ROOT context. this seems like a bug (everything is in the same place), but i need to figure out WHAT information is being provided incorrectly before i can make intelligent comments, i just thought i'd mention this for now. what is the suggested method of configuring tomcat4 to simply process files with certain extensions regardless of directory location? -- CraigL-Thx(); Be Developer ID: 5852 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: reloadable=true just not working. Any ideas gentlefolk?
I also have the same problem, I set reloadable=true, when I change something in my servlet, it never use the new one, everytime I still have to restart the tomcat. Louis - Original Message - From: Jason Koeninger [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Tuesday, May 21, 2002 8:18 PM Subject: Re: reloadable=true just not working. Any ideas gentlefolk? I don't believe the class loader recognizes any new code other than servlets and jsp files. If you have new classes called by servlets, they won't be reloaded. If you search in the archives, you should find a lot of discussions on this topic. If you have servlets or jsp's that aren't reloading, I'm not sure what may be going wrong. Best Regards, Jason Koeninger JJ Computer Consulting http://www.jjcc.com --- Ray Letts [EMAIL PROTECTED] wrote: Below is a snippet from my conf/server.xml file. From all the docs I've read, and the examples, this should work. However the tomcat class loader does not recognize newly compiled class files and still uses the cached versions. Can anyone spot a problem with the xml below? It parses upon startup. But to get the newly compiled classes cached I have to restart the server. and whether thru cmd line or manager web app, this is not want I want to do during development. TIA Ray Context path=/BugTracker docBase=/app/tomcat/jakarta-tomcat/dist/webapps/BugTracker/ debug=0 reloadable=true / ps above is the full path to the webapp, however I have tried the relative as well. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] __ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
reloadable=true just not working. Any ideas gentlefolk?
Below is a snippet from my conf/server.xml file. From all the docs I've read, and the examples, this should work. However the tomcat class loader does not recognize newly compiled class files and still uses the cached versions. Can anyone spot a problem with the xml below? It parses upon startup. But to get the newly compiled classes cached I have to restart the server. and whether thru cmd line or manager web app, this is not want I want to do during development. TIA Ray Context path=/BugTracker docBase=/app/tomcat/jakarta-tomcat/dist/webapps/BugTracker/ debug=0 reloadable=true / ps above is the full path to the webapp, however I have tried the relative as well. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: reloadable=true just not working. Any ideas gentlefolk?
I don't have the answer to why reloading isn't working, but I can recommend using the tomcat manager app to remove and install your app to freshen it. That doesn't require a restart of tomcat. One important note though, if your webapp's main directly exists, this won't work. You have to blow away that directory after you remove. I just have ant blow away the directory and drop a fresh .war in the webapps/ dir, then manager-remove, then manager-install. The only downside is that I haven't worked out why my db pool object doesn't release its connections. Thus, each time I do it I burn 3 database connections :) Michael --- Ray Letts [EMAIL PROTECTED] wrote: Below is a snippet from my conf/server.xml file. From all the docs I've read, and the examples, this should work. However the tomcat class loader does not recognize newly compiled class files and still uses the cached versions. Can anyone spot a problem with the xml below? It parses upon startup. But to get the newly compiled classes cached I have to restart the server. and whether thru cmd line or manager web app, this is not want I want to do during development. TIA Ray Context path=/BugTracker docBase=/app/tomcat/jakarta-tomcat/dist/webapps/BugTracker/ debug=0 reloadable=true / ps above is the full path to the webapp, however I have tried the relative as well. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] __ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: reloadable=true just not working. Any ideas gentlefolk?
I don't believe the class loader recognizes any new code other than servlets and jsp files. If you have new classes called by servlets, they won't be reloaded. If you search in the archives, you should find a lot of discussions on this topic. If you have servlets or jsp's that aren't reloading, I'm not sure what may be going wrong. Best Regards, Jason Koeninger JJ Computer Consulting http://www.jjcc.com --- Ray Letts [EMAIL PROTECTED] wrote: Below is a snippet from my conf/server.xml file. From all the docs I've read, and the examples, this should work. However the tomcat class loader does not recognize newly compiled class files and still uses the cached versions. Can anyone spot a problem with the xml below? It parses upon startup. But to get the newly compiled classes cached I have to restart the server. and whether thru cmd line or manager web app, this is not want I want to do during development. TIA Ray Context path=/BugTracker docBase=/app/tomcat/jakarta-tomcat/dist/webapps/BugTracker/ debug=0 reloadable=true / ps above is the full path to the webapp, however I have tried the relative as well. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] __ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: reloadable=true not working--- problems with reloading servl ets
Why is it that during reloading of changed classes, tomcat clears all variables from HTTPSession? kB __ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: reloadable=true not working--- problems with reloading servlets
On Sat, 18 May 2002, kelly, Burrowa wrote: Date: Sat, 18 May 2002 15:34:31 +0100 (BST) From: kelly, Burrowa [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: Re: reloadable=true not working--- problems with reloading servl ets Why is it that during reloading of changed classes, tomcat clears all variables from HTTPSession? Java does not provide any APIs to replace the classes that have been recompiled. So, servlet containers implement reload by throwing away the entire webapp class loader (including all classes that have been loaded from /WEB-INF/classes and /WEB-INF/lib), and starts the app over again. However, Tomcat also implements a feature that helps in the scenario you describe -- if you make sure that all of the beans you store as session attributes are Serializable, then Tomcat can save and restore them for you as it does the restart. This also works across a regular shutdown and restart of Tomcat itself. kB Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
reloadable=true not working--- problems with reloading servlets
Hello all. Hmm heard this was a problem in Tomcat 3 but we're running a fresh Tomcat 4.03 integrated with Apache HTTP Server Version 1.3 I've set the reloadable to be true in the server.xml, restarted Tomcat but it doesn't seem to be reloading. Is this still a bug in 4.03? I've tried searching the bug reports but that is one crazy form for bugs they have on the jakarta site. Anyone have success with this? or not? Is it a bug? many thanks! Ray Letts -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: reloadable=true not working--- problems with reloading servlets
I've found this to be true on occassions, but I've never found out any reason why. If you restart your app using the manager application, then it seems to reload it properly. Manager application runs from the URL, details can be found here: http://jakarta.apache.org/tomcat/tomcat-4.0-doc/manager-howto.html Hope this helps Adam -Original Message- From: Ray Letts [mailto:[EMAIL PROTECTED]] Sent: 17 May 2002 16:48 To: Tomcat Users List Subject: reloadable=true not working--- problems with reloading servlets Hello all. Hmm heard this was a problem in Tomcat 3 but we're running a fresh Tomcat 4.03 integrated with Apache HTTP Server Version 1.3 I've set the reloadable to be true in the server.xml, restarted Tomcat but it doesn't seem to be reloading. Is this still a bug in 4.03? I've tried searching the bug reports but that is one crazy form for bugs they have on the jakarta site. Anyone have success with this? or not? Is it a bug? many thanks! Ray Letts -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] ** This message may contain information which is confidential or privileged. If you are not the intended recipient, please advise the sender immediately by reply e-mail and delete this message and any attachments without retaining a copy. ** -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: reloadable=true not working--- problems with reloading servl ets
Yes the manager app will restart and the Tomcat will reload but I want Tomcat to detect newly compiled class files and reload without restarting, whether via the command line or via the manager web app. This will avoid developers asking each other if they can 'restart' Tomcat while working on code. Ray -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: reloadable=true not working--- problems with reloading servl ets
Just my two cents, but I never have developers work on the same server instance. You can run multiple tomcat instances on the same server, or you can run one on each developer workstation (what I usually do). The whole reason I'm using tomcat is because it's free and lightweight enough to deploy on most workstations. Ray Letts [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] a cc: Subject: Re: reloadable=true not working--- problems with reloading 05/17/2002 10:59 servlets AM Please respond to Tomcat Users List Yes the manager app will restart and the Tomcat will reload but I want Tomcat to detect newly compiled class files and reload without restarting, whether via the command line or via the manager web app. This will avoid developers asking each other if they can 'restart' Tomcat while working on code. Ray -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: reloadable=true not working--- problems with reloading servl ets
I have same problem, even reload through manager does not reload the servlet class, but it will automatically pick up jsp timestamp. Everytime, I change servlet, I have to restart tomcat, what a pain Bing -Original Message- From: Ray Letts To: Tomcat Users List Sent: 5/17/02 8:59 AM Subject: Re: reloadable=true not working--- problems with reloading servl ets Yes the manager app will restart and the Tomcat will reload but I want Tomcat to detect newly compiled class files and reload without restarting, whether via the command line or via the manager web app. This will avoid developers asking each other if they can 'restart' Tomcat while working on code. Ray -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: JSP-pages and reloadable
Looks like Glenn Nielsen beat me to it. He just added this today. Thanks Glenn! Abe -Original Message- From: Abraham Fathman [mailto:[EMAIL PROTECTED]] Sent: Monday, May 06, 2002 12:43 AM To: 'Tomcat Users List' Subject: RE: JSP-pages and reloadable Craig, Good advice! I'll work on it. Thanks for the encouragement. Abe -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Sunday, May 05, 2002 6:06 PM To: Tomcat Users List Cc: [EMAIL PROTECTED] Subject: RE: JSP-pages and reloadable On Sun, 5 May 2002, Abraham Fathman wrote: Date: Sun, 5 May 2002 00:16:31 -0400 From: Abraham Fathman [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: RE: JSP-pages and reloadable I have had that problem before: included jsp's updating but the outer one not compiling. Why doesn't this feature get added to tomcat? The best way to get something like this added is to send a patch enabling this feature to the TOMCAT-DEV list. I know weblogic does it and it is quite an annoyance in tomcat Many of Tomcat's favorite features came out of users wanting it, so they learned enough about the code to propose a fix themselvs. It *is* open source, after all :-). Abe Craig -Original Message- From: Jay Gardner [mailto:[EMAIL PROTECTED]] Sent: Saturday, May 04, 2002 9:59 PM To: Tomcat Users List Subject: RE: JSP-pages and reloadable I have run into similar problems before. It turned out to be one of two things. Either I had to force my browser to reload or I was making changes in a JSP that was an include for another JSP. I am sure you have tried the first. I don't know if the second is what you are doing, but if it is, you will need to save the outer JSP so the timestamp changes. Then both the outer and any included JSPs will be re-compiled. Other than that I don't know what the problem could be. Regards, --JG -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Saturday, May 04, 2002 10:58 AM To: Tomcat Users List Subject: Re: JSP-pages and reloadable Mattias Brändström wrote: I have a simple question. Is there a way to get Tomcat to handle JSP-pages the same way it does classes in WEB-INF when you set reloadable=true in your Context-element. It is a bit cumbersome to restart tomcat and apache every time I have made a change to my JSP-page... You don't have to restart Tomcat /Apache when the jsp-page is changed. Just reload it in your browser. For some reason that doesn't work for me. Is there some kind of special configuration that needs to be done or should that work automaticaly? I think it's ... Context ... reloadable=true ... / P. -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: JSP-pages and reloadable
On Sun, 5 May 2002, Abraham Fathman wrote: Date: Sun, 5 May 2002 00:16:31 -0400 From: Abraham Fathman [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: RE: JSP-pages and reloadable I have had that problem before: included jsp's updating but the outer one not compiling. Why doesn't this feature get added to tomcat? The best way to get something like this added is to send a patch enabling this feature to the TOMCAT-DEV list. I know weblogic does it and it is quite an annoyance in tomcat Many of Tomcat's favorite features came out of users wanting it, so they learned enough about the code to propose a fix themselvs. It *is* open source, after all :-). Abe Craig -Original Message- From: Jay Gardner [mailto:[EMAIL PROTECTED]] Sent: Saturday, May 04, 2002 9:59 PM To: Tomcat Users List Subject: RE: JSP-pages and reloadable I have run into similar problems before. It turned out to be one of two things. Either I had to force my browser to reload or I was making changes in a JSP that was an include for another JSP. I am sure you have tried the first. I don't know if the second is what you are doing, but if it is, you will need to save the outer JSP so the timestamp changes. Then both the outer and any included JSPs will be re-compiled. Other than that I don't know what the problem could be. Regards, --JG -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Saturday, May 04, 2002 10:58 AM To: Tomcat Users List Subject: Re: JSP-pages and reloadable Mattias Brändström wrote: I have a simple question. Is there a way to get Tomcat to handle JSP-pages the same way it does classes in WEB-INF when you set reloadable=true in your Context-element. It is a bit cumbersome to restart tomcat and apache every time I have made a change to my JSP-page... You don't have to restart Tomcat /Apache when the jsp-page is changed. Just reload it in your browser. For some reason that doesn't work for me. Is there some kind of special configuration that needs to be done or should that work automaticaly? I think it's ... Context ... reloadable=true ... / P. -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: JSP-pages and reloadable
Craig, Good advice! I'll work on it. Thanks for the encouragement. Abe -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Sunday, May 05, 2002 6:06 PM To: Tomcat Users List Cc: [EMAIL PROTECTED] Subject: RE: JSP-pages and reloadable On Sun, 5 May 2002, Abraham Fathman wrote: Date: Sun, 5 May 2002 00:16:31 -0400 From: Abraham Fathman [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: RE: JSP-pages and reloadable I have had that problem before: included jsp's updating but the outer one not compiling. Why doesn't this feature get added to tomcat? The best way to get something like this added is to send a patch enabling this feature to the TOMCAT-DEV list. I know weblogic does it and it is quite an annoyance in tomcat Many of Tomcat's favorite features came out of users wanting it, so they learned enough about the code to propose a fix themselvs. It *is* open source, after all :-). Abe Craig -Original Message- From: Jay Gardner [mailto:[EMAIL PROTECTED]] Sent: Saturday, May 04, 2002 9:59 PM To: Tomcat Users List Subject: RE: JSP-pages and reloadable I have run into similar problems before. It turned out to be one of two things. Either I had to force my browser to reload or I was making changes in a JSP that was an include for another JSP. I am sure you have tried the first. I don't know if the second is what you are doing, but if it is, you will need to save the outer JSP so the timestamp changes. Then both the outer and any included JSPs will be re-compiled. Other than that I don't know what the problem could be. Regards, --JG -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Saturday, May 04, 2002 10:58 AM To: Tomcat Users List Subject: Re: JSP-pages and reloadable Mattias Brändström wrote: I have a simple question. Is there a way to get Tomcat to handle JSP-pages the same way it does classes in WEB-INF when you set reloadable=true in your Context-element. It is a bit cumbersome to restart tomcat and apache every time I have made a change to my JSP-page... You don't have to restart Tomcat /Apache when the jsp-page is changed. Just reload it in your browser. For some reason that doesn't work for me. Is there some kind of special configuration that needs to be done or should that work automaticaly? I think it's ... Context ... reloadable=true ... / P. -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
JSP-pages and reloadable
Hi! I have a simple question. Is there a way to get Tomcat to handle JSP-pages the same way it does classes in WEB-INF when you set reloadable=true in your Context-element. It is a bit cumbersome to restart tomcat and apache every time I have made a change to my JSP-page... Regards, Mattias -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: JSP-pages and reloadable
lørdag 4. mai 2002, 17:23, skrev Mattias Brändström: Hi! I have a simple question. Is there a way to get Tomcat to handle JSP-pages the same way it does classes in WEB-INF when you set reloadable=true in your Context-element. It is a bit cumbersome to restart tomcat and apache every time I have made a change to my JSP-page... You don't have to restart Tomcat /Apache when the jsp-page is changed. Just reload it in your browser. -- ToreS -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: JSP-pages and reloadable
Tore Skogly wrote: lørdag 4. mai 2002, 17:23, skrev Mattias Brändström: Hi! I have a simple question. Is there a way to get Tomcat to handle JSP-pages the same way it does classes in WEB-INF when you set reloadable=true in your Context-element. It is a bit cumbersome to restart tomcat and apache every time I have made a change to my JSP-page... You don't have to restart Tomcat /Apache when the jsp-page is changed. Just reload it in your browser. For some reason that doesn't work for me. Is there some kind of special configuration that needs to be done or should that work automaticaly? Regards, Mattias -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: JSP-pages and reloadable
Should be the only way for it to work Why don't you try a test page in a new web app. Goto tomcat's\webapp directory create a directory called test create a file in test called test.jsp place %=executing jsp% in test.jsp Navigate to it in the browser http://localhost:8080/test/test.jsp (this is by default if you have changed your port or the server is on a different machine it will be different...) Monitor your work directory for the .java and .class file that will be created. There should be a tomcat/work/hostname/test/test$jsp.java. When you change test.jsp and access it again the test$jsp.java should update. I know this has been true on all of the versions of tomcat that I have used. (3.3-4.0.3) Hope this helps, Abe -Original Message- From: Mattias Brändström [mailto:[EMAIL PROTECTED]] Sent: Saturday, May 04, 2002 12:58 PM To: Tomcat Users List Subject: Re: JSP-pages and reloadable Tore Skogly wrote: lørdag 4. mai 2002, 17:23, skrev Mattias Brändström: Hi! I have a simple question. Is there a way to get Tomcat to handle JSP-pages the same way it does classes in WEB-INF when you set reloadable=true in your Context-element. It is a bit cumbersome to restart tomcat and apache every time I have made a change to my JSP-page... You don't have to restart Tomcat /Apache when the jsp-page is changed. Just reload it in your browser. For some reason that doesn't work for me. Is there some kind of special configuration that needs to be done or should that work automaticaly? Regards, Mattias -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: JSP-pages and reloadable
Mattias Brändström wrote: I have a simple question. Is there a way to get Tomcat to handle JSP-pages the same way it does classes in WEB-INF when you set reloadable=true in your Context-element. It is a bit cumbersome to restart tomcat and apache every time I have made a change to my JSP-page... You don't have to restart Tomcat /Apache when the jsp-page is changed. Just reload it in your browser. For some reason that doesn't work for me. Is there some kind of special configuration that needs to be done or should that work automaticaly? I think it's ... Context ... reloadable=true ... / P. -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: JSP-pages and reloadable
I have run into similar problems before. It turned out to be one of two things. Either I had to force my browser to reload or I was making changes in a JSP that was an include for another JSP. I am sure you have tried the first. I don't know if the second is what you are doing, but if it is, you will need to save the outer JSP so the timestamp changes. Then both the outer and any included JSPs will be re-compiled. Other than that I don't know what the problem could be. Regards, --JG -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Saturday, May 04, 2002 10:58 AM To: Tomcat Users List Subject: Re: JSP-pages and reloadable Mattias Brändström wrote: I have a simple question. Is there a way to get Tomcat to handle JSP-pages the same way it does classes in WEB-INF when you set reloadable=true in your Context-element. It is a bit cumbersome to restart tomcat and apache every time I have made a change to my JSP-page... You don't have to restart Tomcat /Apache when the jsp-page is changed. Just reload it in your browser. For some reason that doesn't work for me. Is there some kind of special configuration that needs to be done or should that work automaticaly? I think it's ... Context ... reloadable=true ... / P. -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: JSP-pages and reloadable
Jay Gardner wrote: I have run into similar problems before. It turned out to be one of two things. Either I had to force my browser to reload or I was making changes in a JSP that was an include for another JSP. I am sure you have tried the first. I don't know if the second is what you are doing, but if it is, you will need to save the outer JSP so the timestamp changes. Then both the outer and any included JSPs will be re-compiled. Other than that I don't know what the problem could be. It turned out to be a problem related to the dates on the jsp-files. I was editing files shared with samba to my windows box using WinEmacs. For some reason the dates on the files did not get updated correcty when I saved them so I had to 'touch' them in order to get a good date. When I did that everything worked fine. Regards, Mattias -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: JSP-pages and reloadable
I have had that problem before: included jsp's updating but the outer one not compiling. Why doesn't this feature get added to tomcat? I know weblogic does it and it is quite an annoyance in tomcat Abe -Original Message- From: Jay Gardner [mailto:[EMAIL PROTECTED]] Sent: Saturday, May 04, 2002 9:59 PM To: Tomcat Users List Subject: RE: JSP-pages and reloadable I have run into similar problems before. It turned out to be one of two things. Either I had to force my browser to reload or I was making changes in a JSP that was an include for another JSP. I am sure you have tried the first. I don't know if the second is what you are doing, but if it is, you will need to save the outer JSP so the timestamp changes. Then both the outer and any included JSPs will be re-compiled. Other than that I don't know what the problem could be. Regards, --JG -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Saturday, May 04, 2002 10:58 AM To: Tomcat Users List Subject: Re: JSP-pages and reloadable Mattias Brändström wrote: I have a simple question. Is there a way to get Tomcat to handle JSP-pages the same way it does classes in WEB-INF when you set reloadable=true in your Context-element. It is a bit cumbersome to restart tomcat and apache every time I have made a change to my JSP-page... You don't have to restart Tomcat /Apache when the jsp-page is changed. Just reload it in your browser. For some reason that doesn't work for me. Is there some kind of special configuration that needs to be done or should that work automaticaly? I think it's ... Context ... reloadable=true ... / P. -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Reloadable: reloads also JSP pages?
Hi, a detail I haven't yet found, neither in the archives nor in the user- guide: Does the reload attribute in context not just control reloading of servlets, but also recompiling of JSP pages? I observed that behaviour with reload=false, i.e. the users still got the old version of changed JSP pages. Thus I switched back to reload=true, although this isn't recommended for production sites. Our site has frequent changes of JSP pages, but servlets are updated rather seldom. Is there any other switch to control recompiling (or caching) of JSP pages? Gerd Kersten -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: Reloading Web Applications without manager and without reloadable=true
Sorry, This reply has been late in coming... Thanks Jeff, for your solution. I'll try this out. I am still not quite sure whether this will prevent users from reloading other user's webapps. I'll try it out and let you know. Thanks for the help, Tarun Jeff Larsen wrote: As long as the role-name in the manager app web.xml matches the role assigned to a user in tomcat-users.xml, it works. - Original Message - From: Cox, Charlie [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Monday, April 01, 2002 10:15 AM Subject: RE: Reloading Web Applications without manager and without reloadable=true I stand corrected. I didn't think you could override the default manager role since it is not defined in the web.xml. So you have manager working with a user without the 'manager' role? Or are you adding another role requirement to to the manager path? This is what it appears that you are doing in the example as opposed to replacing 'manager' with 'myappmanager'. Certainly you could add another role requirement on top of manager - you would just have to make sure that each webapp's manager does the same if you want users to only have access to their own app. Charlie -Original Message- From: Jeff Larsen [mailto:[EMAIL PROTECTED]] Sent: Monday, April 01, 2002 10:34 AM To: Tomcat Users List Subject: Re: Reloading Web Applications without manager and without reloadable=true Not true. I've tested with a role-name other than manager. It is configurable in the web.xml for the manager app. See excerpt below. (TC 4.0.3) security-constraint web-resource-collection web-resource-nameEntire Application/web-resource-name url-pattern/*/url-patter /web-resource-collection auth-constraint role-namemyappmanager/role-name /auth-constraint /security-constraint - Original Message - From: Cox, Charlie [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Monday, April 01, 2002 6:02 AM Subject: RE: Reloading Web Applications without manager and without reloadable=true The role must be 'manager'. The manager app currently does not let you specify the role to use. Charlie -Original Message- From: Jeff Larsen [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 28, 2002 2:14 PM To: Tomcat Users List Subject: Re: Reloading Web Applications without manager and without reloadable=true I'm not 100% sure about this, but I'm sure someone will correct me if I'm wrong Isn't the manager app limited to apps within the same virtual host? So have your sysadmin create a tomcat virtual host just for your web app. Install the manager app in your virtual host under a unique context name so as not to conflict with the manager app for other virtual hosts. Then configure the role in the web.xml for YOUR manager app to a custom role and create a unique username and password for that role in tomcat-users.xml. Now you have access to a manager app just for your webapp. And your sysadmin rests easy knowing that you can't mess with anyone elses webapps. Jeff - Original Message - From: Tarun Ramakrishna Elankath [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, March 27, 2002 10:28 AM Subject: Reloading Web Applications without manager and without reloadable=true Hello all, I had asked this question previously without anybody understanding. I need to be able to reload my web-application *without* setting the reloadable=true parameter in the context tag, when I *dont* have access to the manager web-application. Why? This is because my web-application will be on a *production* server where reloadable *should* be set equal to false (as the documentation recommends). And I will not be given access to the manager application because my web-application resides with web-apps of other independent developers. I do not want to bother my system administrator for every modification that I commit to the site. (Even production environments suffer from modification) Is there another way of forcing Tomcat to reload classes of *only* my web application? If no such program exists then I would be grateful if someone could point me towards how to write one. Any help appreciated, Tarun -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles
RE: Reloading Web Applications without manager and without reloadable=true
The role must be 'manager'. The manager app currently does not let you specify the role to use. Charlie -Original Message- From: Jeff Larsen [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 28, 2002 2:14 PM To: Tomcat Users List Subject: Re: Reloading Web Applications without manager and without reloadable=true I'm not 100% sure about this, but I'm sure someone will correct me if I'm wrong Isn't the manager app limited to apps within the same virtual host? So have your sysadmin create a tomcat virtual host just for your web app. Install the manager app in your virtual host under a unique context name so as not to conflict with the manager app for other virtual hosts. Then configure the role in the web.xml for YOUR manager app to a custom role and create a unique username and password for that role in tomcat-users.xml. Now you have access to a manager app just for your webapp. And your sysadmin rests easy knowing that you can't mess with anyone elses webapps. Jeff - Original Message - From: Tarun Ramakrishna Elankath [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, March 27, 2002 10:28 AM Subject: Reloading Web Applications without manager and without reloadable=true Hello all, I had asked this question previously without anybody understanding. I need to be able to reload my web-application *without* setting the reloadable=true parameter in the context tag, when I *dont* have access to the manager web-application. Why? This is because my web-application will be on a *production* server where reloadable *should* be set equal to false (as the documentation recommends). And I will not be given access to the manager application because my web-application resides with web-apps of other independent developers. I do not want to bother my system administrator for every modification that I commit to the site. (Even production environments suffer from modification) Is there another way of forcing Tomcat to reload classes of *only* my web application? If no such program exists then I would be grateful if someone could point me towards how to write one. Any help appreciated, Tarun -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: Reloading Web Applications without manager and without reloadable=true
Not true. I've tested with a role-name other than manager. It is configurable in the web.xml for the manager app. See excerpt below. (TC 4.0.3) security-constraint web-resource-collection web-resource-nameEntire Application/web-resource-name url-pattern/*/url-patter /web-resource-collection auth-constraint role-namemyappmanager/role-name /auth-constraint /security-constraint - Original Message - From: Cox, Charlie [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Monday, April 01, 2002 6:02 AM Subject: RE: Reloading Web Applications without manager and without reloadable=true The role must be 'manager'. The manager app currently does not let you specify the role to use. Charlie -Original Message- From: Jeff Larsen [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 28, 2002 2:14 PM To: Tomcat Users List Subject: Re: Reloading Web Applications without manager and without reloadable=true I'm not 100% sure about this, but I'm sure someone will correct me if I'm wrong Isn't the manager app limited to apps within the same virtual host? So have your sysadmin create a tomcat virtual host just for your web app. Install the manager app in your virtual host under a unique context name so as not to conflict with the manager app for other virtual hosts. Then configure the role in the web.xml for YOUR manager app to a custom role and create a unique username and password for that role in tomcat-users.xml. Now you have access to a manager app just for your webapp. And your sysadmin rests easy knowing that you can't mess with anyone elses webapps. Jeff - Original Message - From: Tarun Ramakrishna Elankath [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, March 27, 2002 10:28 AM Subject: Reloading Web Applications without manager and without reloadable=true Hello all, I had asked this question previously without anybody understanding. I need to be able to reload my web-application *without* setting the reloadable=true parameter in the context tag, when I *dont* have access to the manager web-application. Why? This is because my web-application will be on a *production* server where reloadable *should* be set equal to false (as the documentation recommends). And I will not be given access to the manager application because my web-application resides with web-apps of other independent developers. I do not want to bother my system administrator for every modification that I commit to the site. (Even production environments suffer from modification) Is there another way of forcing Tomcat to reload classes of *only* my web application? If no such program exists then I would be grateful if someone could point me towards how to write one. Any help appreciated, Tarun -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: Reloading Web Applications without manager and without reloadable=true
I stand corrected. I didn't think you could override the default manager role since it is not defined in the web.xml. So you have manager working with a user without the 'manager' role? Or are you adding another role requirement to to the manager path? This is what it appears that you are doing in the example as opposed to replacing 'manager' with 'myappmanager'. Certainly you could add another role requirement on top of manager - you would just have to make sure that each webapp's manager does the same if you want users to only have access to their own app. Charlie -Original Message- From: Jeff Larsen [mailto:[EMAIL PROTECTED]] Sent: Monday, April 01, 2002 10:34 AM To: Tomcat Users List Subject: Re: Reloading Web Applications without manager and without reloadable=true Not true. I've tested with a role-name other than manager. It is configurable in the web.xml for the manager app. See excerpt below. (TC 4.0.3) security-constraint web-resource-collection web-resource-nameEntire Application/web-resource-name url-pattern/*/url-patter /web-resource-collection auth-constraint role-namemyappmanager/role-name /auth-constraint /security-constraint - Original Message - From: Cox, Charlie [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Monday, April 01, 2002 6:02 AM Subject: RE: Reloading Web Applications without manager and without reloadable=true The role must be 'manager'. The manager app currently does not let you specify the role to use. Charlie -Original Message- From: Jeff Larsen [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 28, 2002 2:14 PM To: Tomcat Users List Subject: Re: Reloading Web Applications without manager and without reloadable=true I'm not 100% sure about this, but I'm sure someone will correct me if I'm wrong Isn't the manager app limited to apps within the same virtual host? So have your sysadmin create a tomcat virtual host just for your web app. Install the manager app in your virtual host under a unique context name so as not to conflict with the manager app for other virtual hosts. Then configure the role in the web.xml for YOUR manager app to a custom role and create a unique username and password for that role in tomcat-users.xml. Now you have access to a manager app just for your webapp. And your sysadmin rests easy knowing that you can't mess with anyone elses webapps. Jeff - Original Message - From: Tarun Ramakrishna Elankath [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, March 27, 2002 10:28 AM Subject: Reloading Web Applications without manager and without reloadable=true Hello all, I had asked this question previously without anybody understanding. I need to be able to reload my web-application *without* setting the reloadable=true parameter in the context tag, when I *dont* have access to the manager web-application. Why? This is because my web-application will be on a *production* server where reloadable *should* be set equal to false (as the documentation recommends). And I will not be given access to the manager application because my web-application resides with web-apps of other independent developers. I do not want to bother my system administrator for every modification that I commit to the site. (Even production environments suffer from modification) Is there another way of forcing Tomcat to reload classes of *only* my web application? If no such program exists then I would be grateful if someone could point me towards how to write one. Any help appreciated, Tarun -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: Reloading Web Applications without manager and without reloadable=true
As long as the role-name in the manager app web.xml matches the role assigned to a user in tomcat-users.xml, it works. - Original Message - From: Cox, Charlie [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Monday, April 01, 2002 10:15 AM Subject: RE: Reloading Web Applications without manager and without reloadable=true I stand corrected. I didn't think you could override the default manager role since it is not defined in the web.xml. So you have manager working with a user without the 'manager' role? Or are you adding another role requirement to to the manager path? This is what it appears that you are doing in the example as opposed to replacing 'manager' with 'myappmanager'. Certainly you could add another role requirement on top of manager - you would just have to make sure that each webapp's manager does the same if you want users to only have access to their own app. Charlie -Original Message- From: Jeff Larsen [mailto:[EMAIL PROTECTED]] Sent: Monday, April 01, 2002 10:34 AM To: Tomcat Users List Subject: Re: Reloading Web Applications without manager and without reloadable=true Not true. I've tested with a role-name other than manager. It is configurable in the web.xml for the manager app. See excerpt below. (TC 4.0.3) security-constraint web-resource-collection web-resource-nameEntire Application/web-resource-name url-pattern/*/url-patter /web-resource-collection auth-constraint role-namemyappmanager/role-name /auth-constraint /security-constraint - Original Message - From: Cox, Charlie [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Monday, April 01, 2002 6:02 AM Subject: RE: Reloading Web Applications without manager and without reloadable=true The role must be 'manager'. The manager app currently does not let you specify the role to use. Charlie -Original Message- From: Jeff Larsen [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 28, 2002 2:14 PM To: Tomcat Users List Subject: Re: Reloading Web Applications without manager and without reloadable=true I'm not 100% sure about this, but I'm sure someone will correct me if I'm wrong Isn't the manager app limited to apps within the same virtual host? So have your sysadmin create a tomcat virtual host just for your web app. Install the manager app in your virtual host under a unique context name so as not to conflict with the manager app for other virtual hosts. Then configure the role in the web.xml for YOUR manager app to a custom role and create a unique username and password for that role in tomcat-users.xml. Now you have access to a manager app just for your webapp. And your sysadmin rests easy knowing that you can't mess with anyone elses webapps. Jeff - Original Message - From: Tarun Ramakrishna Elankath [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, March 27, 2002 10:28 AM Subject: Reloading Web Applications without manager and without reloadable=true Hello all, I had asked this question previously without anybody understanding. I need to be able to reload my web-application *without* setting the reloadable=true parameter in the context tag, when I *dont* have access to the manager web-application. Why? This is because my web-application will be on a *production* server where reloadable *should* be set equal to false (as the documentation recommends). And I will not be given access to the manager application because my web-application resides with web-apps of other independent developers. I do not want to bother my system administrator for every modification that I commit to the site. (Even production environments suffer from modification) Is there another way of forcing Tomcat to reload classes of *only* my web application? If no such program exists then I would be grateful if someone could point me towards how to write one. Any help appreciated, Tarun -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto
Re: Getting a JSP re-compiled from run-time (I don't mean reloadable=true)
Thank you Anthony, is that new in tomcat-4.x? As far as I remember in tomcat-3.2.x JSP files got recompiled only in case of reloadable=true. Zsolt On Tuesday 26 March 2002 20:39, you wrote: If the JSP file is modified it will be recompiled. If you are actually generating JSP files then when the generation finishes and the page is first requested the JSP will be compiled. You can also force compilation by updating the last modified time by 'touch'ing the file. Sincerely, Anthony Eden -Original Message- From: Zsolt Koppany [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 10:40 AM To: [EMAIL PROTECTED] Subject: Getting a JSP re-compiled from run-time (I don't mean reloadable=true) Hi, my application wants to generate JSP files during runtime and depending on application logic. I understand that setting reloadable=true would solve the problem but that would affect the run time performance of tomcat. What I mean: when I generate (modify) a JSP file I want tomcat to recompile that JSP file regardless whether reloadable is true or false. How could I do that? -- Zsolt Koppany -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- Zsolt Koppany -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: Reloading Web Applications without manager and without reloadable=true
Tarun Ramakrishna Elankath a écrit : Thanks for replying . I'll look at the tomcat docs and source and see whether there is a way of modifying tomcat to allow this functionality. Or whether I can write a class to check for changes only after a certain time period - say 3 or 4 minutes. Thanks Tarun Cox, Charlie wrote: no, you will have to have someone with maanger access restart your web app. The only other way to reload classes is to restart tomcat, which it sounds like you don't want to do. you are correct in that reloadable=false for production. Charlie -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] Well, I think that yu only need the 'manager' features... Makin' manager/stop?path=/MyApp and 3-4 mns after manager/start?path=/MyApp hope this help. Jean-Luc :O) -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: Reloading Web Applications without manager and without reloadable=true
I'm not 100% sure about this, but I'm sure someone will correct me if I'm wrong Isn't the manager app limited to apps within the same virtual host? So have your sysadmin create a tomcat virtual host just for your web app. Install the manager app in your virtual host under a unique context name so as not to conflict with the manager app for other virtual hosts. Then configure the role in the web.xml for YOUR manager app to a custom role and create a unique username and password for that role in tomcat-users.xml. Now you have access to a manager app just for your webapp. And your sysadmin rests easy knowing that you can't mess with anyone elses webapps. Jeff - Original Message - From: Tarun Ramakrishna Elankath [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, March 27, 2002 10:28 AM Subject: Reloading Web Applications without manager and without reloadable=true Hello all, I had asked this question previously without anybody understanding. I need to be able to reload my web-application *without* setting the reloadable=true parameter in the context tag, when I *dont* have access to the manager web-application. Why? This is because my web-application will be on a *production* server where reloadable *should* be set equal to false (as the documentation recommends). And I will not be given access to the manager application because my web-application resides with web-apps of other independent developers. I do not want to bother my system administrator for every modification that I commit to the site. (Even production environments suffer from modification) Is there another way of forcing Tomcat to reload classes of *only* my web application? If no such program exists then I would be grateful if someone could point me towards how to write one. Any help appreciated, Tarun -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Reloading Web Applications without manager and without reloadable=true
Hello all, I had asked this question previously without anybody understanding. I need to be able to reload my web-application *without* setting the reloadable=true parameter in the context tag, when I *dont* have access to the manager web-application. Why? This is because my web-application will be on a *production* server where reloadable *should* be set equal to false (as the documentation recommends). And I will not be given access to the manager application because my web-application resides with web-apps of other independent developers. I do not want to bother my system administrator for every modification that I commit to the site. (Even production environments suffer from modification) Is there another way of forcing Tomcat to reload classes of *only* my web application? If no such program exists then I would be grateful if someone could point me towards how to write one. Any help appreciated, Tarun -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: Reloading Web Applications without manager and without reloadable=true
no, you will have to have someone with maanger access restart your web app. The only other way to reload classes is to restart tomcat, which it sounds like you don't want to do. you are correct in that reloadable=false for production. Charlie -Original Message- From: Tarun Ramakrishna Elankath [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 27, 2002 11:29 AM To: [EMAIL PROTECTED] Subject: Reloading Web Applications without manager and without reloadable=true Hello all, I had asked this question previously without anybody understanding. I need to be able to reload my web-application *without* setting the reloadable=true parameter in the context tag, when I *dont* have access to the manager web-application. Why? This is because my web-application will be on a *production* server where reloadable *should* be set equal to false (as the documentation recommends). And I will not be given access to the manager application because my web-application resides with web-apps of other independent developers. I do not want to bother my system administrator for every modification that I commit to the site. (Even production environments suffer from modification) Is there another way of forcing Tomcat to reload classes of *only* my web application? If no such program exists then I would be grateful if someone could point me towards how to write one. Any help appreciated, Tarun -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: Reloading Web Applications without manager and without reloadable=true
Thanks for replying . I'll look at the tomcat docs and source and see whether there is a way of modifying tomcat to allow this functionality. Or whether I can write a class to check for changes only after a certain time period - say 3 or 4 minutes. Thanks Tarun Cox, Charlie wrote: no, you will have to have someone with maanger access restart your web app. The only other way to reload classes is to restart tomcat, which it sounds like you don't want to do. you are correct in that reloadable=false for production. Charlie -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Getting a JSP re-compiled from run-time (I don't mean reloadable=true)
Hi, my application wants to generate JSP files during runtime and depending on application logic. I understand that setting reloadable=true would solve the problem but that would affect the run time performance of tomcat. What I mean: when I generate (modify) a JSP file I want tomcat to recompile that JSP file regardless whether reloadable is true or false. How could I do that? -- Zsolt Koppany -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: Getting a JSP re-compiled from run-time (I don't mean reloadable=true)
If the JSP file is modified it will be recompiled. If you are actually generating JSP files then when the generation finishes and the page is first requested the JSP will be compiled. You can also force compilation by updating the last modified time by 'touch'ing the file. Sincerely, Anthony Eden -Original Message- From: Zsolt Koppany [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 10:40 AM To: [EMAIL PROTECTED] Subject: Getting a JSP re-compiled from run-time (I don't mean reloadable=true) Hi, my application wants to generate JSP files during runtime and depending on application logic. I understand that setting reloadable=true would solve the problem but that would affect the run time performance of tomcat. What I mean: when I generate (modify) a JSP file I want tomcat to recompile that JSP file regardless whether reloadable is true or false. How could I do that? -- Zsolt Koppany -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
reloadable doesn't work with warpconnector
Hi everyone, I'm new to Tomcat, so this could be something that I've done wrong... I've noticed some strange behavior with the warpconnector. For example, if I use the manager application to shutdown the root path (manager/stop?path=/) then the pages are no longer served by the *standalone* server, but using the warpconnector, they are still served. Also, I have a servlet that is under a path I've set to use reloadable=true. Accessing that applet through Apache never reflects a change unless Tomcat is restarted. However the servlet is reloaded it accessed through the standalone connector. Can anybody help me with this? It's been driving me nuts all morning --- Tomcat: 4.0.3 Warpconnector binary from apache.org jdk 1.3.1 --- Thanks! Mike Johnson -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: reloadable doesn't work with warpconnector
Hi Mike, I posted a bug about this, warp connector shows all sorts of odd behaviour with the manager app. because the way applications are indexed internally to tomcat. Example: you stop on application, then re-install it. When you reinstall it, tomcat gives it a incremented id, yet webapp is still looking for the previous id. The solution to this is to restart apache, the point where mod_webapp indexes the applications. Regards, James Williamson www.nameonthe.net - Original Message - From: Mike Johnson [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Wednesday, March 20, 2002 9:02 PM Subject: reloadable doesn't work with warpconnector Hi everyone, I'm new to Tomcat, so this could be something that I've done wrong... I've noticed some strange behavior with the warpconnector. For example, if I use the manager application to shutdown the root path (manager/stop?path=/) then the pages are no longer served by the *standalone* server, but using the warpconnector, they are still served. Also, I have a servlet that is under a path I've set to use reloadable=true. Accessing that applet through Apache never reflects a change unless Tomcat is restarted. However the servlet is reloaded it accessed through the standalone connector. Can anybody help me with this? It's been driving me nuts all morning --- Tomcat: 4.0.3 Warpconnector binary from apache.org jdk 1.3.1 --- Thanks! Mike Johnson -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
reloadable=true not working in 4.0.3?
Hello: Is reloadable=true working in 4.0.3? Tomcat does not seem to be reloading my classes when I upload a newer version to the server. Here is what I put in my /usr/local/jakarta-tomcat-4.0.3/conf/server.xml file: !-- BurnRateDiet Context -- Context path=/burnratediet docBase=burnratediet debug=0 reloadable=true / I put this in the Host directive for the local host. I am using Apache 1.3.23 and mod_webapp. Also, since this is a development server, I wanted to have all of my contexts reload classes by default. Is there a default setting for the reloading of classes? Thanks, Neil. -- Neil Aggarwal JAMM Consulting, Inc.(972) 612-6056, http://www.JAMMConsulting.com Custom Internet DevelopmentWebsites, Ecommerce, Java, databases -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: reloadable=true not working in 4.0.3?
Neil Aggarwal a écrit : Hello: Is reloadable=true working in 4.0.3? Tomcat does not seem to be reloading my classes when I upload a newer version to the server. Here is what I put in my /usr/local/jakarta-tomcat-4.0.3/conf/server.xml file: !-- BurnRateDiet Context -- Context path=/burnratediet docBase=burnratediet debug=0 reloadable=true / I put this in the Host directive for the local host. I am using Apache 1.3.23 and mod_webapp. Also, since this is a development server, I wanted to have all of my contexts reload classes by default. Is there a default setting for the reloading of classes? Thanks, Neil. -- Neil Aggarwal JAMM Consulting, Inc.(972) 612-6056, http://www.JAMMConsulting.com Custom Internet DevelopmentWebsites, Ecommerce, Java, databases -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] It had been such a mess all around it ! I give yu my code: !-- Define an Apache-Connector Service -- Service name=Tomcat-Apache Connector className=org.apache.catalina.connector.warp.WarpConnector port=8025 minProcessors=5 maxProcessors=75 enableLookups=true appBase=webapps acceptCount=10 debug=0/ !-- Replace localhost with what your Apache ServerName is set to -- Engine className=org.apache.catalina.connector.warp.WarpEngine name=Apache appBase=webapps defaulthost=MyServer.com DefaultContext reloadable=true/ Valve className=org.apache.catalina.valves.AccessLogValve directory=Logs prefix=local_access_log. suffix=.txt pattern=common / !-- Global logger unless overridden at lower levels -- Logger className=org.apache.catalina.logger.FileLogger prefix=apache_log. suffix=.txt timestamp=true/ !-- Because this Realm is here, an instance will be shared globally -- Realm className=org.apache.catalina.realm.MemoryRealm / Host name=MyServer.com debug=10 appBase=webapps unpackWARs=true !-- Tomcat Manager Context -- Context path=/manager docBase=manager privileged=true/ /Host /Engine /Service The best way is via the manager facilities. To do so yu DO have to declare the Host, like in the code below, so that it is available thru the warp connector via: WebAppDeploy manager conn /manager/ Hope this help. Jean-Luc B :O) -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: reloadable=true not working in 4.0.3?
Jean-Luc: That worked. Thanks! Neil. -- Neil Aggarwal JAMM Consulting, Inc.(972) 612-6056, http://www.JAMMConsulting.com Custom Internet DevelopmentWebsites, Ecommerce, Java, databases -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jean-Luc BEAUDET Sent: Wednesday, March 13, 2002 10:54 AM To: Tomcat Users List Subject: Re: reloadable=true not working in 4.0.3? Neil Aggarwal a écrit : Hello: Is reloadable=true working in 4.0.3? Tomcat does not seem to be reloading my classes when I upload a newer version to the server. Here is what I put in my /usr/local/jakarta-tomcat-4.0.3/conf/server.xml file: !-- BurnRateDiet Context -- Context path=/burnratediet docBase=burnratediet debug=0 reloadable=true / I put this in the Host directive for the local host. I am using Apache 1.3.23 and mod_webapp. Also, since this is a development server, I wanted to have all of my contexts reload classes by default. Is there a default setting for the reloading of classes? Thanks, Neil. -- Neil Aggarwal JAMM Consulting, Inc.(972) 612-6056, http://www.JAMMConsulting.com Custom Internet DevelopmentWebsites, Ecommerce, Java, databases -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] It had been such a mess all around it ! I give yu my code: !-- Define an Apache-Connector Service -- Service name=Tomcat-Apache Connector className=org.apache.catalina.connector.warp.WarpConnector port=8025 minProcessors=5 maxProcessors=75 enableLookups=true appBase=webapps acceptCount=10 debug=0/ !-- Replace localhost with what your Apache ServerName is set to -- Engine className=org.apache.catalina.connector.warp.WarpEngine name=Apache appBase=webapps defaulthost=MyServer.com DefaultContext reloadable=true/ Valve className=org.apache.catalina.valves.AccessLogValve directory=Logs prefix=local_access_log. suffix=.txt pattern=common / !-- Global logger unless overridden at lower levels -- Logger className=org.apache.catalina.logger.FileLogger prefix=apache_log. suffix=.txt timestamp=true/ !-- Because this Realm is here, an instance will be shared globally -- Realm className=org.apache.catalina.realm.MemoryRealm / Host name=MyServer.com debug=10 appBase=webapps unpackWARs=true !-- Tomcat Manager Context -- Context path=/manager docBase=manager privileged=true/ /Host /Engine /Service The best way is via the manager facilities. To do so yu DO have to declare the Host, like in the code below, so that it is available thru the warp connector via: WebAppDeploy manager conn /manager/ Hope this help. Jean-Luc B :O) -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Is it possible to execute a reloadable...
Hi everybody, I'm using SOLARIS 8, apache 1.3.22, tomcat 4.0.1 Tomcat is configured to communicate with Apache via the WARP Connector. As it is set for devlopement stuff, i want all the changes made in the WEB_INF/lib or classes under CATALINA_BASE/webapps to be automatically reloaded. Below is my server.xml. Where can i put my directive relodable=true so that it is effective for the whole ./webapps projects ? !-- Define an Apache-Connector Service -- Service name=Tomcat-Apache Connector className=org.apache.catalina.connector.warp.WarpConnector port=8012 minProcessors=5 maxProcessors=75 enableLookups=true acceptCount=10 debug=0/ !-- Replace localhost with what your Apache ServerName is set to -- Engine className=org.apache.catalina.connector.warp.WarpEngine name=apache debug=0 appBase=webapps defaultHost=photosharing.ko.kodak.com !-- Global logger unless overridden at lower levels -- Logger className=org.apache.catalina.logger.FileLogger prefix=apache_log. suffix=.txt timestamp=true/ !-- Because this Realm is here, an instance will be shared globally -- Realm className=org.apache.catalina.realm.MemoryRealm / /Engine /Service Any clues welcome. Regards. Jean-Luc B :O) -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Reloadable pbs...
Hi everybody, I'm using SOLARIS 8, apache 1.3.22, tomcat 4.0.1 Tomcat is configured to communicate with Apache via the WARP Connector. As it is set for devlopement stuff, i want all the changes made in the WEB_INF/lib or classes under CATALINA_BASE/webapps to be automatically reloaded. Below is my server.xml. Where can i put my directive relodable=true so that it is effective for the whole ./webapps projects ? !-- Define an Apache-Connector Service -- Service name=Tomcat-Apache Connector className=org.apache.catalina.connector.warp.WarpConnector port=8012 minProcessors=5 maxProcessors=75 enableLookups=true acceptCount=10 debug=0/ !-- Replace localhost with what your Apache ServerName is set to -- Engine className=org.apache.catalina.connector.warp.WarpEngine name=apache debug=0 appBase=webapps defaultHost=photosharing.ko.kodak.com !-- Global logger unless overridden at lower levels -- Logger className=org.apache.catalina.logger.FileLogger prefix=apache_log. suffix=.txt timestamp=true/ !-- Because this Realm is here, an instance will be shared globally -- Realm className=org.apache.catalina.realm.MemoryRealm / /Engine /Service Any clues welcome. Regards. Jean-Luc B :O) -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Pb with the reloadable option with Apache/Tomcat.
Don't pay attention if this is the second Message, please. Hi everybody, I'm using SOLARIS 8, apache 1.3.22, tomcat 4.0.1 Tomcat is configured to communicate with Apache via the WARP Connector. As it is set for devlopement stuff, i want all the changes made in the WEB_INF/lib or classes under CATALINA_BASE/webapps to be automatically reloaded. Below is my server.xml. Where can i put my directive relodable=true so that it is effective for the whole ./webapps projects ?!-- Define an Apache-Connector Service -- Service name=Tomcat-Apache Connector className=org.apache.catalina.connector.warp.WarpConnector port=8012 minProcessors=5 maxProcessors=75 enableLookups=true acceptCount=10 debug=0/ !-- Replace localhost with what your Apache ServerName is set to -- Engine className=org.apache.catalina.connector.warp.WarpEngine name=apache debug=0 appBase=webapps defaultHost=photosharing.ko.kodak.com !-- Global logger unless overridden at lower levels -- Logger className=org.apache.catalina.logger.FileLogger prefix=apache_log. suffix=.txt timestamp=true/ !-- Because this Realm is here, an instance will be shared globally -- Realm className=org.apache.catalina.realm.MemoryRealm / /Engine /Service Any clues welcome. Regards. Jean-Luc B :O) -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
reloadable
Hi! I have little problem with re-compiling JSP pages by Tomcat after modyfing them. I have the following situation: file a.jsp which includes b.jsp I'm viewing a.jsp in browser, then I modify b.jsp and reload page in browser, but I can't see changes - b.jsp doesn't recompile :-( I have reloadable=true in my context. What to do? Best regards Krzysztof Janiszewski IT Partner http://www.it-partner.com.pl/ - oprogramowanie dla kawiarni internetowych http://www.fr.pl - webhosting -- Okresl Swoje potrzeby - my znajdziemy oferte za Ciebie! [ http://oferty.onet.pl ] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: reloadable
You must either modify and save a.jsp, or delete .java and .class files for a.jsp in Tomcat's work folder. Reloadable = true is for reloading class files in WEB-INF/classes folder. Rasto -Original Message- From: Krzysztof Janiszewski [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 17, 2002 1:46 PM To: Tomcat Users List Subject: reloadable Hi! I have little problem with re-compiling JSP pages by Tomcat after modyfing them. I have the following situation: file a.jsp which includes b.jsp I'm viewing a.jsp in browser, then I modify b.jsp and reload page in browser, but I can't see changes - b.jsp doesn't recompile :-( I have reloadable=true in my context. What to do? Best regards Krzysztof Janiszewski IT Partner http://www.it-partner.com.pl/ - oprogramowanie dla kawiarni internetowych http://www.fr.pl - webhosting -- Okresl Swoje potrzeby - my znajdziemy oferte za Ciebie! [ http://oferty.onet.pl ] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: reloadable
Hi! You must either modify and save a.jsp, or delete .java and .class files for a.jsp in Tomcat's work folder. Is there any other method? I can't give access to tomcat's work directory to my customer. Pozdrawiam Krzysztof Janiszewski IT Partner http://www.it-partner.com.pl/ - oprogramowanie dla kawiarni internetowych http://www.fr.pl - webhosting -- Znudzilo Ci sie logo w komorce? Wgraj nowe [ http://komorki.onet.pl/dodatki.html ] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
