Chris/Chuck,
You are probably right about httpd. Please see the attached images for
details. The reason why I thought I had a 2.2 application is because whenever
I shutdown the 2.2 service, the main web site running on port 80 would not
launch. Please excuse my naiveness about our
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rashid,
On 4/7/2009 4:45 PM, Rashid Malik wrote:
To give you an example, the URL to get to the application in 4.1 is:
http://localhost/MyWebAPP/
However, after shutting down tomcat 4.1, installing and configuring
tomcat 6.0, I can use the new
Hi,
I changed port 8080 to 80 and I get page not found error. Please note that I
have another website that is running on an older version of tomcat. that
website is already using port 80. On that page, there is a link that connects
to http://localhost/MyWebAPP/ . If I use the older version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rashid,
On 4/7/2009 5:08 PM, Rashid Malik wrote:
Hi, I changed port 8080 to 80 and I get page not found error. Please
note that I have another website that is running on an older version
of tomcat.
Aah, you didn't mention that.
Only one process
Hello Chris,
Thanks for your quick response. What you said makes sense to me but let me
clarify my situation further.
Hi, I changed port 8080 to 80 and I get page not found error. Please
note that I have another website that is running on an older version
of tomcat.
What I mean here is
From: Rashid Malik [mailto:rma...@dhmh.state.md.us]
Subject: Re: Migration from Tomcat 4.1 to 6.0 Urgent
There is tomcat 2.2 application (using port 80)
There was never any Tomcat 2.2 release. You may actually have httpd on port
80, since there is a 2.2 version of that. httpd usually
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rashid,
On 4/7/2009 5:45 PM, Rashid Malik wrote:
What I mean here is that I have three 3 installations of tomcat not
2.
How many total web applications do you have?
Do any of them have any requirements for which Tomcat version on which
they are