RE: TOMCAT listening on 80 Thanks John-Turner/Jan-Michael/seemanto/Donie/Anyone....
Hi,
Thanks John, Everything works perfect now. ;-) I am
almost done with the integration of tomcat and apache. I was planning to
configure mod_ssl with tomcat.
SO here are few of my queries.
1. Is apache ssl default for redhat, how different is it from mod_ssl.
2. Do I need to make changes in server.xml or the httpd.conf
If you have some pointers for this let me know.
Regards
Vivek
-Original Message-
From: Turner, John [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 07, 2003 6:31 PM
To: 'Tomcat Users List'
Subject: RE: TOMCAT listening on 80 Thanks
John-Turner/Jan-Michael/seemanto/Donie/Anyone
In server.xml, comment out the CoyoteConnector on port 8080, and restart
Tomcat. Be careful editing server.xml. ;)
If you're feeling ambitious, you could always try disabling that
connector
in the admin app on port 80 now that you have the connector working, but
I've never done it that way.
John
-Original Message-
From: Vivek Singh [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 07, 2003 6:52 AM
To: 'Tomcat Users List'
Subject: TOMCAT listening on 80 Thanks
John-Turner/Jan-Michael/seemanto/Donie/Anyone
BINGO!!!
IT is working at last at port 80. All services still running.
Reason; screwed up server.xml.
Gotta watch those tags next time.
But I still have tomcat running at 8080. How do I stop
it at 8080?
-Original Message-
From: Turner, John [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 07, 2003 4:49 PM
To: ''Tomcat Users List' '
Subject: RE: RE: TOMCAT Not listening on 80
John-Turner/Jan-Michael/seemanto/Donie/Anyone
Yeah, your server.xml file is screwed up, which is why you aren't
getting
anything in mod_jk.conf, which is why Apache doesn't have any JK
directives,
which is why Apache doesn't understand what to do with JSP and servlet
URLs.
Fix your server.xml, sounds like you have a tag out of place
or you have
a
tag terminated incorrectly. If everything is fixed, you WILL
ALWAYS get
content in mod_jk.conf. If you don't, if mod_jk.conf is
empty, there is
something seriously wrong on the Tomcat side in server.xml.
You can always just add the JK directives to httpd.conf
directly, there
is a
link to a mod_jk.conf file on my site that has what you need
or will at
least provide a guideline.
John
-Original Message-
From: Vivek Singh
To: 'Tomcat Users List'; [EMAIL PROTECTED]
Sent: 1/7/03 4:35 AM
Subject: RE: RE: TOMCAT Not listening on 80
John-Turner/Jan-Michael/seemanto/Donie/Anyone
Hi ,
I just noticed that when I try opening the server
XML file I
get this error.
End tag 'Host' does not match the start tag 'Engine'. Line
388, Position
9
/Host
^
Any feedback!!
Regards
~Vivek
-Original Message-
From: Vivek Singh [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 07, 2003 2:56 PM
To: 'Tomcat Users List'
Subject: RE: RE: TOMCAT Not listening on 80
John-Turner/Jan-Michael/seemanto/Donie/Anyone
Hi Guys,
Here is what is happening now with very precise
info. I think
I was dealing at a very high level so far. . I am running
apache 1.3.19
+ tomcat 4.1.18 and modjk 1.2.1
I have given the URL down from where I got the entire .so module,no
building was done just a copy from Jakarta web site to the
apache module
directory.
Now this is the picture on the linux server.
http://192.168.132.34 is a test page from apache.
http://192.168.132.34/bugzilla is a perl-CGI application
sitting on port
80.
http://192.168.132.34:8080 tomcat's page
http://192.168.132.34:8080/examples/jsp/index.html shows me
JSP samples.
They execute very well
http://192.168.132.34:8080/examples/servlets/index.html shows me
servelets they execute very well.
PAGE NOT FOUND ERRORS for
http://192.168.132.34/examples/jsp/index.html
http://192.168.132.34/examples/servlets/index.htm;
Pl. Look for-
comments.
I am attaching all the configs file as mentioned by Jan/John. The
mod_jk.conf file is always empty after I deleted the contents,since I
assumed that it would be autogenrated. But it never did.
I edited the contents of server.xml and insered
workers.properties from
John's website, Just retyping the URL again..
http://www.johnturner.com/howto/apache2-tomcat4110-jk-howto.html
Thanks Again.
Hope to hear a LOT!!
~Vivek
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 06, 2003 9:44 PM
To: Tomcat Users List
Subject: Re: RE: TOMCAT Not listening on 80
Hi there,
Hi vivek,
John Turner's suggestion is right on. Try setting it up on a
development box first. This will save you and your colleagues
a lot of
headaches later on. Besides it is good practice. But here are some
pointers
RE: TOMCAT listening on 80 Thanks John-Turner/Jan-Michael/seemanto/Donie/Anyone....
I've never done it, but from reading this list: - you need to setup SSL on Apache, not Tomcat, if the two are integrated...communications between the two via JK and JK2 are NOT over SSL, even if the communication between Apache and the client browser uses SSL. Make sure the SSL connector on 8443 in server.xml by default is disabled along with the connector on 8080. - I think that there are issues with Apache SSL configuration and using the auto-generation ApacheConfig feature of mod_jk, in that ApacheConfig generates Apache VirtualHost containers using hostnames, and SSL configuration in httpd.conf needs IP addresses, which means you have to do the SSL part by hand I've only setup SSL for Tomcat alone and Apache alone, never when the two are integrated. In any case, I would start going through the process of setting up SSL on Apache, and just post back here under a new thread if you have problems. I'm sure someone who has done it will reply with suggestions, and who knows, maybe we will get a new HOWTO out of it. :) John -Original Message- From: Vivek Singh [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 5:25 AM To: 'Tomcat Users List' Subject: RE: TOMCAT listening on 80 Thanks John-Turner/Jan-Michael/seemanto/Donie/Anyone Hi, Thanks John, Everything works perfect now. ;-) I am almost done with the integration of tomcat and apache. I was planning to configure mod_ssl with tomcat. SO here are few of my queries. 1. Is apache ssl default for redhat, how different is it from mod_ssl. 2. Do I need to make changes in server.xml or the httpd.conf If you have some pointers for this let me know. Regards Vivek -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 07, 2003 6:31 PM To: 'Tomcat Users List' Subject: RE: TOMCAT listening on 80 Thanks John-Turner/Jan-Michael/seemanto/Donie/Anyone In server.xml, comment out the CoyoteConnector on port 8080, and restart Tomcat. Be careful editing server.xml. ;) If you're feeling ambitious, you could always try disabling that connector in the admin app on port 80 now that you have the connector working, but I've never done it that way. John -Original Message- From: Vivek Singh [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 07, 2003 6:52 AM To: 'Tomcat Users List' Subject: TOMCAT listening on 80 Thanks John-Turner/Jan-Michael/seemanto/Donie/Anyone BINGO!!! IT is working at last at port 80. All services still running. Reason; screwed up server.xml. Gotta watch those tags next time. But I still have tomcat running at 8080. How do I stop it at 8080? -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 07, 2003 4:49 PM To: ''Tomcat Users List' ' Subject: RE: RE: TOMCAT Not listening on 80 John-Turner/Jan-Michael/seemanto/Donie/Anyone Yeah, your server.xml file is screwed up, which is why you aren't getting anything in mod_jk.conf, which is why Apache doesn't have any JK directives, which is why Apache doesn't understand what to do with JSP and servlet URLs. Fix your server.xml, sounds like you have a tag out of place or you have a tag terminated incorrectly. If everything is fixed, you WILL ALWAYS get content in mod_jk.conf. If you don't, if mod_jk.conf is empty, there is something seriously wrong on the Tomcat side in server.xml. You can always just add the JK directives to httpd.conf directly, there is a link to a mod_jk.conf file on my site that has what you need or will at least provide a guideline. John -Original Message- From: Vivek Singh To: 'Tomcat Users List'; [EMAIL PROTECTED] Sent: 1/7/03 4:35 AM Subject: RE: RE: TOMCAT Not listening on 80 John-Turner/Jan-Michael/seemanto/Donie/Anyone Hi , I just noticed that when I try opening the server XML file I get this error. End tag 'Host' does not match the start tag 'Engine'. Line 388, Position 9 /Host ^ Any feedback!! Regards ~Vivek -Original Message- From: Vivek Singh [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 07, 2003 2:56 PM To: 'Tomcat Users List' Subject: RE: RE: TOMCAT Not listening on 80 John-Turner/Jan-Michael/seemanto/Donie/Anyone Hi Guys, Here is what is happening now with very precise info. I think I was dealing at a very high level so far. . I am running apache 1.3.19 + tomcat 4.1.18 and modjk 1.2.1 I have given the URL down from where I got the entire .so module,no building was done just a copy from Jakarta web site to the apache module directory. Now this is the picture on the linux server. http://192.168.132.34 is a test page from apache. http://192.168.132.34/bugzilla is a perl-CGI application sitting on port 80. http://192.168.132.34:8080 tomcat's page
RE: TOMCAT listening on 80 Thanks John-Turner/Jan-Michael/seemanto/Donie/Anyone....
the Java XML errors I used to get while stopping tomcat ./shutdown.sh have also gone. Regards ~Vivek **Disclaimer** Information contained in this E-MAIL being proprietary to Wipro Limited is 'privileged' and 'confidential' and intended for use only by the individual or entity to which it is addressed. You are notified that any use, copying or dissemination of the information contained in the E-MAIL in any manner whatsoever is strictly prohibited. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: TOMCAT listening on 80 Thanks John-Turner/Jan-Michael/seemanto/Donie/Anyone....
In server.xml, comment out the CoyoteConnector on port 8080, and restart
Tomcat. Be careful editing server.xml. ;)
If you're feeling ambitious, you could always try disabling that connector
in the admin app on port 80 now that you have the connector working, but
I've never done it that way.
John
-Original Message-
From: Vivek Singh [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 07, 2003 6:52 AM
To: 'Tomcat Users List'
Subject: TOMCAT listening on 80 Thanks
John-Turner/Jan-Michael/seemanto/Donie/Anyone
BINGO!!!
IT is working at last at port 80. All services still running.
Reason; screwed up server.xml.
Gotta watch those tags next time.
But I still have tomcat running at 8080. How do I stop
it at 8080?
-Original Message-
From: Turner, John [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 07, 2003 4:49 PM
To: ''Tomcat Users List' '
Subject: RE: RE: TOMCAT Not listening on 80
John-Turner/Jan-Michael/seemanto/Donie/Anyone
Yeah, your server.xml file is screwed up, which is why you aren't
getting
anything in mod_jk.conf, which is why Apache doesn't have any JK
directives,
which is why Apache doesn't understand what to do with JSP and servlet
URLs.
Fix your server.xml, sounds like you have a tag out of place
or you have
a
tag terminated incorrectly. If everything is fixed, you WILL
ALWAYS get
content in mod_jk.conf. If you don't, if mod_jk.conf is
empty, there is
something seriously wrong on the Tomcat side in server.xml.
You can always just add the JK directives to httpd.conf
directly, there
is a
link to a mod_jk.conf file on my site that has what you need
or will at
least provide a guideline.
John
-Original Message-
From: Vivek Singh
To: 'Tomcat Users List'; [EMAIL PROTECTED]
Sent: 1/7/03 4:35 AM
Subject: RE: RE: TOMCAT Not listening on 80
John-Turner/Jan-Michael/seemanto/Donie/Anyone
Hi ,
I just noticed that when I try opening the server
XML file I
get this error.
End tag 'Host' does not match the start tag 'Engine'. Line
388, Position
9
/Host
^
Any feedback!!
Regards
~Vivek
-Original Message-
From: Vivek Singh [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 07, 2003 2:56 PM
To: 'Tomcat Users List'
Subject: RE: RE: TOMCAT Not listening on 80
John-Turner/Jan-Michael/seemanto/Donie/Anyone
Hi Guys,
Here is what is happening now with very precise
info. I think
I was dealing at a very high level so far. . I am running
apache 1.3.19
+ tomcat 4.1.18 and modjk 1.2.1
I have given the URL down from where I got the entire .so module,no
building was done just a copy from Jakarta web site to the
apache module
directory.
Now this is the picture on the linux server.
http://192.168.132.34 is a test page from apache.
http://192.168.132.34/bugzilla is a perl-CGI application
sitting on port
80.
http://192.168.132.34:8080 tomcat's page
http://192.168.132.34:8080/examples/jsp/index.html shows me
JSP samples.
They execute very well
http://192.168.132.34:8080/examples/servlets/index.html shows me
servelets they execute very well.
PAGE NOT FOUND ERRORS for
http://192.168.132.34/examples/jsp/index.html
http://192.168.132.34/examples/servlets/index.htm;
Pl. Look for-
comments.
I am attaching all the configs file as mentioned by Jan/John. The
mod_jk.conf file is always empty after I deleted the contents,since I
assumed that it would be autogenrated. But it never did.
I edited the contents of server.xml and insered
workers.properties from
John's website, Just retyping the URL again..
http://www.johnturner.com/howto/apache2-tomcat4110-jk-howto.html
Thanks Again.
Hope to hear a LOT!!
~Vivek
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 06, 2003 9:44 PM
To: Tomcat Users List
Subject: Re: RE: TOMCAT Not listening on 80
Hi there,
Hi vivek,
John Turner's suggestion is right on. Try setting it up on a
development box first. This will save you and your colleagues
a lot of
headaches later on. Besides it is good practice. But here are some
pointers.
I have shifted the Bugzilla MySQL DB on a different box and
ghosted the server too
so I damn well have a contingency plan. Haven't I.
Let's not worry about it anymore If anything goes crazy I
will ghost
it again.
--
1. Log in as root or su to it
su -
-
one of the reasons why I write to user groups :-)
--
2. Search for perl
which perl or whereis perl
This should return /usr/bin/perl or /usr/local/bin/perl
--
/usr/bin/perl
--
3. Check the version
/path/to/perl -V
Note this version
--
5.6.0
--
4. Search for
