Re: Tomcat Loads Deleted Context?
Remy Maucherat wrote: What I recommend with TC 5 is put your context declarations in /META-INF/context.xml, and use the manager to manage your webapps. If using external contexts, then it's the similar: either use the manager webapp or drop your context file in the right subdir of conf (and use the manager to undeploy). I've been playing with tomcat and the new way of doing things isn't all bad. In some ways its nice to have one file per context. Certainly its nice not having to restart tomcat for context changes. I still believe there is something to be said for everything in one place but for now I don't think this scheme is so bad as I did a few days ago. Could've been documented better but Yoav has addressed that to some degree. Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat Loads Deleted Context?
Howdy, Is META-INF/context.xml a standard way to provide a default context in a war? Or is it tomcat specific? It is tomcat-specific. Yoav Shapira 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: Tomcat Loads Deleted Context?
Shapira, Yoav ha scritto: Howdy, Is META-INF/context.xml a standard way to provide a default context in a war? Or is it tomcat specific? It is tomcat-specific. Yoav Shapira 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] But where is documented? How it run? How is possible change a context during the life of Tomcat? Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat Loads Deleted Context?
Hi, But where is documented? How it run? How is possible change a context during the life of Tomcat? http://jakarta.apache.org/tomcat/tomcat-5.0-doc/deployer-howto.html http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/host.html#Automat ic%20Application%20Deployment http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/context.html http://jakarta.apache.org/tomcat/tomcat-5.0-doc/manager-howto.html#Deplo y%20A%20New%20Application%20Remotely http://jakarta.apache.org/tomcat/faq/deployment.html Yoav Shapira 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: Tomcat Loads Deleted Context?
Howdy, Thanks. BTW, why can't server.xml be reloaded? Here's part of your commit: Because many of the components defined/declared in server.xml don't have restart support. There'd be significant code changes to support this. And the downtime would be equivalent to a normal server restart, so there's no advantage to reloading server.xml. note that directory is should be directly. It might also be clearer about *where* context elts should be placed. Corrected/enhanced, thanks. Again, I think this is a bad way to configure software. Everything in one place is the quite reasonable mantra espoused in _The Practical I agree: that one place for your web application is your WAR. It should be completely self-contained. I dislike putting anything in server.xml for my webapp. It's not server.xml for all your webapp. But obviously we disagree on that, and this is fine because tomcat is flexible enough to support either way. Perhaps there is some technical limitation to reloading server.xml. but I can't see it. Remy has said it's a hack but of course that doesn't really say anything. You are just trading one hierarchical data structure for another (directories for nested XML elts). No, you're doing a lot more. (I am looking into this but I can't get tomcat built, and no-one on the dev list has replied to my build questions yet. When I have more time tonight I'll try again.) Building tomcat 5 is trivial. Just checkout the source and run the ant file (default target). It will download all dependencies and build everything for you. I do it routinely from a scratch, completely clean environment, without any problems (it takes about 3-4 minutes on my box). If you have problems post them here (in another thread). Yoav Shapira 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: Tomcat Loads Deleted Context?
Thanks a bunch for the response. Comments below. Shapira, Yoav wrote: Howdy, Thanks. BTW, why can't server.xml be reloaded? Here's part of your commit: Because many of the components defined/declared in server.xml don't have restart support. There'd be significant code changes to support this. And the downtime would be equivalent to a normal server restart, so there's no advantage to reloading server.xml. I would not expect that all parts of server.xml be restartable, just the Contexts. note that directory is should be directly. It might also be clearer about *where* context elts should be placed. Corrected/enhanced, thanks. Glad to help! Again, I think this is a bad way to configure software. Everything in one place is the quite reasonable mantra espoused in _The Practical I agree: that one place for your web application is your WAR. It should be completely self-contained. I dislike putting anything in server.xml for my webapp. It's not server.xml for all your webapp. But obviously we disagree on that, and this is fine because tomcat is flexible enough to support either way. Is META-INF/context.xml a standard way to provide a default context in a war? Or is it tomcat specific? Perhaps there is some technical limitation to reloading server.xml. but I can't see it. Remy has said it's a hack but of course that doesn't really say anything. You are just trading one hierarchical data structure for another (directories for nested XML elts). No, you're doing a lot more. (I am looking into this but I can't get tomcat built, and no-one on the dev list has replied to my build questions yet. When I have more time tonight I'll try again.) Building tomcat 5 is trivial. Just checkout the source and run the ant file (default target). It will download all dependencies and build everything for you. I do it routinely from a scratch, completely clean environment, without any problems (it takes about 3-4 minutes on my box). If you have problems post them here (in another thread). I won't bother posting in another thread; essentially, I set base.path to a relative directory, and the build broke rather badly. That script is really cool otherwise. Yoav Shapira 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. Is this for real? :) Cheers, Josh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Loads Deleted Context?
Josh Rehman wrote: Amen to that brother. I wasted a lot of time having an old context load up on me with TC5 when I had removed it from server.xml. Very, very bad idea tomcat developers! Glad you like it :) BTW, it's not going to change. Just stop using server.xml for your context declarations and you'll be fine. Note that they *can't* delete that directory because you might have modified something by hand, and presumably that would be even worse. (Of course, you could check to see if anything had changed before deleting, this safer deletion is possible.) Bottom line is that any piece of server software should have reversable behavior - if I make a change to a config file, and change it back, then the server should act the same way before the change was made at all. Tomcat doesn't do this, and that's very bad. Now, if I am wrong about this, please correct me. I'm all ears! -- x Rémy Maucherat Developer Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Loads Deleted Context?
Josh Rehman wrote: This TC5 feature concerns me so much I've written up a bug. Please feel free to comment on it and/or vote for it. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26676 It's closed now ;) -- x Rémy Maucherat Developer Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Loads Deleted Context?
Remy Maucherat wrote: Josh Rehman wrote: This TC5 feature concerns me so much I've written up a bug. Please feel free to comment on it and/or vote for it. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26676 It's closed now ;) Well, that's a quick response, although not the one I had hoped for. This is obviously a problem, and deserves more attention than a quick closure. If 3 people here have the problem, then at least 100 people out there have the problem, and haven't bothered to say anything about it. This is especially true for those coming from 4.x where this did not happen. There is certainly nothing in the documentation warning against Context modifications in server.xml. Indeed, even if there was that would be a bad idea. Apache works that way, and people are used to it. Why not just have Tomcat reload server.xml if you want to support context parm changes without a restart? That would be a great feature! If the concern is reloading in the middle of an incomplete edit, there are ways around that. And besides, that would seem to be a problem no matter what. Come to think of it, I don't see why you can't reload server.xml. You write in the bug: You are not supposed to add Context declarations to server.xml, because the contexts then become impossile to manage. This works as designed, but it is obviously different from Tomcat 4.1.x. How exactly do Contexts become impossible to manage? They seemed to work fine under all previous versions of Tomcat. Josh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Loads Deleted Context?
Remy Maucherat wrote: Josh Rehman wrote: Amen to that brother. I wasted a lot of time having an old context load up on me with TC5 when I had removed it from server.xml. Very, very bad idea tomcat developers! Glad you like it :) BTW, it's not going to change. Just stop using server.xml for your context declarations and you'll be fine. If you're really in love with this idea, then why not, at the very least, comment out the server.xml Context for the poor, unsuspecting users, and include a note saying, By the way, you shouldn't edit contexts here. Edit them at x/y/z/mycontext.xml. Then at least people will be merely annoyed rather than actively frustrated trying to figure out why their contexts aren't going away. Just a suggestion. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Loads Deleted Context?
Josh Rehman wrote: Remy Maucherat wrote: Josh Rehman wrote: This TC5 feature concerns me so much I've written up a bug. Please feel free to comment on it and/or vote for it. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26676 It's closed now ;) Well, that's a quick response, although not the one I had hoped for. This is obviously a problem, and deserves more attention than a quick closure. If 3 people here have the problem, then at least 100 people out there have the problem, and haven't bothered to say anything about it. This is especially true for those coming from 4.x where this did not happen. There is certainly nothing in the documentation warning against Context modifications in server.xml. Indeed, even if there was that would be a bad idea. Apache works that way, and people are used to it. Why not just have Tomcat reload server.xml if you want to support context parm changes without a restart? That would be a great feature! If the concern is reloading in the middle of an incomplete edit, there are ways around that. And besides, that would seem to be a problem no matter what. Come to think of it, I don't see why you can't reload server.xml. Basically, it would be the same as restarting the whole server (with the gain of the VM startup time). So it's not useful. You write in the bug: You are not supposed to add Context declarations to server.xml, because the contexts then become impossile to manage. This works as designed, but it is obviously different from Tomcat 4.1.x. How exactly do Contexts become impossible to manage? They seemed to work fine under all previous versions of Tomcat. Ex: - you want the container to undeploy dynamically a context - you want to update stuff in your context element dynamically Saving the whole server.xml for these cases is error prone, and basically a big hack. What I recommend with TC 5 is put your context declarations in /META-INF/context.xml, and use the manager to manage your webapps. If using external contexts, then it's the similar: either use the manager webapp or drop your context file in the right subdir of conf (and use the manager to undeploy). -- x Rémy Maucherat Developer Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Loads Deleted Context?
Remy Maucherat wrote, On 2/5/2004 1:32 AM: What I recommend with TC 5 is put your context declarations in /META-INF/context.xml, and use the manager to manage your webapps. If using external contexts, then it's the similar: either use the manager webapp or drop your context file in the right subdir of conf (and use the manager to undeploy). Remy, this sums up how users are expected to manage contexts with TC5 quite nicely. Can you stick this comment in the server.xml so that unsuspecting users upgrading from TC4 aren't caught off guard by this? I briefly looked through the TC5 docs on the site and couldn't find any reference to this change in behavior there, either. IMO, this change is is very important and should be noted somewhere prominent as a TC4-TC5 upgrade note/gotcha. It had me baffled for a while, too, now I modified my startup script to `rm -rf conf/Catalina` every time so I don't get caught with any webapps I forgot about as I am used to doing all my context management through the conf/server.xml. This and the change in web-app reloading now causes requests to fail in between the shutdown-startup phase instead of blocking are two significant non-obvious changes in behavior of managing a TC server between TC4/5. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Loads Deleted Context?
On Thu, 5 Feb 2004, Josh Rehman wrote: Remy Maucherat wrote: Josh Rehman wrote: Amen to that brother. I wasted a lot of time having an old context load up on me with TC5 when I had removed it from server.xml. Very, very bad idea tomcat developers! Glad you like it :) BTW, it's not going to change. Just stop using server.xml for your context declarations and you'll be fine. If you're really in love with this idea, then why not, at the very least, comment out the server.xml Context for the poor, unsuspecting FWIW, the Context tag in the distributed server.xml is commented out. users, and include a note saying, By the way, you shouldn't edit contexts here. Edit them at x/y/z/mycontext.xml. Then at least people will be merely annoyed rather than actively frustrated trying to figure out why their contexts aren't going away. Just a suggestion. And a good one. I don't think Remy's suggestion above is unreasonable -- AS LONG AS IT'S DOCUMENTED (sorry for shouting). Especially if it's as simple as adding a few lines in server.xml. (Well, it would be nice if it were added to the server configuration documentation as well.) Milt Epstein Research Programmer Integration and Software Engineering (ISE) Campus Information Technologies and Educational Services (CITES) University of Illinois at Urbana-Champaign (UIUC) [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat Loads Deleted Context?
Howdy, I've created a FAQ item for this, in its own FAQ page (Deployment, under http://jakarta.apache.org/tomcat/faq), where I expect to add more content -- suggestions welcome. Yoav Shapira Millennium ChemInformatics -Original Message- From: David Rees [mailto:[EMAIL PROTECTED] Sent: Thursday, February 05, 2004 4:48 AM To: Tomcat Users List Subject: Re: Tomcat Loads Deleted Context? Remy Maucherat wrote, On 2/5/2004 1:32 AM: What I recommend with TC 5 is put your context declarations in /META-INF/context.xml, and use the manager to manage your webapps. If using external contexts, then it's the similar: either use the manager webapp or drop your context file in the right subdir of conf (and use the manager to undeploy). Remy, this sums up how users are expected to manage contexts with TC5 quite nicely. Can you stick this comment in the server.xml so that unsuspecting users upgrading from TC4 aren't caught off guard by this? I briefly looked through the TC5 docs on the site and couldn't find any reference to this change in behavior there, either. IMO, this change is is very important and should be noted somewhere prominent as a TC4-TC5 upgrade note/gotcha. It had me baffled for a while, too, now I modified my startup script to `rm -rf conf/Catalina` every time so I don't get caught with any webapps I forgot about as I am used to doing all my context management through the conf/server.xml. This and the change in web-app reloading now causes requests to fail in between the shutdown-startup phase instead of blocking are two significant non-obvious changes in behavior of managing a TC server between TC4/5. -Dave - 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: Tomcat Loads Deleted Context?
Howdy, I don't think Remy's suggestion above is unreasonable -- AS LONG AS IT'S DOCUMENTED (sorry for shouting). Especially if it's as simple as adding a few lines in server.xml. (Well, it would be nice if it were added to the server configuration documentation as well.) Added to Context configuration documentation. Added to Tomcat FAQ (deployment page). And Remy just beat me to removing the Context example altogether (as opposed to commenting it out as it has been) from server.xml. Yoav Shapira 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: Tomcat Loads Deleted Context?
Shapira, Yoav wrote: Howdy, I don't think Remy's suggestion above is unreasonable -- AS LONG AS IT'S DOCUMENTED (sorry for shouting). Especially if it's as simple as adding a few lines in server.xml. (Well, it would be nice if it were added to the server configuration documentation as well.) Added to Context configuration documentation. Added to Tomcat FAQ (deployment page). And Remy just beat me to removing the Context example altogether (as opposed to commenting it out as it has been) from server.xml. Thanks. BTW, why can't server.xml be reloaded? Here's part of your commit: pYou may define as many strongContext/strong elements as you - wish, nested within a a href=host.htmlHost/a element in - codeconf/server.xml/code. Each such Context MUST have a unique + wish. Each such Context MUST have a unique context path, which is defined by the codepath/code attribute. In addition, you MUST define a Context with a context path equal to a zero-length string. This Context becomes the emdefault/em @@ -53,7 +52,9 @@ Application Deployment/a for more information. This method allows dynamic reconfiguration of the web application, since the main codeconf/server.xml/code file cannot be reloaded without restarting - Tomcat./p + Tomcat. bPlease note that for tomcat 5.x, unlike tomcat 4.x, it is NOT + recommended to place Context elements directory in the server.xml file./b + /p note that directory is should be directly. It might also be clearer about *where* context elts should be placed. Again, I think this is a bad way to configure software. Everything in one place is the quite reasonable mantra espoused in _The Practical Programmer_ among other places, not to mention I've had success with it as a rule of thumb. Logically, I want to see all contexts in one place. Moving that responsibility to the manager app doesn't count as one place because then I have to be pointing and clicking everywhere. I should be able to use vi to manage my server with one file. The apache web server has been doing it this way for a long, long time and it seems to work pretty well. I work alongside Perl and Apache folk, and I can hear their sniggers when I tell them I have to navigate a directory tree to modify a context...and they'd be right! Perhaps there is some technical limitation to reloading server.xml. but I can't see it. Remy has said it's a hack but of course that doesn't really say anything. You are just trading one hierarchical data structure for another (directories for nested XML elts). (I am looking into this but I can't get tomcat built, and no-one on the dev list has replied to my build questions yet. When I have more time tonight I'll try again.) Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat Loads Deleted Context?
Hi, I am having a weird problem. It seems that Tomcat is trying to deploy a
deleted project. The deleted project was outside of ${tomcat_home}/ dir. And I
already I commented out the context for that project. I also deleted the
work/ dir, but the problem persists. The generated
/work/Catalina/localhost/deleted/ dir doesn't have any class files except
SESSIONS.ser and tldCache.ser. I suspect tomcat is installing web applications
based on some sort of cache.
Here is the console output when deploying tomcat:
Feb 4, 2004 8:14:19 AM org.apache.catalina.core.StandardHostDeployer install
INFO: Processing Context configuration file URL
file:C:\Web\ApacheGroup\Tomcat\conf\Catalina\localhost\deleted.xml
log4j:WARN No appenders could be found for logger
(org.apache.commons.digester.Digester).
log4j:WARN Please initialize the log4j system properly.
I was wondering if this is a bug? I am using tomcat-5.0.18.
Thanks!
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Loads Deleted Context?
On Wed, 4 Feb 2004, Yansheng Lin wrote:
Hi, I am having a weird problem. It seems that Tomcat is trying to
deploy a deleted project. The deleted project was outside of
${tomcat_home}/ dir. And I already I commented out the context
for that project. I also deleted the work/ dir, but the problem
persists. The generated /work/Catalina/localhost/deleted/ dir
doesn't have any class files except SESSIONS.ser and tldCache.ser. I
suspect tomcat is installing web applications based on some sort of
cache.
What do you mean by commented out the context for that project?
Where/in what file did you do that?
Here is the console output when deploying tomcat:
Feb 4, 2004 8:14:19 AM org.apache.catalina.core.StandardHostDeployer install
INFO: Processing Context configuration file URL
file:C:\Web\ApacheGroup\Tomcat\conf\Catalina\localhost\deleted.xml
Does this file still exist? If so, that could be your problem. (That
is the context configuration file for the deleted webapp.)
(deleted is the name of your webapp? Or did you just fill that in
as a placeholder?)
log4j:WARN No appenders could be found for logger
(org.apache.commons.digester.Digester).
log4j:WARN Please initialize the log4j system properly.
I was wondering if this is a bug? I am using tomcat-5.0.18.
Thanks!
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Milt Epstein
Research Programmer
Integration and Software Engineering (ISE)
Campus Information Technologies and Educational Services (CITES)
University of Illinois at Urbana-Champaign (UIUC)
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Loads Deleted Context?
delete the context file (if present) from
$TOMCAT_HOME/conf/{ENGINE}/{HOST}/
On Wed, 4 Feb 2004 10:39:30 -0600 (CST)
Milt Epstein [EMAIL PROTECTED] wrote:
On Wed, 4 Feb 2004, Yansheng Lin wrote:
Hi, I am having a weird problem. It seems that Tomcat is trying to
deploy a deleted project. The deleted project was outside of
${tomcat_home}/ dir. And I already I commented out the context
for that project. I also deleted the work/ dir, but the problem
persists. The generated /work/Catalina/localhost/deleted/ dir
doesn't have any class files except SESSIONS.ser and tldCache.ser. I
suspect tomcat is installing web applications based on some sort of
cache.
What do you mean by commented out the context for that project?
Where/in what file did you do that?
Here is the console output when deploying tomcat:
Feb 4, 2004 8:14:19 AM org.apache.catalina.core.StandardHostDeployer
install INFO: Processing Context configuration file URL
file:C:\Web\ApacheGroup\Tomcat\conf\Catalina\localhost\deleted.xml
Does this file still exist? If so, that could be your problem. (That
is the context configuration file for the deleted webapp.)
(deleted is the name of your webapp? Or did you just fill that in
as a placeholder?)
log4j:WARN No appenders could be found for logger
(org.apache.commons.digester.Digester).
log4j:WARN Please initialize the log4j system properly.
I was wondering if this is a bug? I am using tomcat-5.0.18.
Thanks!
---
-- To unsubscribe, e-mail:
[EMAIL PROTECTED] For additional commands,
e-mail: [EMAIL PROTECTED]
Milt Epstein
Research Programmer
Integration and Software Engineering (ISE)
Campus Information Technologies and Educational Services (CITES)
University of Illinois at Urbana-Champaign (UIUC)
[EMAIL PROTECTED]
-
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: Tomcat Loads Deleted Context?
Yes, that context descriptor(deleted.xml) still exists under that directory!!! And after deleting it, tomcat doesn't load the particular webapp anymore. But I still think this is a possible bug. Since the expected behaviour is not to load anything anymore for a deleted webapp. I removed the Context for that webapp in conf/server.xml. And the deleted project directory is located outside of TOMCAT default webapps/ dir... . Thanks! -Original Message- From: Milt Epstein [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 04, 2004 9:40 AM To: Tomcat Users List Subject: Re: Tomcat Loads Deleted Context? Here is the console output when deploying tomcat: Feb 4, 2004 8:14:19 AM org.apache.catalina.core.StandardHostDeployer install INFO: Processing Context configuration file URL file:C:\Web\ApacheGroup\Tomcat\conf\Catalina\localhost\deleted.xml Does this file still exist? If so, that could be your problem. (That is the context configuration file for the deleted webapp.) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat Loads Deleted Context?
On Wed, 4 Feb 2004, Yansheng Lin wrote: Yes, that context descriptor(deleted.xml) still exists under that directory!!! And after deleting it, tomcat doesn't load the particular webapp anymore. But I still think this is a possible bug. Since the expected behaviour is not to load anything anymore for a deleted webapp. Yes, but the question is, what constitutes a webapp being deleted? And the answer, I think, depends on how you have Tomcat configured (e.g., in terms of auto-deployment of webapps). I'd say that if you're using a context configuration file, that's part of the webapp. And if you haven't deleted it, you haven't really deleted the webapp. I removed the Context for that webapp in conf/server.xml. Hmmm -- you had a Context element for this webapp in server.xml *and* a separate context configuration file? That's redundant, because they serve the same purpose. I'm not sure what would happen in that case -- were you per chance seeing your webapp starting up twice? And the deleted project directory is located outside of TOMCAT default webapps/ dir... . Which means there has to be some element inside Tomcat's configuration (either in server.xml or a separate context configuration file) that lets Tomcat know about it. And until you delete that element, you haven't deleted the webapp. That's my take on it, at least :-). -Original Message- From: Milt Epstein [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 04, 2004 9:40 AM To: Tomcat Users List Subject: Re: Tomcat Loads Deleted Context? Here is the console output when deploying tomcat: Feb 4, 2004 8:14:19 AM org.apache.catalina.core.StandardHostDeployer install INFO: Processing Context configuration file URL file:C:\Web\ApacheGroup\Tomcat\conf\Catalina\localhost\deleted.xml Does this file still exist? If so, that could be your problem. (That is the context configuration file for the deleted webapp.) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Milt Epstein Research Programmer Integration and Software Engineering (ISE) Campus Information Technologies and Educational Services (CITES) University of Illinois at Urbana-Champaign (UIUC) [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat Loads Deleted Context?
Hi, No, I didn't create the context configuration file under /conf/[enginename]/[hostname]/. It was created by Tomcat on the fly. And my webapp wasn't starting up twice, which is good. Also I can delete that dir, but it would be recreated next time when I restart Tomcat5. I think the confusion lies on whether it's user's responsibily or the container's to clean up the configuration file after user deleting a context element in server.xml. In tomcat user-guide: http://jakarta.apache.org/tomcat/tomcat-5.0-doc/deployer-howto.html, there is nothing about when a context descriptor is created, and what happens if you decide to delete a context in your server.xml. It would be nice if the container refreshes that directory/recreates all the context descriptors when server.xml is modified. But maybe there is some other setting I don't know of in 5. I didnt' have this problem with tomcat 4 before. Thanks! -Yan -Original Message- From: Milt Epstein [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 04, 2004 12:12 PM To: Tomcat Users List Subject: RE: Tomcat Loads Deleted Context? I removed the Context for that webapp in conf/server.xml. Hmmm -- you had a Context element for this webapp in server.xml *and* a separate context configuration file? That's redundant, because they serve the same purpose. I'm not sure what would happen in that case -- were you per chance seeing your webapp starting up twice? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat Loads Deleted Context?
Howdy, This is new functionality to tomcat5. Senor Epstein's description of what constitutes a deleted webapp is accurate and well-written. If you happen to think tomcat should refresh its conf directory periodically or upon some trigger, please feel free to contribute a patch ;) Yoav Shapira Millennium ChemInformatics -Original Message- From: Yansheng Lin [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 04, 2004 3:20 PM To: 'Tomcat Users List' Subject: RE: Tomcat Loads Deleted Context? Hi, No, I didn't create the context configuration file under /conf/[enginename]/[hostname]/. It was created by Tomcat on the fly. And my webapp wasn't starting up twice, which is good. Also I can delete that dir, but it would be recreated next time when I restart Tomcat5. I think the confusion lies on whether it's user's responsibily or the container's to clean up the configuration file after user deleting a context element in server.xml. In tomcat user-guide: http://jakarta.apache.org/tomcat/tomcat-5.0-doc/deployer-howto.html, there is nothing about when a context descriptor is created, and what happens if you decide to delete a context in your server.xml. It would be nice if the container refreshes that directory/recreates all the context descriptors when server.xml is modified. But maybe there is some other setting I don't know of in 5. I didnt' have this problem with tomcat 4 before. Thanks! -Yan -Original Message- From: Milt Epstein [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 04, 2004 12:12 PM To: Tomcat Users List Subject: RE: Tomcat Loads Deleted Context? I removed the Context for that webapp in conf/server.xml. Hmmm -- you had a Context element for this webapp in server.xml *and* a separate context configuration file? That's redundant, because they serve the same purpose. I'm not sure what would happen in that case -- were you per chance seeing your webapp starting up twice? - 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: Tomcat Loads Deleted Context?
Hi, Where can I find the Senor Epstein's description of what constitutes a deleted webapp? I looked everywhere I remembered and I could not find. Thanks in advance, Hernani -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: quarta-feira, 4 de Fevereiro de 2004 20:47 To: Tomcat Users List Subject: RE: Tomcat Loads Deleted Context? Howdy, This is new functionality to tomcat5. Senor Epstein's description of what constitutes a deleted webapp is accurate and well-written. If you happen to think tomcat should refresh its conf directory periodically or upon some trigger, please feel free to contribute a patch ;) Yoav Shapira Millennium ChemInformatics -Original Message- From: Yansheng Lin [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 04, 2004 3:20 PM To: 'Tomcat Users List' Subject: RE: Tomcat Loads Deleted Context? Hi, No, I didn't create the context configuration file under /conf/[enginename]/[hostname]/. It was created by Tomcat on the fly. And my webapp wasn't starting up twice, which is good. Also I can delete that dir, but it would be recreated next time when I restart Tomcat5. I think the confusion lies on whether it's user's responsibily or the container's to clean up the configuration file after user deleting a context element in server.xml. In tomcat user-guide: http://jakarta.apache.org/tomcat/tomcat-5.0-doc/deployer-howto.html, there is nothing about when a context descriptor is created, and what happens if you decide to delete a context in your server.xml. It would be nice if the container refreshes that directory/recreates all the context descriptors when server.xml is modified. But maybe there is some other setting I don't know of in 5. I didnt' have this problem with tomcat 4 before. Thanks! -Yan -Original Message- From: Milt Epstein [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 04, 2004 12:12 PM To: Tomcat Users List Subject: RE: Tomcat Loads Deleted Context? I removed the Context for that webapp in conf/server.xml. Hmmm -- you had a Context element for this webapp in server.xml *and* a separate context configuration file? That's redundant, because they serve the same purpose. I'm not sure what would happen in that case -- were you per chance seeing your webapp starting up twice? - 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: Tomcat Loads Deleted Context?
On Wed, 4 Feb 2004, Yansheng Lin wrote: Hi, No, I didn't create the context configuration file under /conf/[enginename]/[hostname]/. It was created by Tomcat on the fly. Really?! I just tried this myself, and you're right, it does get created by Tomcat! That is, when I added a Context tag to server.xml for my webapp outside of Tomcat's webapps directory, Tomcat created a context configuration file for my webapp in conf/engine/host. And it stayed there after I deleted that Context tag from server.xml. I amend what I said before :-). And I agree with you -- it should be Tomcat's responsibility to delete the context configuration file it is creating. (What makes it even worse is that the context configuration file isn't even complete with what's included in the Context tag in server.xml.) And my webapp wasn't starting up twice, which is good. Also I can delete that dir, but it would be recreated next time when I restart Tomcat5. I think the confusion lies on whether it's user's responsibily or the container's to clean up the configuration file after user deleting a context element in server.xml. In tomcat user-guide: http://jakarta.apache.org/tomcat/tomcat-5.0-doc/deployer-howto.html, there is nothing about when a context descriptor is created, and what happens if you decide to delete a context in your server.xml. It would be nice if the container refreshes that directory/recreates all the context descriptors when server.xml is modified. But maybe there is some other setting I don't know of in 5. I didnt' have this problem with tomcat 4 before. Yes, it seems several things about the way this works have been changed from 4. (For example, the location of the context configuration files, and how they are managed, automatically created, modified, and/or deleted.) -Original Message- From: Milt Epstein [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 04, 2004 12:12 PM To: Tomcat Users List Subject: RE: Tomcat Loads Deleted Context? I removed the Context for that webapp in conf/server.xml. Hmmm -- you had a Context element for this webapp in server.xml *and* a separate context configuration file? That's redundant, because they serve the same purpose. I'm not sure what would happen in that case -- were you per chance seeing your webapp starting up twice? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Milt Epstein Research Programmer Integration and Software Engineering (ISE) Campus Information Technologies and Educational Services (CITES) University of Illinois at Urbana-Champaign (UIUC) [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat Loads Deleted Context?
On Wed, 4 Feb 2004, Shapira, Yoav wrote: Howdy, This is new functionality to tomcat5. Senor Epstein's description of what constitutes a deleted webapp is accurate and well-written. Well, in light of this new information, I've amended my description :-). I don't think it should be the user's responsibility to delete something that Tomcat creates (in this case at least). Tomcat is going through the trouble of creating it (and it's unclear why -- plus it's also undocumented), it should go through the trouble of cleaning it up. If you happen to think tomcat should refresh its conf directory periodically or upon some trigger, please feel free to contribute a patch ;) Obviously something is triggering Tomcat to create that configuration file, so it's not unreasonable to expect there to be a trigger for Tomcat to delete it (and most likely the inverse of the original trigger). As to contributing a patch -- well, I don't want to open up that Pandora's box :-). But most likely someone already has knowledge of how/why Tomcat is creating the configuration file, they're the most likely choice to look into this. Or at least offer some explanation of why it behaves this way and/or a pointer to the relevant section(s) of code. -Original Message- From: Yansheng Lin [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 04, 2004 3:20 PM To: 'Tomcat Users List' Subject: RE: Tomcat Loads Deleted Context? Hi, No, I didn't create the context configuration file under /conf/[enginename]/[hostname]/. It was created by Tomcat on the fly. And my webapp wasn't starting up twice, which is good. Also I can delete that dir, but it would be recreated next time when I restart Tomcat5. I think the confusion lies on whether it's user's responsibily or the container's to clean up the configuration file after user deleting a context element in server.xml. In tomcat user-guide: http://jakarta.apache.org/tomcat/tomcat-5.0-doc/deployer-howto.html, there is nothing about when a context descriptor is created, and what happens if you decide to delete a context in your server.xml. It would be nice if the container refreshes that directory/recreates all the context descriptors when server.xml is modified. But maybe there is some other setting I don't know of in 5. I didnt' have this problem with tomcat 4 before. Thanks! -Yan -Original Message- From: Milt Epstein [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 04, 2004 12:12 PM To: Tomcat Users List Subject: RE: Tomcat Loads Deleted Context? I removed the Context for that webapp in conf/server.xml. Hmmm -- you had a Context element for this webapp in server.xml *and* a separate context configuration file? That's redundant, because they serve the same purpose. I'm not sure what would happen in that case -- were you per chance seeing your webapp starting up twice? - 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] Milt Epstein Research Programmer Integration and Software Engineering (ISE) Campus Information Technologies and Educational Services (CITES) University of Illinois at Urbana-Champaign (UIUC) [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Loads Deleted Context?
Amen to that brother. I wasted a lot of time having an old context load up on me with TC5 when I had removed it from server.xml. Very, very bad idea tomcat developers! Note that they *can't* delete that directory because you might have modified something by hand, and presumably that would be even worse. (Of course, you could check to see if anything had changed before deleting, this safer deletion is possible.) Bottom line is that any piece of server software should have reversable behavior - if I make a change to a config file, and change it back, then the server should act the same way before the change was made at all. Tomcat doesn't do this, and that's very bad. Now, if I am wrong about this, please correct me. I'm all ears! Milt Epstein wrote: I amend what I said before . And I agree with you -- it should be Tomcat's responsibility to delete the context configuration file it is creating. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat Loads Deleted Context?
On Wed, 4 Feb 2004, Hernani Mourao wrote: Hi, Where can I find the Senor Epstein's description of what constitutes a deleted webapp? I looked everywhere I remembered and I could not find. I believe he's referring (somewhat facetiously :-) to what I wrote in an earlier post in this thread. To find it, you can check the list archives. There's one at http://marc.theaimsgroup.com/. -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: quarta-feira, 4 de Fevereiro de 2004 20:47 To: Tomcat Users List Subject: RE: Tomcat Loads Deleted Context? Howdy, This is new functionality to tomcat5. Senor Epstein's description of what constitutes a deleted webapp is accurate and well-written. If you happen to think tomcat should refresh its conf directory periodically or upon some trigger, please feel free to contribute a patch ;) Yoav Shapira Millennium ChemInformatics -Original Message- From: Yansheng Lin [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 04, 2004 3:20 PM To: 'Tomcat Users List' Subject: RE: Tomcat Loads Deleted Context? Hi, No, I didn't create the context configuration file under /conf/[enginename]/[hostname]/. It was created by Tomcat on the fly. And my webapp wasn't starting up twice, which is good. Also I can delete that dir, but it would be recreated next time when I restart Tomcat5. I think the confusion lies on whether it's user's responsibily or the container's to clean up the configuration file after user deleting a context element in server.xml. In tomcat user-guide: http://jakarta.apache.org/tomcat/tomcat-5.0-doc/deployer-howto.html, there is nothing about when a context descriptor is created, and what happens if you decide to delete a context in your server.xml. It would be nice if the container refreshes that directory/recreates all the context descriptors when server.xml is modified. But maybe there is some other setting I don't know of in 5. I didnt' have this problem with tomcat 4 before. Thanks! -Yan -Original Message- From: Milt Epstein [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 04, 2004 12:12 PM To: Tomcat Users List Subject: RE: Tomcat Loads Deleted Context? I removed the Context for that webapp in conf/server.xml. Hmmm -- you had a Context element for this webapp in server.xml *and* a separate context configuration file? That's redundant, because they serve the same purpose. I'm not sure what would happen in that case -- were you per chance seeing your webapp starting up twice? - 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] Milt Epstein Research Programmer Integration and Software Engineering (ISE) Campus Information Technologies and Educational Services (CITES) University of Illinois at Urbana-Champaign (UIUC) [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Loads Deleted Context?
This TC5 feature concerns me so much I've written up a bug. Please feel free to comment on it and/or vote for it. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26676 Milt Epstein wrote: On Wed, 4 Feb 2004, Hernani Mourao wrote: Hi, Where can I find the Senor Epstein's description of what constitutes a deleted webapp? I looked everywhere I remembered and I could not find. I believe he's referring (somewhat facetiously :-) to what I wrote in an earlier post in this thread. To find it, you can check the list archives. There's one at http://marc.theaimsgroup.com/. -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: quarta-feira, 4 de Fevereiro de 2004 20:47 To: Tomcat Users List Subject: RE: Tomcat Loads Deleted Context? Howdy, This is new functionality to tomcat5. Senor Epstein's description of what constitutes a deleted webapp is accurate and well-written. If you happen to think tomcat should refresh its conf directory periodically or upon some trigger, please feel free to contribute a patch ;) Yoav Shapira Millennium ChemInformatics -Original Message- From: Yansheng Lin [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 04, 2004 3:20 PM To: 'Tomcat Users List' Subject: RE: Tomcat Loads Deleted Context? Hi, No, I didn't create the context configuration file under /conf/[enginename]/[hostname]/. It was created by Tomcat on the fly. And my webapp wasn't starting up twice, which is good. Also I can delete that dir, but it would be recreated next time when I restart Tomcat5. I think the confusion lies on whether it's user's responsibily or the container's to clean up the configuration file after user deleting a context element in server.xml. In tomcat user-guide: http://jakarta.apache.org/tomcat/tomcat-5.0-doc/deployer-howto.html, there is nothing about when a context descriptor is created, and what happens if you decide to delete a context in your server.xml. It would be nice if the container refreshes that directory/recreates all the context descriptors when server.xml is modified. But maybe there is some other setting I don't know of in 5. I didnt' have this problem with tomcat 4 before. Thanks! -Yan -Original Message- From: Milt Epstein [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 04, 2004 12:12 PM To: Tomcat Users List Subject: RE: Tomcat Loads Deleted Context? I removed the Context for that webapp in conf/server.xml. Hmmm -- you had a Context element for this webapp in server.xml *and* a separate context configuration file? That's redundant, because they serve the same purpose. I'm not sure what would happen in that case -- were you per chance seeing your webapp starting up twice? - 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] Milt Epstein Research Programmer Integration and Software Engineering (ISE) Campus Information Technologies and Educational Services (CITES) University of Illinois at Urbana-Champaign (UIUC) [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks, Josh Rehman Citysearch Toolsdev, 3559 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
