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 2004/02/05 06:58:02 UTC

DO NOT REPLY [Bug 26676] New: - Changes to server.xml irreversable

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26676>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26676

Changes to server.xml irreversable

           Summary: Changes to server.xml irreversable
           Product: Tomcat 5
           Version: 5.0.18
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: jrehman@citysearch.com


Tomcat 5 now explodes server.xml into a directory structure under
$CATALINA_HOME/conf. There is one XML fragment per context. This is desired
behavior if the documentation is to be believed. A typical directory structure
looks like: conf/Catalina/localhost/ with documents (admin.xml, balancer.xml,
manager.xml).

When a user adds a context to server.xml and restarts Tomcat, let's say
"my_context", this fragment too is added to the directory. All is well, the app
loads, etc. Now you remove the context from server.xml and restart Tomcat. The
fragment remains, and the app is still accessible.

This is undesirable behavior. All configuration changes should be reversable -
that is, as a rule, software shouldn't behave differently after making and then
unmaking a configuration change.

I have marked this bug as "major" because it has wasted my time and, from the
traffic on tomcat-user, many other people's time. While I understand the
justification for exploding server.xml, it seems like a poor implementation. At
the very least, there should be a big fat warning in server.xml explaining why
you should run "startup.sh -clear_config_cache" if you really want to work with
server.xml without worrying about config detritus. At most it would be best for
tomcat to clean up after itself when shutting down - e.g. delete the directories
it created.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org