Using port 8080 connects directly to Tomcat running in stand-alone mode. If
you want to use port 80 (the web server standard/default), you must either
use a web server and configure it to pass all *.jsp pages to Tomcat, or
configure Tomcat to listen to port 80 instead of 8080. Connecting Tomcat
Subject: Re: jsp wont open unless port 8080 is specified in browser
Thanks a lot for your help Travis. I dont suppose you could
tell me how to
configure my windows 2000 server to pass all jsp
files to tomcat would you?
Thanks again.
martin
- Original Message -
From: Travis Schmid
. 15...
I'm going to dbl check environ variables
-Original Message-
From: Travis Schmid [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 16, 2001 5:11 PM
To: 'Tomcat Users List'
Subject: RE: Mod-jk conf question
Check your include line in the httpd.conf file in apache
will be watching for any feedback
on this one!
Travis Schmid wrote:
H...I don't know what would stop Tomcat from generating
that file.
Have you checked the Tomcat logs and stdout to see if Tomcat is
listing any error messages when it starts up? Double check
c:/program
files
Tomcat autogenerates that file. You need to start Tomcat first, the Apache.
Travis
-Original Message-
From: Mike Kelley [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 16, 2001 3:20 PM
To: 'Tomcat Users List'
Subject: Mod-jk conf question
Since I can't get webapp to work on
apache
-Original Message-
From: Travis Schmid [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 16, 2001 4:49 PM
To: 'Tomcat Users List'
Subject: RE: Mod-jk conf question
Tomcat autogenerates that file. You need to start Tomcat
first, the Apache.
Travis
-Original
David,
We are using Tomcat 3.2.3 with mod_jk but it should be similar in 4.0. We
set it up like this to utilize multiple processors and machines efficiently
for better scalability. Here's what we did:
We setup Apache to start 4 Ajp13 workers all communicating on a different
port number.
Then
-Original Message-
From: Schulz, Sebastian, fiscus GmbH, Bonn
[mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 14, 2001 1:19 AM
To: '[EMAIL PROTECTED]'
Subject: AW: mod_jk / Ajp13 config fix on heavily loaded system
what's about loadbalancing?
say, we have defined
Thanks for the thought but it is neither of those things. I was using the
-Xrs flag and was NOT encountering the shutdown bug. The additional
services would shutdown immediately upon starting a second service. I
didn't have to logout for the problem to occur.
The services were installed using
We got around the shutdown when logging off issue by using SUN JDK 1.3.1.01
and including the -Xrs switch in the wrapper.properties file. This flag was
readded to the JDK to address this issue. You can get the whole history of
the bug on Sun's Java BugParade website.
I had a similar problem running Tomcat as an NT service on Win2k Pro. I
could start one instance but when starting second the first would shut down
with no error message. I could install as many as I wanted but only one
would run at a time. I found that this problem doesn't exist with Win NT
I am working with Tomcat 3.2.3 and Apache 1.3.2. I have configured Tomcat
to use multiple Ajp13 workers and a loadbalancer worker to control them
using the worker.properties file. After reading the documentation, I am
unclear whether each worker has it's own instance of a JVM.
Travis
--
To
12 matches
Mail list logo
