You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by "Richard S. Huntrods" <hu...@nucleus.com> on 2001/12/21 18:46:46 UTC
Lessons Learned...
Greetings!
Having just come through a steep learning curve, I thought I'd compress
the lessons learned for the benefit of all:
Problem:
Tomcat 4.0 ran on W2K, but 4.0.1 would not
Solution:
New classloader didn't like different versions of "servlet.jar" in
JAVA_HOMEjre/lib/ext and CATALINA_HOME/common/lib
Put the same servlet.jar (use the TC4.0.1 version) in both places, and
all works.
Problem:
TC 4.0.1 ran SSL easily on W2K, but same stuff would not run on Solaris
8
Solution:
Solaris 8 comes with Java SDK 1.2 as default. Obtain and install SDK
1.3 and
everything works properly.
NOTE: be sure to put the JSSE jar files (3 of them) in the
JAVA_HOME/jre/lib/ext directory (this is one of the two suggested
installation choices). I found that the variable JSSE_HOME did not
work. The JSSE jars should NOT be placed anywhere in Tomcat.
Problem:
Two servers - one Apache only, one Tomcat only. (BTW, this is my
recommendation for anyone with significant "stuff" in both web and
servlets/jsp. Divides the load on a very smart boundary, and avoids all
those "why won't Apache forward stuff to Tomcat" type problems.) Could
not get https to properly find my Tomcat server.
Solution:
First, Apache is listening on port 80. Good. Make Tomcat listen to
port 443, as this is the standard SSL (https) port. Avoids client
firewall problems as well (we did have a problem with one client's site
and port 8080 - their firewall blocked it).
Second, make SURE your hardware (routers) and O/S (servers) are all
working properly. If they aren't, no amount of "Tomcat fiddling" will
solve the underlying problem. In my case, the "defaultrouter" file in
Solaris was pointing to the wrong router for the current configuration.
Fixed defaultrouter, and HTTPS worked immediately.
Next email - my last (current) problem!
Cheers,
-Richard
--
To unsubscribe: <ma...@jakarta.apache.org>
For additional commands: <ma...@jakarta.apache.org>
Troubles with the list: <ma...@jakarta.apache.org>
RE: Alternate webapps dir not seen by apache
Posted by "Charles N. Harvey III" <ch...@alloy.com>.
answer inline:
>> -----Original Message-----
>> From: Brian Adams [mailto:bigb@satx.rr.com]
>> Sent: Friday, December 21, 2001 4:53 PM
>> To: Tomcat Users List
>> Subject: RE: Alternate webapps dir not seen by apache
>>
>>
>> have you erased the compiled apps in the work directory?
>>
>>
----------------------------------------------------------------------------
---
I thought for sure that would have been it. But it definately put me
on the right path. Here is how it went down...
I have just figured it out. Very odd. I had to keep my work directory
open whilst I was stopping and starting services.
When tomcat starts up it creats a "localhost" directory inside the work
directory. This is because of the first engine which has:
name="localhost"
Bear with me, this took me quite a few tries to figure out.
A few seconds later a second directory was created, called "apache"
because the engine under the warp connector has:
name="apache"
But... when I would access my computer, I was not using http://localhost.
I was using http://charlieh, the way other users in the office would do it.
And I noticed that once I accessed the site, a "charlieh" directory was
created in the work directory.
So I changed the second engine name to be "charlieh" and then everything
worked the way it was supposed to. Now I just need to be mindful of that
once I start moving this environment into production (which will be linux
so a whole new set of challenges). Especially if I create a few virtual
hosts in Apache.
Thanks so much for the help. And people say they don't like open source
because there is no support. :)
Charlie
>> -----Original Message-----
>>From: Charles N. Harvey III [mailto:charlieh@alloy.com]
>> Sent: Friday, December 21, 2001 3:20 PM
>> To: Tomcat Users List
>> Subject: Alternate webapps dir not seen by apache
>>
>>
>> Hello.
>>
>> I have tomcat at C:\tomcat and apache at C:\apache.
>> I have the warp module in place and everything is working just peachy
>> for me in my little test environment (my desktop). I realized that I
>> do not want all my webapps in the C:\tomcat\webapps directory because if
>> I install a new version of tomcat it will be easier to have all my apps
>> in one central place (not ususual thoughts).
>>
>> I moved my webapps to C:\website. So I have the example and manager
>> and even the forumdemo app from Velocity. I changed server.xml to see
>> the new directory as the base for both Standalone and Apache. I go to
>> http://localhost:8080/examples/jsp/index.html and its all good. The
little
>> text change that I made at the top of the page is present. But when I
>> go to http://localhost/examples/jsp/index.html it is still seeing the
>> original one in the C:\tomcat\webapps directory. Do I just need to
>> restart a few times? Is there a different way to configure the
httpd.conf?
>>
>> WebAppConnection warpConnection warp localhost:8008
>> WebAppDeploy examples warpConnection /examples/
>>
>> and server.xml has:
>>
>> <!-- Define the default virtual host -->
>> <Host name="localhost"
>> debug="0"
>> appBase="C:\website"
>> unpackWARs="true">
>>
>>
>> How come Tomcat can see it and not Apache? I will keep hacking away at
it.
>> I was just wondering if anyone else had run into this problem.
>>
>> Thanks.
>>
>> Charlie Harvey
>>
>>
--
To unsubscribe: <ma...@jakarta.apache.org>
For additional commands: <ma...@jakarta.apache.org>
Troubles with the list: <ma...@jakarta.apache.org>
RE: Alternate webapps dir not seen by apache
Posted by Brian Adams <bi...@satx.rr.com>.
have you erased the compiled apps in the work directory?
-----Original Message-----
From: Charles N. Harvey III [mailto:charlieh@alloy.com]
Sent: Friday, December 21, 2001 3:20 PM
To: Tomcat Users List
Subject: Alternate webapps dir not seen by apache
Hello.
I have tomcat at C:\tomcat and apache at C:\apache.
I have the warp module in place and everything is working just peachy
for me in my little test environment (my desktop). I realized that I
do not want all my webapps in the C:\tomcat\webapps directory because if
I install a new version of tomcat it will be easier to have all my apps
in one central place (not ususual thoughts).
I moved my webapps to C:\website. So I have the example and manager
and even the forumdemo app from Velocity. I changed server.xml to see
the new directory as the base for both Standalone and Apache. I go to
http://localhost:8080/examples/jsp/index.html and its all good. The little
text change that I made at the top of the page is present. But when I
go to http://localhost/examples/jsp/index.html it is still seeing the
original one in the C:\tomcat\webapps directory. Do I just need to
restart a few times? Is there a different way to configure the httpd.conf?
WebAppConnection warpConnection warp localhost:8008
WebAppDeploy examples warpConnection /examples/
and server.xml has:
<!-- Define the default virtual host -->
<Host name="localhost"
debug="0"
appBase="C:\website"
unpackWARs="true">
How come Tomcat can see it and not Apache? I will keep hacking away at it.
I was just wondering if anyone else had run into this problem.
Thanks.
Charlie Harvey
--
To unsubscribe: <ma...@jakarta.apache.org>
For additional commands: <ma...@jakarta.apache.org>
Troubles with the list: <ma...@jakarta.apache.org>
--
To unsubscribe: <ma...@jakarta.apache.org>
For additional commands: <ma...@jakarta.apache.org>
Troubles with the list: <ma...@jakarta.apache.org>
Alternate webapps dir not seen by apache
Posted by "Charles N. Harvey III" <ch...@alloy.com>.
Hello.
I have tomcat at C:\tomcat and apache at C:\apache.
I have the warp module in place and everything is working just peachy
for me in my little test environment (my desktop). I realized that I
do not want all my webapps in the C:\tomcat\webapps directory because if
I install a new version of tomcat it will be easier to have all my apps
in one central place (not ususual thoughts).
I moved my webapps to C:\website. So I have the example and manager
and even the forumdemo app from Velocity. I changed server.xml to see
the new directory as the base for both Standalone and Apache. I go to
http://localhost:8080/examples/jsp/index.html and its all good. The little
text change that I made at the top of the page is present. But when I
go to http://localhost/examples/jsp/index.html it is still seeing the
original one in the C:\tomcat\webapps directory. Do I just need to
restart a few times? Is there a different way to configure the httpd.conf?
WebAppConnection warpConnection warp localhost:8008
WebAppDeploy examples warpConnection /examples/
and server.xml has:
<!-- Define the default virtual host -->
<Host name="localhost"
debug="0"
appBase="C:\website"
unpackWARs="true">
How come Tomcat can see it and not Apache? I will keep hacking away at it.
I was just wondering if anyone else had run into this problem.
Thanks.
Charlie Harvey
--
To unsubscribe: <ma...@jakarta.apache.org>
For additional commands: <ma...@jakarta.apache.org>
Troubles with the list: <ma...@jakarta.apache.org>