tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 35573] New: - Virtual servers should be identified by ID not server name
Date Fri, 01 Jul 2005 05:28:39 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=35573>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=35573

           Summary: Virtual servers should be identified by ID not server
                    name
           Product: Tomcat 5
           Version: 5.5.9
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Unknown
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: bht@actrix.gen.nz


There is an urgent need to identify virtual servers within Tomcat by an ID or
zone name and not by server name.

The scenario is multiple virtual servers and mod_jk with Apache httpd.

The reason for the request is as follows:

A virtual server might need to have its name changed.
In that case, with the current state of affairs the following changes
would have to be performed:

1) In Apache httpd.conf, change the server name.
2) In Apache httpd.conf, change the server name aliases.
3) In Tomcat server.xml, change the the name attribute in the <Host element.
4) In Tomcat server.xml, change the the server name aliases.
5) In Tomcat, in conf/Catalina, change the name of the directory with the name
of the server.
6) Stop Apache httpd.
7) Re-start Tomcat.
8) Start Apache httpd.

These steps are by far too many.

In comparison, when a server entity is referenced by an ID, such as a servlet
zone, then only the following steps are required to change the server names and
aliases:

1) In Apache httpd.conf, change the server name.
2) In Apache httpd.conf, change the server name aliases.
3) Re-start Apache httpd.


As can be seen here, with a servlet zone based scheme, a server name change does
NOT require a Tomcat re-start because the zone name remains unchanged.

This is because the connector responds to the servlet zone name and Tomcat is
freed from having to duplicate the server alias lookup of Apache httpd.

As is obvious from the steps in the current state of affairs, that a lot of
duplication has to be painfully maintained both in Apache httpd and Tomcat
configuration files.

jserv, the predecessor of Tomcat, employed a servlet zone based scheme as
suggested and did not require a re-start on a change of server name.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


Mime
View raw message