You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2008/04/01 13:22:50 UTC
DO NOT REPLY [Bug 44725] New: Tomcat delete context.xml and web.
xml if re-naming Folders in CONF
https://issues.apache.org/bugzilla/show_bug.cgi?id=44725
Summary: Tomcat delete context.xml and web.xml if re-naming
Folders in CONF
Product: Tomcat 6
Version: 6.0.16
Platform: PC
OS/Version: Windows Server 2003
Status: NEW
Severity: critical
Priority: P2
Component: Catalina
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: alexanderdiedler@gmx.de
CC: alexanderdiedler@gmx.de
Hello,
Very critical things happens in Tomcat.
If anybody rename a Appliaction Website Folder (e.g./conf/www.testsite.de ->
/conf/www.testsite2.com) in [tomcat_home]/conf and try again to open the Site
on a Browser (you see a blank site without Errormessages), Tomcat delete
automatically the web.xml and context.xml.
I found this in Version 6.0.14 and 6.0.16
Greetings
Alexander Diedler
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
DO NOT REPLY [Bug 44725] Tomcat delete context.xml and web.xml if
re-naming Folders in CONF
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=44725
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |INVALID
--- Comment #6 from Mark Thomas <ma...@apache.org> 2010-04-24 19:19:50 EDT ---
The behaviour if you delete a context.xml is documented here:
http://tomcat.apache.org/tomcat-6.0-doc/config/host.html#Automatic%20Application%20Deployment
The docs seem clear on this to me but if you think there is room for
improvement, patches are always welcome (please open a new issue & mark it as
an enhancement).
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
DO NOT REPLY [Bug 44725] Tomcat delete context.xml and web.xml if
re-naming Folders in CONF
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=44725
--- Comment #5 from Pid <bu...@pidster.com> 2010-04-24 15:38:49 EDT ---
The original bug refers to a situation where a user renamed a critical
directory location while the server was running. Tomcat interpreted this as an
instruction to undeploy all of the webapps for that host.
An exploded webapp directory can be completely deleted during undeployment,
config files included.
I think the second complaint misunderstands the nature of a Servlet based web
application, some configuration is completely self contained and must be
replaced - renaming & leaving files in place would prevent the directory being
deleted. Renaming the directory would cause another deployment under the new
name.
Godmar:
Ask on the Users list if you are having problems updating your application,
I'll assist.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
DO NOT REPLY [Bug 44725] Tomcat delete context.xml and web.xml if
re-naming Folders in CONF
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=44725
godmar <go...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |
--- Comment #4 from godmar <go...@gmail.com> 2010-04-24 13:25:47 EDT ---
I just got bitten by this as well.
I wondered why Tomcat (even after restarting the entire server!!!) didn't pick
up changes I had made to my /webappname/META-INF/context.xml file, until I
discovered via grep -r the cached version of that file in
conf/Catalina/localhost/webappname.xml. I deleted webappname.xml in an attempt
to force Tomcat to pick up the updated version of context.xml.
In retaliation, Tomcat deletes my web.xml file. Fortunately, we were able to
restore from CVS.
Filing this as INVALID shows a disturbing attitude on the part of the Tomcat
developers. Please understand that we don't have the time to analyze the Tomcat
code base for whatever behavior you've programmed into it. We rely on the
documentation, and we rely on the assumption that Tomcat shows sensible
behavior if in doubt.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
DO NOT REPLY [Bug 44725] Tomcat delete context.xml and web.
xml if re-naming Folders in CONF
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=44725
Andreas Sahlbach <an...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |
--- Comment #2 from Andreas Sahlbach <an...@gmail.com> 2008-05-22 03:37:01 PST ---
IMHO this is still a bug.
A server should _never_ever_ delete any kind of configuration file. Disable it
somehow, move it somewhere else, rename it, whatever. But don't dare to delete
it. This configuration file can contain very valuable configurations, even
secrets that can be hard to recover. Deleting it is simply wrong.
And please point me to the part of the documentation that describes this
dreaded behaviour so that I can turn it off.Thank you.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
DO NOT REPLY [Bug 44725] Tomcat delete context.xml and web.
xml if re-naming Folders in CONF
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=44725
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |INVALID
--- Comment #3 from Mark Thomas <ma...@apache.org> 2008-05-22 10:40:54 PST ---
The effects aren't documented for the simple reason that editing the
configuration directory structure (ie the engine name and host name) whilst
Tomcat is running isn't documented since it isn't supported.
I can't see any viable way of supporting such configuration changes whilst
Tomcat is running.
The docs you want are the host doc and the context docs. If you need more help,
please use the users list.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
DO NOT REPLY [Bug 44725] Tomcat delete context.xml and web.
xml if re-naming Folders in CONF
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=44725
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
--- Comment #1 from Mark Thomas <ma...@apache.org> 2008-04-01 11:47:52 PST ---
Only if you do this whilst Tomcat is running and only if Tomcat is configured
to monitor those configuration files for changes. It will probably (I haven't
tested it) be perceived as the removal of every webapp. This would certainly
explain what you see.
Tomcat does not support changing the name of a host in this way.
For a range of alternative approaches to achieve what you want to do, please
ask on the users list.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org