You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Glenn Nielsen <gl...@mail.more.net> on 2003/09/07 06:37:06 UTC

jakarta-tomcat-connector release cleanup

I have promised to setup the tomcat connector releases so that they
can be mirrored when I perform the next mod_jk release.  First I have
a few questions.

Are the coyote beta release/milestone releases in
/www/jakarta.apache.org/builds/jakarta-tomcat-connectors/coyote
still needed?  Will there be separate releases of coyote or will
it only be bundled with Tomcat 4/5 releases?

mod_webapp is deprecated so should we continue to have the
/www/jakarta.apache.org/builds/jakarta-tomcat-connectors/webapp
release directory or should this be moved to archive.apache.org?

Can /www/jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/nightly/
be removed?  The last nightly build of this was October of 2002.

Can the old mod_jk 1.2 and mod_jk2 releases be moved to
archive.apache.org?

Thanks,

Glenn



Re: jakarta-tomcat-connector release cleanup

Posted by Bill Barker <wb...@wilshire.com>.
----- Original Message ----- 
From: "Glenn Nielsen" <gl...@mail.more.net>
To: <to...@jakarta.apache.org>
Sent: Saturday, September 06, 2003 9:37 PM
Subject: jakarta-tomcat-connector release cleanup


> I have promised to setup the tomcat connector releases so that they
> can be mirrored when I perform the next mod_jk release.  First I have
> a few questions.
>
> Are the coyote beta release/milestone releases in
> /www/jakarta.apache.org/builds/jakarta-tomcat-connectors/coyote
> still needed?  Will there be separate releases of coyote or will
> it only be bundled with Tomcat 4/5 releases?

Don't forget Tomcat 3.3!  The Tomcat 4/5 releases get issued pretty often,
and the current Connectors build is broken for 3.3, so +1 to remove the
Connectors download.  I'll look into transfering the "how-to-use"
instructions to the 3.3 nightly download page.

>
> mod_webapp is deprecated so should we continue to have the
> /www/jakarta.apache.org/builds/jakarta-tomcat-connectors/webapp
> release directory or should this be moved to archive.apache.org?

+1 for moving.  The fewer mod_webapp questions I have to field on
tomcat-user, the better ;-).

>
> Can /www/jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/nightly/
> be removed?  The last nightly build of this was October of 2002.
>
> Can the old mod_jk 1.2 and mod_jk2 releases be moved to
> archive.apache.org?

+1 for moving.

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


Virtual hosts and multiple Tomcat instances

Posted by Thomas Eichberger <th...@gmx.net>.
Hi,

please excuse that I ask my question on this list here, but on tomcat-users 
I didn't get a reply (maybe too difficult).



I have Apache 1.3 and Tomcat 4.1.8 on a Red Hat 9 machine.

Apache serves several virutal hosts. We have one Tomcat instance running 
with several web contexts, one context for each virtual host.

Now I would like to change this to have one Tomcat instance for each 
virtual host (this is necessary because Tomcat sometimes crashes, and I 
don't want all virtual hosts to be down then).

I read a book about Tomcat and searched the Web, but could not find out how 
to do this. What I assume is:


In Apache's httpd.conf I have something (after the import of mod_jk):

NameVirtualHost 200.200.200.200 (or whatever)

<VirtualHost 200.200.200.200>
ServerName www.xxx.com
DocumentRoot /tomcat1/webapps/xxx
JkMount /servlet/* worker1
JkMount /*.jsp worker1
JkMount /*.do worker1
</VirtualHost>

<VirtualHost 200.200.200.200>
ServerName www.yyy.com
DocumentRoot /tomcat2/webapps/yyy
JkMount /servlet/* worker2
JkMount /*.jsp worker2
JkMount /*.do worker2
</VirtualHost>


Then I will install Tomcat two times, in /tomcat1 and /tomcat2.

The server.xml of each Tomcat contains different ports (for shutdown and 
for the connector for ajp13).


The workers.properties should look like:

worker.list=worker1,worker2
...
worker.worker1.port=8009
worker.worker1.host=localhost
worker.worker1.type=ajp13
...
worker.worker1.port=8010
worker.worker1.host=localhost
worker.worker1.type=ajp13


Is this all correct? Should that work?

Thomas