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: 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]
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]
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]
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]
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: 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=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]
reloadable=true in 4.01
Hi guys, After looking at the examples context in server.xml and reading this, I have tried the following config. Context path=/myApp docBase=myApp debug=0 privileged=true reloadable=true / This is supposed to reload a servlet if the file has changed. Currently, the page never loads when I change the class file after Tomcat has started and loaded the first version of the class. When I first tried to get this going a week ago or so, I got a null pointer exception. Although, I don't have the actual exception to paste at this time unfortunately. This is with Tomcat 4.01. Does anyone have this working? I did not see this question in the archives of this mailing list so I assume it works for most people since this is probably the first thing anyone does when setting up Tomcat during the development phase. :-) Thanks, __ Joseph Chandler Software Engineer Franke Holding USA 305 Tech Park Drive La Vergne, TN 37086 USA Switchboard: +1-615-287-8243 Fax: +1-615-287-8343 mailto:[EMAIL PROTECTED] http://www.franke.com -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
reloadable=true exception is
Here is the exception. At first, I thought it might be due to the 1.4beta3 class file bytecode or something. However, a recompile under 1.3.1_01 yeilded the same result. The exception is not thrown to the page, but to standard output on the server. Hope this helps. Thanks again. Starting service Tomcat-Apache Apache Tomcat/4.0.1 WebappClassLoader: Resource '/WEB-INF/classes/pbs/servlet/www/PartsPictureInfo Servlet.class' was modified; Date is now: Fri Jan 04 10:30:06 CST 2002 Was: Fri Jan 04 10:28:08 CST 2002 WebappClassLoader: Resource '/WEB-INF/classes/pbs/servlet/www/PartsPictureInfo Servlet.class' was modified; Date is now: Fri Jan 04 10:31:37 CST 2002 Was: Fri Jan 04 10:30:06 CST 2002 java.lang.ClassFormatError: pbs/servlet/www/PartsPictureInfoServlet (Extra bytes at the end of the class file) at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:493) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:11 1) at org.apache.catalina.loader.WebappClassLoader.findClassInternal(Webapp ClassLoader.java:1534) at org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoa der.java:852) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoa der.java:1273) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoa der.java:1156) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:80 1) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContex t.java:3267) at org.apache.catalina.core.StandardContext.reload(StandardContext.java: 2480) at org.apache.catalina.loader.WebappContextNotifier.run(WebappLoader.jav a:1315) at java.lang.Thread.run(Thread.java:484) __ Joseph Chandler Software Engineer Franke Holding USA 305 Tech Park Drive La Vergne, TN 37086 USA Switchboard: +1-615-287-8243 Fax: +1-615-287-8343 mailto:[EMAIL PROTECTED] http://www.franke.com -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: reloadable=true in 4.01
Hi, It's working :) The only thing you should check is that your classes are in the directory myApp/WEB-INF/classes this is the only place TC looks for changed files. Amine - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, January 04, 2002 4:25 PM Subject: reloadable=true in 4.01 Hi guys, After looking at the examples context in server.xml and reading this, I have tried the following config. Context path=/myApp docBase=myApp debug=0 privileged=true reloadable=true / This is supposed to reload a servlet if the file has changed. Currently, the page never loads when I change the class file after Tomcat has started and loaded the first version of the class. When I first tried to get this going a week ago or so, I got a null pointer exception. Although, I don't have the actual exception to paste at this time unfortunately. This is with Tomcat 4.01. Does anyone have this working? I did not see this question in the archives of this mailing list so I assume it works for most people since this is probably the first thing anyone does when setting up Tomcat during the development phase. :-) Thanks, __ Joseph Chandler Software Engineer Franke Holding USA 305 Tech Park Drive La Vergne, TN 37086 USA Switchboard: +1-615-287-8243 Fax: +1-615-287-8343 mailto:[EMAIL PROTECTED] http://www.franke.com -- 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, ok...but...
(i'm talking about re-deploying a WAR file without stopping Tomcat) how does this option affect to tomcat's efficiency? ...because i supose this option force Tomcat to check often its 'webapp' directory in order to look for new files. Regards: __ Jaume Soriano Sivera [EMAIL PROTECTED] Tel: 96504 -ext. 44744 Fax: 965040047 Portal y servicios multimedia - Nuevas tecnologias W a n a d o o E s p a n a - http://www.wanadoo.es __
