You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by "Robert P. J. Day" <rp...@crashcourse.ca> on 2011/03/31 14:51:31 UTC
what exactly does it mean to run multiple tomcat "instances"?
reading the snippet from RUNNING.txt and i think something needs to
be clarified.
i can see how multiple users could share a common CATALINA_HOME
directory, whose only common contents would be the bin/ and lib/
directories. but how would individual users take advantage of that?
if i create a personal CATALINA_BASE directory, and someone else has
already started tomcat listening on port 8080, then i certainly can't
start another one on that same port with the startup.sh script -- i
tried that and quite predictably got an error that port 8080 was
already in use. and if i change that server port to, say, 8081, i'm
just going to run into another conflict on port 8009.
so if i want to run an entirely separate tomcat instance, don't i
have to modify server.xml, at least to the extent that it doesn't
conflict with any other running instances in terms of ports? and if
so, shouldn't that be mentioned in RUNNING.txt? (unless it's spelled
out in more detail elsewhere.)
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: what exactly does it mean to run multiple tomcat "instances"?
Posted by "Robert P. J. Day" <rp...@crashcourse.ca>.
On Fri, 1 Apr 2011, Christopher Schultz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Robert,
>
> On 4/1/2011 1:13 PM, Robert P. J. Day wrote:
> > On Thu, 31 Mar 2011, Christopher Schultz wrote:
> >> So... it specifically tells you that it will use your own
> >> conf/server.xml file. Would you like an additional reinforcing statement?
> >
> > Why, yes, thanks for asking so politely. :-) because if you read
> > further down in that RUNNING.txt file, you see:
> >
> > [snip]
> >
> > now correct me if i'm wrong, but since we just established that you
> > need to reassign more than just the main (8080) server port, to then
> > subsequently claim that all you need to do to avoid a conflict is to
> > reassign the main (8080) server port would be incorrect, would it not?
>
> That's just the most common problem: since servers /other/ than Tomcat
> often bind to port 8080, Tomcat may interfere with some other non-Tomcat
> process. You're point is valid, though: there are many potentially
> conflicting port numbers in server.xml.
>
> Patches, even for documentation, are always welcome...
as i'm still working my way thru the docs, i don't think i'm ready
to start submitting patches just yet. give me a few days ...
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: what exactly does it mean to run multiple tomcat "instances"?
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Robert,
On 4/1/2011 1:13 PM, Robert P. J. Day wrote:
> On Thu, 31 Mar 2011, Christopher Schultz wrote:
>> So... it specifically tells you that it will use your own
>> conf/server.xml file. Would you like an additional reinforcing statement?
>
> Why, yes, thanks for asking so politely. :-) because if you read
> further down in that RUNNING.txt file, you see:
>
> [snip]
>
> now correct me if i'm wrong, but since we just established that you
> need to reassign more than just the main (8080) server port, to then
> subsequently claim that all you need to do to avoid a conflict is to
> reassign the main (8080) server port would be incorrect, would it not?
That's just the most common problem: since servers /other/ than Tomcat
often bind to port 8080, Tomcat may interfere with some other non-Tomcat
process. You're point is valid, though: there are many potentially
conflicting port numbers in server.xml.
Patches, even for documentation, are always welcome...
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk2WLdwACgkQ9CaO5/Lv0PA+DQCgmpu8ErvC1PU6xw/71yDbPN3E
XJgAn1eDSlYEBFSRtvWeXngEkJ8NGRd6
=us+1
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: what exactly does it mean to run multiple tomcat "instances"?
Posted by "Robert P. J. Day" <rp...@crashcourse.ca>.
On Thu, 31 Mar 2011, Christopher Schultz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Robert,
>
> On 3/31/2011 9:07 AM, Robert P. J. Day wrote:
> > i'd eventually deduced most of that. i think it would be useful if
> > that were explained more forcefully in the RUNNING.txt file since it's
> > not immediately obvious.
>
> - From RUNNING.txt:
>
> " When you use $CATALINA_BASE, Tomcat will calculate all relative
> references for files in the following directories based on the value
> of $CATALINA_BASE instead of $CATALINA_HOME:
>
> * bin - Only setenv.sh (*nix), setenv.bat (windows) and tomcat-juli.jar
>
> * conf - Server configuration files (including server.xml)
> "
>
> So... it specifically tells you that it will use your own
> conf/server.xml file. Would you like an additional reinforcing statement?
why, yes, thanks for asking so politely. :-) because if you read
further down in that RUNNING.txt file, you see:
================
Troubleshooting
================
There are only really 3 things likely to go wrong during the stand-alone
Tomcat install:
(1) The most common hiccup is when another web server (or any process for that
matter) has laid claim to port 8080. This is the default HTTP port that
Tomcat attempts to bind to at startup. To change this, open the file:
$CATALINA_HOME/conf/server.xml
and search for '8080'. Change it to a port that isn't in use, and is
greater than 1024, as ports less than or equal to 1024 require superuser
access to bind under UNIX.
Restart Tomcat and you're in business. Be sure that you replace the "8080"
in the URL you're using to access Tomcat. For example, if you change the
port to 1977, you would request the URL http://localhost:1977/ in your browser.
now correct me if i'm wrong, but since we just established that you
need to reassign more than just the main (8080) server port, to then
subsequently claim that all you need to do to avoid a conflict is to
reassign the main (8080) server port would be incorrect, would it not?
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: what exactly does it mean to run multiple tomcat "instances"?
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Robert,
On 3/31/2011 9:07 AM, Robert P. J. Day wrote:
> i'd eventually deduced most of that. i think it would be useful if
> that were explained more forcefully in the RUNNING.txt file since it's
> not immediately obvious.
- From RUNNING.txt:
"
When you use $CATALINA_BASE, Tomcat will calculate all relative
references for
files in the following directories based on the value of $CATALINA_BASE
instead
of $CATALINA_HOME:
* bin - Only setenv.sh (*nix), setenv.bat (windows) and tomcat-juli.jar
* conf - Server configuration files (including server.xml)
"
So... it specifically tells you that it will use your own
conf/server.xml file. Would you like an additional reinforcing statement?
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk2Ujr4ACgkQ9CaO5/Lv0PDs4wCgtbzCav3COtmMu09oOoS51HnV
cGQAoI8vMd2r0+SUmFLAA4nNbpXfMeZr
=HV5y
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: what exactly does it mean to run multiple tomcat "instances"?
Posted by "Robert P. J. Day" <rp...@crashcourse.ca>.
On Thu, 31 Mar 2011, Caldarale, Charles R wrote:
> > From: Robert P. J. Day [mailto:rpjday@crashcourse.ca]
> > Subject: what exactly does it mean to run multiple tomcat "instances"?
>
> > i can see how multiple users could share a common CATALINA_HOME
> > directory, whose only common contents would be the bin/ and lib/
> > directories. but how would individual users take advantage of that?
>
> This has nothing to do with users, but rather with running multiple
> Tomcat servers on a single machine. For example, you may want to
> segregate webapps more than you can inside a single JVM, thus
> avoiding the potential of one misbehaving webapp taking the whole
> set down.
>
> > if i change that server port to, say, 8081, i'm just going to
> > run into another conflict on port 8009.
>
> Yes, each ip-address/port combination must be unique for each
> instance of Tomcat. This is true for any server-like program, not
> just Tomcat.
>
> > so if i want to run an entirely separate tomcat instance, don't i
> > have to modify server.xml
>
> Yes - each instance must have its own.
i'd eventually deduced most of that. i think it would be useful if
that were explained more forcefully in the RUNNING.txt file since it's
not immediately obvious.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: what exactly does it mean to run multiple tomcat "instances"?
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Robert P. J. Day [mailto:rpjday@crashcourse.ca]
> Subject: what exactly does it mean to run multiple tomcat "instances"?
> i can see how multiple users could share a common CATALINA_HOME
> directory, whose only common contents would be the bin/ and lib/
> directories. but how would individual users take advantage of that?
This has nothing to do with users, but rather with running multiple Tomcat servers on a single machine. For example, you may want to segregate webapps more than you can inside a single JVM, thus avoiding the potential of one misbehaving webapp taking the whole set down.
> if i change that server port to, say, 8081, i'm just going to
> run into another conflict on port 8009.
Yes, each ip-address/port combination must be unique for each instance of Tomcat. This is true for any server-like program, not just Tomcat.
> so if i want to run an entirely separate tomcat instance, don't i
> have to modify server.xml
Yes - each instance must have its own.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org