RE: Connecting the HTTP Server and Tomcat
Hi, The jsvc utility in commons-daemon is just for this purpose, it allows you to specify a user TC should run as, and if you read the INSTALL.txt and Tomcat5.sh under native/ you will know it's very easy to change the startup method. Yang -Original Message- From: SH Solutions [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 5:35 PM To: 'Tomcat Users List' Subject: RE: Connecting the HTTP Server and Tomcat Hi Currently I use catalina.sh start | stop to control tomcat 4.1.x and 5.0.x running as root. Can I change it easily to use commons-daemon (running as non-root)? A lot of command line options are set in catalina.sh. Would I need to do this manually ? Regards, Steffen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Connecting the HTTP Server and Tomcat
Hi, You can change fairly easily to run with commons-daemon. Specific instructions are at http://jakarta.apache.org/tomcat/tomcat-5.0-doc/setup.html and general instructions for daemon are at http://jakarta.apache.org/commons/daemon/jsvc.html (for unix platforms) and http://jakarta.apache.org/commons/daemon/procrun.html (for windows platforms). As to your command-line options, it depends. If you mean many -D params for the JVMs, that's easy to copy and paste to the jsvc/procrun script. If you mean options set by catalina.sh, there really aren't that many (4-5, e.g. endorsed directory, classpath), and they're short. You will need to copy and paste those into your jsvc/procrun script if you write one. You can also look at/extend $CATALINA_HOME/bin/catalina.xml, and use commons-launcher (http://jakarta.apache.org/commons/launcher/) to launch your tomcat. This eliminates the need for OS-specific scripts, instead using an Ant file. This Ant file (catalina.xml) provided with tomcat has the utility tasks and information you'd need. Please start another thread on this mailing list if you go down one of these routes. Yoav Shapira Millennium Research Informatics -Original Message- From: SH Solutions [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 5:35 PM To: 'Tomcat Users List' Subject: RE: Connecting the HTTP Server and Tomcat Hi Currently I use catalina.sh start | stop to control tomcat 4.1.x and 5.0.x running as root. Can I change it easily to use commons-daemon (running as non-root)? A lot of command line options are set in catalina.sh. Would I need to do this manually ? Regards, Steffen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Connecting the HTTP Server and Tomcat
Hi. I realize you're looking at jsvc right now and thinking about removing the Apache component altogether, but I'll take a shot at this anyway. AddModule appears to have been dropped in Apache 2.0.xx, so just leave it out. I didn't use it in my environment and things are working. Here's most likely to be an issue: Did you name your worker in workers.properties 'ajp13'? You should probably change your JkMount to read: JkMount/portal/* ajp13worker # or whatever you named the ajp13 worker If you did name your worker 'ajp13', I would at least change the name to something else just to remove confusion. This may or may not affect you, but I'll throw it out there in case some reading this finds it useful. In my config, I was setting things up for a virtual host environtment and things only worked when JkWorkersFile, JkLogFile, and JkLogLevel stayed out of my VirtualHost block. Only JkMount was included in the VirualHost block. I'm not sure whether that's normal or not, but it's my experience. --David Wilson, Allen wrote: No a problem...I am using 2.0.48.. I have the LoadModule line and the other directives here...they are LoadModule jk_module /usr/WWW/libexec/mod_jk.so JkWorkersFile /usr/tomcat-4.1.18/conf/jk/workers.properties JkLogFile /usr/tomcat-4.1.18/logs/mod_jk.log JkLogLeveldebug JkMount /portal/* ajp13 I was unable to put in the AddModule line because I did not see it (the mod_jk.c file) loaded when I did the apachectl -l. I am working on getting that loaded now -Original Message- From: David Smith [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 3:19 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat Hi. Can you post the relevant parts of your httpd.conf file? Also, I missed this in the thread if it was mentioned, but what version of Apache are you working with? I ask, because it looks like from my setup that Apache ditched the AddModule directive in Apache 2.0.xx. LoadModule needs to be in your httpd.conf file before the AddModule directive under Apache 1.3.x as in: # All the other LoadModule directive here. LoadModule jk_module modules/mod_jk.so # Further down, all the AddModule directives here AddModule mod_jk.c It'd be helpful to see the JkWorkersFile directive, JkMount directive, and the contents of the jk workers file. --David Just tack it on to the end of the list of LoadModule directives. Then use AddModule at the end of the list of AddModule directives. Wilson, Allen wrote: I think I may have found the problem I tried to add the line AddModule mod_jk.c in the HTTP server config and it gave an error. I could not locate the file within my HTTP or Tomcat installation.even though I have the mod_jk.so file in the libexec directory. -Original Message- From: Jon Wingfield [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 2:35 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat Assuming the connector is working, what effect does adding an additional mapping of /portal ajp13 to your existing /portal/* ajp13 mapping have? I just double-checked on our dev box where jk is definitely up. I got a 404 from apache for /mapping but /mapping/stuff got routed through to tomcat. Jon Wilson, Allen wrote: No you are not way off...at least not from my point of view because that is what I thought would work. But unless I specify the port (http://myserver.com:8080/portal) it will not get there... It makes me think that the connector is not function correctly but I do not know how to tell..when I check the running ports I see the 8009 port running but it does not hand to Tomcat -Original Message- From: Jon Wingfield [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 2:09 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat I may be way off but... I don't think http://myserver.com/portal maps to /portal/* ajp13 http://myserver.com/portal/ or http://myserver.com/portal/whatever.jsp probably will, though. Give it a go, may work, Jon Wilson, Allen wrote: Bill..thanks for the reply... I will read through the link you provide but isn't that what the connector is supposed to do. My understanding what that the Apache HTTP server would detect what the request was (Java or not) and pass it on to Tomcat. Is this not what the specification of /portal/* ajp13 in the configuration does. This is what I got from the document at: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk.quickhowto.htm l Here is a little from one of the pages in that area... ( http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk/aphowto.html ) In a nutshell a web server is waiting for client HTTP requests. When these requests arrive the server does whatever is needed to serve the requests
RE: Connecting the HTTP Server and Tomcat
Not a problem... I wish I could get it working as easily with Apache and Tomcat on Solaris... I think I just missing something..but I cannot put my finger on it. -Original Message- From: Bill Bruns [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 6:31 PM To: Tomcat User Subject: RE: Connecting the HTTP Server and Tomcat Allen, thanks for pointing me at mod_jk. It works better than proxy or rewrite! I've implemented it here now on Apache 2.0 (under WinXP) connected to Tomcat 4.1.24 (Solaris). with mod_jk 1.2.5. Works great! In case it helps, I'll attach my config files: Tomcat's server.xml: - Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8113 minProcessors=5 maxProcessors=75 acceptCount=10 debug=20/ workers.properties: --- # Define 1 real worker using ajp13 worker.list=worker1 # Set properties for worker1 (ajp13) worker.worker1.type=ajp13 worker.worker1.host=192.168.1.62 worker.worker1.port=8113 worker.worker1.lbfactor=50 worker.worker1.cachesize=10 worker.worker1.cache_timeout=600 worker.worker1.socket_keepalive=1 worker.worker1.socket_timeout=300 Apache httpd.conf: -- # # Entries for connection to Tomcat # Load mod_jk module # Update this path to match your modules location LoadModule jk_module modules/mod_jk.dll # Declare the module for IfModule directive #AddModule mod_jk2.c # Where to find workers.properties # Update this path to match your conf directory location (put workers.properties next to httpd.conf) JkWorkersFile C:\Program Files\Apache Group\Apache2\conf\workers.properties # Where to put jk logs # Update this path to match your logs directory location (put mod_jk.log next to access_log) #JkLogFile /var/log/httpd/mod_jk.log # Set the jk log level [debug/error/info] #JkLogLevel info # Select the log format #JkLogStampFormat [%a %b %d %H:%M:%S %Y] # JkOptions indicate to send SSL KEY SIZE, #JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories # JkRequestLogFormat set the request format #JkRequestLogFormat %w %V %T # Send everything for context /examples to worker named worker1 (ajp13) JkMount /fitmesite/* worker1 jkMount /soap/* worker1 # # end of Tomcat connection info -Original Message- From: David Smith [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 1:19 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat Hi. Can you post the relevant parts of your httpd.conf file? Also, I missed this in the thread if it was mentioned, but what version of Apache are you working with? I ask, because it looks like from my setup that Apache ditched the AddModule directive in Apache 2.0.xx. LoadModule needs to be in your httpd.conf file before the AddModule directive under Apache 1.3.x as in: # All the other LoadModule directive here. LoadModule jk_module modules/mod_jk.so # Further down, all the AddModule directives here AddModule mod_jk.c It'd be helpful to see the JkWorkersFile directive, JkMount directive, and the contents of the jk workers file. --David Just tack it on to the end of the list of LoadModule directives. Then use AddModule at the end of the list of AddModule directives. Wilson, Allen wrote: I think I may have found the problem I tried to add the line AddModule mod_jk.c in the HTTP server config and it gave an error. I could not locate the file within my HTTP or Tomcat installation.even though I have the mod_jk.so file in the libexec directory. -Original Message- From: Jon Wingfield [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 2:35 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat Assuming the connector is working, what effect does adding an additional mapping of /portalajp13 to your existing /portal/* ajp13 mapping have? I just double-checked on our dev box where jk is definitely up. I got a 404 from apache for /mapping but /mapping/stuff got routed through to tomcat. Jon Wilson, Allen wrote: No you are not way off...at least not from my point of view because that is what I thought would work. But unless I specify the port (http://myserver.com:8080/portal) it will not get there... It makes me think that the connector is not function correctly but I do not know how to tell..when I check the running ports I see the 8009 port running but it does not hand to Tomcat -Original Message- From: Jon Wingfield [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 2:09 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat I may be way off but... I don't think http://myserver.com/portal maps to /portal/* ajp13 http://myserver.com/portal/ or http://myserver.com/portal/whatever.jsp probably will, though. Give it a go, may work, Jon Wilson, Allen wrote
RE: Connecting the HTTP Server and Tomcat
Okay...maybe I am missing the boat hereI've got the jsvc built and started to read through the Daemon API to see how to implement the interface for Tomcat-4.1.18. But I do not see how to use it to start my Tomcat session. Is there a for dummies book on this -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Thursday, April 08, 2004 7:47 AM To: Tomcat Users List Subject: RE: Connecting the HTTP Server and Tomcat Hi, You can change fairly easily to run with commons-daemon. Specific instructions are at http://jakarta.apache.org/tomcat/tomcat-5.0-doc/setup.html and general instructions for daemon are at http://jakarta.apache.org/commons/daemon/jsvc.html (for unix platforms) and http://jakarta.apache.org/commons/daemon/procrun.html (for windows platforms). As to your command-line options, it depends. If you mean many -D params for the JVMs, that's easy to copy and paste to the jsvc/procrun script. If you mean options set by catalina.sh, there really aren't that many (4-5, e.g. endorsed directory, classpath), and they're short. You will need to copy and paste those into your jsvc/procrun script if you write one. You can also look at/extend $CATALINA_HOME/bin/catalina.xml, and use commons-launcher (http://jakarta.apache.org/commons/launcher/) to launch your tomcat. This eliminates the need for OS-specific scripts, instead using an Ant file. This Ant file (catalina.xml) provided with tomcat has the utility tasks and information you'd need. Please start another thread on this mailing list if you go down one of these routes. Yoav Shapira Millennium Research Informatics -Original Message- From: SH Solutions [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 5:35 PM To: 'Tomcat Users List' Subject: RE: Connecting the HTTP Server and Tomcat Hi Currently I use catalina.sh start | stop to control tomcat 4.1.x and 5.0.x running as root. Can I change it easily to use commons-daemon (running as non-root)? A lot of command line options are set in catalina.sh. Would I need to do this manually ? Regards, Steffen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message may contain proprietary or confidential company information. Any unauthorized use or disclosure is prohibited. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Connecting the HTTP Server and Tomcat
Hi, Oh, I thought you were on tomcat 5. In a way, tomcat 4 is easier because it comes with a class that implements the Daemon interface already, so you don't need to write that. See org.apache.catalina.startup.BootstrapService/BootstrapServiceContext. http://www.mail-archive.com/[EMAIL PROTECTED]/msg111954.htm l Yoav Shapira Millennium Research Informatics -Original Message- From: Wilson, Allen [mailto:[EMAIL PROTECTED] Sent: Thursday, April 08, 2004 11:50 AM To: Tomcat Users List Subject: RE: Connecting the HTTP Server and Tomcat Okay...maybe I am missing the boat hereI've got the jsvc built and started to read through the Daemon API to see how to implement the interface for Tomcat-4.1.18. But I do not see how to use it to start my Tomcat session. Is there a for dummies book on this -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Thursday, April 08, 2004 7:47 AM To: Tomcat Users List Subject: RE: Connecting the HTTP Server and Tomcat Hi, You can change fairly easily to run with commons-daemon. Specific instructions are at http://jakarta.apache.org/tomcat/tomcat-5.0-doc/setup.html and general instructions for daemon are at http://jakarta.apache.org/commons/daemon/jsvc.html (for unix platforms) and http://jakarta.apache.org/commons/daemon/procrun.html (for windows platforms). As to your command-line options, it depends. If you mean many -D params for the JVMs, that's easy to copy and paste to the jsvc/procrun script. If you mean options set by catalina.sh, there really aren't that many (4-5, e.g. endorsed directory, classpath), and they're short. You will need to copy and paste those into your jsvc/procrun script if you write one. You can also look at/extend $CATALINA_HOME/bin/catalina.xml, and use commons-launcher (http://jakarta.apache.org/commons/launcher/) to launch your tomcat. This eliminates the need for OS-specific scripts, instead using an Ant file. This Ant file (catalina.xml) provided with tomcat has the utility tasks and information you'd need. Please start another thread on this mailing list if you go down one of these routes. Yoav Shapira Millennium Research Informatics -Original Message- From: SH Solutions [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 5:35 PM To: 'Tomcat Users List' Subject: RE: Connecting the HTTP Server and Tomcat Hi Currently I use catalina.sh start | stop to control tomcat 4.1.x and 5.0.x running as root. Can I change it easily to use commons-daemon (running as non-root)? A lot of command line options are set in catalina.sh. Would I need to do this manually ? Regards, Steffen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Connecting the HTTP Server and Tomcat
Hi, Oh and please start a new thread on this mailing list now that you're working with commons-daemon, for easier reference in the future. Yoav Shapira Millennium Research Informatics -Original Message- From: Wilson, Allen [mailto:[EMAIL PROTECTED] Sent: Thursday, April 08, 2004 11:50 AM To: Tomcat Users List Subject: RE: Connecting the HTTP Server and Tomcat Okay...maybe I am missing the boat hereI've got the jsvc built and started to read through the Daemon API to see how to implement the interface for Tomcat-4.1.18. But I do not see how to use it to start my Tomcat session. Is there a for dummies book on this -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Thursday, April 08, 2004 7:47 AM To: Tomcat Users List Subject: RE: Connecting the HTTP Server and Tomcat Hi, You can change fairly easily to run with commons-daemon. Specific instructions are at http://jakarta.apache.org/tomcat/tomcat-5.0-doc/setup.html and general instructions for daemon are at http://jakarta.apache.org/commons/daemon/jsvc.html (for unix platforms) and http://jakarta.apache.org/commons/daemon/procrun.html (for windows platforms). As to your command-line options, it depends. If you mean many -D params for the JVMs, that's easy to copy and paste to the jsvc/procrun script. If you mean options set by catalina.sh, there really aren't that many (4-5, e.g. endorsed directory, classpath), and they're short. You will need to copy and paste those into your jsvc/procrun script if you write one. You can also look at/extend $CATALINA_HOME/bin/catalina.xml, and use commons-launcher (http://jakarta.apache.org/commons/launcher/) to launch your tomcat. This eliminates the need for OS-specific scripts, instead using an Ant file. This Ant file (catalina.xml) provided with tomcat has the utility tasks and information you'd need. Please start another thread on this mailing list if you go down one of these routes. Yoav Shapira Millennium Research Informatics -Original Message- From: SH Solutions [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 5:35 PM To: 'Tomcat Users List' Subject: RE: Connecting the HTTP Server and Tomcat Hi Currently I use catalina.sh start | stop to control tomcat 4.1.x and 5.0.x running as root. Can I change it easily to use commons-daemon (running as non-root)? A lot of command line options are set in catalina.sh. Would I need to do this manually ? Regards, Steffen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Connecting the HTTP Server and Tomcat
Not a problemand no..I still do not have it working Here is the workers.properties #BEGIN workers.properties worker.list=ajp13 worker.ajp13.port=8009 worker.ajp13.host=localhost worker.ajp13.type=ajp13 worker.ajp13.lbfactor=1 #END workers.properties -Original Message- From: Bill Bruns [mailto:[EMAIL PROTECTED] Sent: Thursday, April 08, 2004 1:49 PM To: Wilson, Allen Subject: RE: Connecting the HTTP Server and Tomcat Allen, did you solve the problem of connecting these? If not, someone in another email had asked that you show your worker.properties file. That could be helpful. So post it if it ain't soup yet. Regards Bill -Original Message- From: Wilson, Allen [mailto:[EMAIL PROTECTED] Sent: Thursday, April 08, 2004 7:32 AM To: Tomcat Users List; [EMAIL PROTECTED] Subject: RE: Connecting the HTTP Server and Tomcat Not a problem... I wish I could get it working as easily with Apache and Tomcat on Solaris... I think I just missing something..but I cannot put my finger on it. -Original Message- From: Bill Bruns [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 6:31 PM To: Tomcat User Subject: RE: Connecting the HTTP Server and Tomcat Allen, thanks for pointing me at mod_jk. It works better than proxy or rewrite! I've implemented it here now on Apache 2.0 (under WinXP) connected to Tomcat 4.1.24 (Solaris). with mod_jk 1.2.5. Works great! In case it helps, I'll attach my config files: Tomcat's server.xml: - Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8113 minProcessors=5 maxProcessors=75 acceptCount=10 debug=20/ workers.properties: --- # Define 1 real worker using ajp13 worker.list=worker1 # Set properties for worker1 (ajp13) worker.worker1.type=ajp13 worker.worker1.host=192.168.1.62 worker.worker1.port=8113 worker.worker1.lbfactor=50 worker.worker1.cachesize=10 worker.worker1.cache_timeout=600 worker.worker1.socket_keepalive=1 worker.worker1.socket_timeout=300 Apache httpd.conf: -- # # Entries for connection to Tomcat # Load mod_jk module # Update this path to match your modules location LoadModule jk_module modules/mod_jk.dll # Declare the module for IfModule directive #AddModule mod_jk2.c # Where to find workers.properties # Update this path to match your conf directory location (put workers.properties next to httpd.conf) JkWorkersFile C:\Program Files\Apache Group\Apache2\conf\workers.properties # Where to put jk logs # Update this path to match your logs directory location (put mod_jk.log next to access_log) #JkLogFile /var/log/httpd/mod_jk.log # Set the jk log level [debug/error/info] #JkLogLevel info # Select the log format #JkLogStampFormat [%a %b %d %H:%M:%S %Y] # JkOptions indicate to send SSL KEY SIZE, #JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories # JkRequestLogFormat set the request format #JkRequestLogFormat %w %V %T # Send everything for context /examples to worker named worker1 (ajp13) JkMount /fitmesite/* worker1 jkMount /soap/* worker1 # # end of Tomcat connection info -Original Message- From: David Smith [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 1:19 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat Hi. Can you post the relevant parts of your httpd.conf file? Also, I missed this in the thread if it was mentioned, but what version of Apache are you working with? I ask, because it looks like from my setup that Apache ditched the AddModule directive in Apache 2.0.xx. LoadModule needs to be in your httpd.conf file before the AddModule directive under Apache 1.3.x as in: # All the other LoadModule directive here. LoadModule jk_module modules/mod_jk.so # Further down, all the AddModule directives here AddModule mod_jk.c It'd be helpful to see the JkWorkersFile directive, JkMount directive, and the contents of the jk workers file. --David Just tack it on to the end of the list of LoadModule directives. Then use AddModule at the end of the list of AddModule directives. Wilson, Allen wrote: I think I may have found the problem I tried to add the line AddModule mod_jk.c in the HTTP server config and it gave an error. I could not locate the file within my HTTP or Tomcat installation.even though I have the mod_jk.so file in the libexec directory. -Original Message- From: Jon Wingfield [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 2:35 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat Assuming the connector is working, what effect does adding an additional mapping of /portalajp13 to your existing /portal/* ajp13 mapping have? I just double-checked on our dev box where jk is definitely up. I got a 404 from apache for /mapping but /mapping/stuff got routed through
RE: Connecting the HTTP Server and Tomcat
Okay...that looks similar to the tomcat 4 information I haveis your connector working correctly? -Original Message- From: Emerson Cargnin [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 6:06 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat My configuration is for tomcat 5: Service name=Catalina Connector acceptCount=100 connectionTimeout=2 disableUploadTimeout=true port=8080 redirectPort=8443 /Connector Connector port=8009 enableLookups=false redirectPort=8443 debug=0 protocol=AJP/1.3 / Engine defaultHost=localhost name=Catalina Host appBase=webapps name=localhost Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_log. suffix=.txt timestamp=true/ ... ... Wilson, Allen wrote: Here are the lines. Connector className=org.apache.catalina.connector.http.HttpConnector port=8080 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=2 / !-- Define an AJP 1.3 Connector on port 8009 -- Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8009 minProcessors=5 maxProcessors=75 acceptCount=10 debug=0/ Let me know if there is something that is incorrect. -Original Message- From: Emerson Cargnin [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 4:28 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat You said you can connect through port 8009 through the browser??? The jk protocol is not http, so if the configuration was allright you can't connect through 8009 as http. Maybe the error is at your server.xml... Wilson, Allen wrote: Thanks but this is on a Windows system and will not help...I am on a Solaris and I have looked at documents like this before and they still do not give me a definitive way of setting everything and testing it... Right now I have the HTTP server (port 80), Tomcat (port 8080), and the connector (8009) running. I even looked at the netstat to see if each port was available...and they were. When a do the home page request (http://myserver.com) it works fine...but if I request the page for the Jetspeed Portal (http://myserver.com/portal), I get an error. If I request the portal page through port 8080 it works fine. If I request the same page on 8009 it works fine. In all cases there were no entries in my mod_jk.log. I am looking for something that will outline the steps for me on a Solaris machine or at least give me a better way to diagnose what I am doing wrong -Original Message- From: kwilding [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 10:55 AM To: 'Tomcat Users List' Subject: RE: Connecting the HTTP Server and Tomcat http://www.greenfieldresearch.ca/technical/jk2_config.html This was a really good starting point. Ignore the fact it talks abut windows, I imstaled on SuSE8.2 using apache2.0.48 and both tomcat 4 and 5 Kevan -Original Message- From: Wilson, Allen [mailto:[EMAIL PROTECTED] Sent: 06 April 2004 16:42 To: Tomcat Users List Subject: Connecting the HTTP Server and Tomcat Good morning Can any provide some assistance on connecting the HTTP server and Tomcat together. I am using HTTP Server 2.0.48 and Tomcat-4.1.18 on a Sun Solaris machine. I think I have everything in place but when the only way I can reach the Tomcat stuff is my specifying the port number in the URL. Can someone point me in the direction of some How to connect Apache and Tomcat for Dummies instructions that will provide me some clear steps and methods for checking everything out. Thanks...and any help is appreciated. Allen This message may contain proprietary or confidential company information. Any unauthorized use or disclosure is prohibited. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message may contain proprietary or confidential company information. Any unauthorized use or disclosure is prohibited. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Emerson Cargnin Analista de Sistemas Setor de Desenvolvimento de Sistemas - TRE-SC tel : (048) - 251-3700 - Ramal 3181
RE: Connecting the HTTP Server and Tomcat
Allen, do you have the web server configured to throw the requests over to Tomcat? In other words, have either Proxy support or else URL Rewriting turned on in the web server? Otherwise your HTTP requests default to port 80, so they will be eaten by the web server and never reach Tomcat, since Tomcat is listening on ports that the HTTP requests do not come to by default. Have you looked at http://jakarta.apache.org/tomcat/tomcat-4.1-doc/proxy-howto.html - Bill -Original Message- From: Wilson, Allen [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 8:54 AM To: Tomcat Users List Subject: RE: Connecting the HTTP Server and Tomcat Okay...that looks similar to the tomcat 4 information I haveis your connector working correctly? -Original Message- From: Emerson Cargnin [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 6:06 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat My configuration is for tomcat 5: Service name=Catalina Connector acceptCount=100 connectionTimeout=2 disableUploadTimeout=true port=8080 redirectPort=8443 /Connector Connector port=8009 enableLookups=false redirectPort=8443 debug=0 protocol=AJP/1.3 / Engine defaultHost=localhost name=Catalina Host appBase=webapps name=localhost Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_log. suffix=.txt timestamp=true/ ... ... Wilson, Allen wrote: Here are the lines. Connector className=org.apache.catalina.connector.http.HttpConnector port=8080 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=2 / !-- Define an AJP 1.3 Connector on port 8009 -- Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8009 minProcessors=5 maxProcessors=75 acceptCount=10 debug=0/ Let me know if there is something that is incorrect. -Original Message- From: Emerson Cargnin [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 4:28 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat You said you can connect through port 8009 through the browser??? The jk protocol is not http, so if the configuration was allright you can't connect through 8009 as http. Maybe the error is at your server.xml... Wilson, Allen wrote: Thanks but this is on a Windows system and will not help...I am on a Solaris and I have looked at documents like this before and they still do not give me a definitive way of setting everything and testing it... Right now I have the HTTP server (port 80), Tomcat (port 8080), and the connector (8009) running. I even looked at the netstat to see if each port was available...and they were. When a do the home page request (http://myserver.com) it works fine...but if I request the page for the Jetspeed Portal (http://myserver.com/portal), I get an error. If I request the portal page through port 8080 it works fine. If I request the same page on 8009 it works fine. In all cases there were no entries in my mod_jk.log. I am looking for something that will outline the steps for me on a Solaris machine or at least give me a better way to diagnose what I am doing wrong -Original Message- From: kwilding [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 10:55 AM To: 'Tomcat Users List' Subject: RE: Connecting the HTTP Server and Tomcat http://www.greenfieldresearch.ca/technical/jk2_config.html This was a really good starting point. Ignore the fact it talks abut windows, I imstaled on SuSE8.2 using apache2.0.48 and both tomcat 4 and 5 Kevan -Original Message- From: Wilson, Allen [mailto:[EMAIL PROTECTED] Sent: 06 April 2004 16:42 To: Tomcat Users List Subject: Connecting the HTTP Server and Tomcat Good morning Can any provide some assistance on connecting the HTTP server and Tomcat together. I am using HTTP Server 2.0.48 and Tomcat-4.1.18 on a Sun Solaris machine. I think I have everything in place but when the only way I can reach the Tomcat stuff is my specifying the port number in the URL. Can someone point me in the direction of some How to connect Apache and Tomcat for Dummies instructions that will provide me some clear steps and methods for checking everything out. Thanks...and any help is appreciated. Allen This message may contain proprietary or confidential company information. Any unauthorized use or disclosure is prohibited. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED
RE: Connecting the HTTP Server and Tomcat
Bill..thanks for the reply... I will read through the link you provide but isn't that what the connector is supposed to do. My understanding what that the Apache HTTP server would detect what the request was (Java or not) and pass it on to Tomcat. Is this not what the specification of /portal/* ajp13 in the configuration does. This is what I got from the document at: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk.quickhowto.html Here is a little from one of the pages in that area... ( http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk/aphowto.html ) In a nutshell a web server is waiting for client HTTP requests. When these requests arrive the server does whatever is needed to serve the requests by providing the necessary content. Adding a servlet container may somewhat change this behavior. Now the web server needs also to perform the following: Load the servlet container adapter library and initialize it (prior to serving requests). When a request arrives, it needs to check and see if a certain request belongs to a servlet, if so it needs to let the adapter take the request and handle it. The adapter on the other hand needs to know what requests it is going to serve, usually based on some pattern in the request URL, and to where to direct these requests. Is this not correct...or am I misunderstanding it -Original Message- From: Bill Bruns [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 12:26 PM To: Tomcat Users List Subject: RE: Connecting the HTTP Server and Tomcat Allen, do you have the web server configured to throw the requests over to Tomcat? In other words, have either Proxy support or else URL Rewriting turned on in the web server? Otherwise your HTTP requests default to port 80, so they will be eaten by the web server and never reach Tomcat, since Tomcat is listening on ports that the HTTP requests do not come to by default. Have you looked at http://jakarta.apache.org/tomcat/tomcat-4.1-doc/proxy-howto.html - Bill -Original Message- From: Wilson, Allen [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 8:54 AM To: Tomcat Users List Subject: RE: Connecting the HTTP Server and Tomcat Okay...that looks similar to the tomcat 4 information I haveis your connector working correctly? -Original Message- From: Emerson Cargnin [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 6:06 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat My configuration is for tomcat 5: Service name=Catalina Connector acceptCount=100 connectionTimeout=2 disableUploadTimeout=true port=8080 redirectPort=8443 /Connector Connector port=8009 enableLookups=false redirectPort=8443 debug=0 protocol=AJP/1.3 / Engine defaultHost=localhost name=Catalina Host appBase=webapps name=localhost Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_log. suffix=.txt timestamp=true/ ... ... Wilson, Allen wrote: Here are the lines. Connector className=org.apache.catalina.connector.http.HttpConnector port=8080 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=2 / !-- Define an AJP 1.3 Connector on port 8009 -- Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8009 minProcessors=5 maxProcessors=75 acceptCount=10 debug=0/ Let me know if there is something that is incorrect. -Original Message- From: Emerson Cargnin [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 4:28 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat You said you can connect through port 8009 through the browser??? The jk protocol is not http, so if the configuration was allright you can't connect through 8009 as http. Maybe the error is at your server.xml... Wilson, Allen wrote: Thanks but this is on a Windows system and will not help...I am on a Solaris and I have looked at documents like this before and they still do not give me a definitive way of setting everything and testing it... Right now I have the HTTP server (port 80), Tomcat (port 8080), and the connector (8009) running. I even looked at the netstat to see if each port was available...and they were. When a do the home page request (http://myserver.com) it works fine...but if I request the page for the Jetspeed Portal (http://myserver.com/portal), I get an error. If I request the portal page through port 8080 it works fine. If I request the same page on 8009 it works fine. In all cases there were no entries in my mod_jk.log. I am looking for something that will outline the steps for me on a Solaris machine or at least give me a better way to diagnose what I am doing wrong -Original Message- From: kwilding [mailto:[EMAIL
RE: Connecting the HTTP Server and Tomcat
Allen, you ask isn't that what the connector is supposed to do, but the connector is in Tomcat, not in your web server. It is the web server software that is monitoring port 80, and that is where your browser sends requests to by default, so the request must get past the web server first. To do that you need to tell the web server where to send them, namely to your Tomcat port. I think this accounts for the behaviour you told about, namely that Tomcat responds fine when you specify the port number in your URL. -Bill -Original Message- From: Wilson, Allen [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 11:32 AM To: Tomcat Users List; [EMAIL PROTECTED] Subject: RE: Connecting the HTTP Server and Tomcat Bill..thanks for the reply... I will read through the link you provide but isn't that what the connector is supposed to do. My understanding what that the Apache HTTP server would detect what the request was (Java or not) and pass it on to Tomcat. Is this not what the specification of /portal/* ajp13 in the configuration does. This is what I got from the document at: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk.quickhowto.html Here is a little from one of the pages in that area... ( http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk/aphowto.html ) In a nutshell a web server is waiting for client HTTP requests. When these requests arrive the server does whatever is needed to serve the requests by providing the necessary content. Adding a servlet container may somewhat change this behavior. Now the web server needs also to perform the following: Load the servlet container adapter library and initialize it (prior to serving requests). When a request arrives, it needs to check and see if a certain request belongs to a servlet, if so it needs to let the adapter take the request and handle it. The adapter on the other hand needs to know what requests it is going to serve, usually based on some pattern in the request URL, and to where to direct these requests. Is this not correct...or am I misunderstanding it -Original Message- From: Bill Bruns [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 12:26 PM To: Tomcat Users List Subject: RE: Connecting the HTTP Server and Tomcat Allen, do you have the web server configured to throw the requests over to Tomcat? In other words, have either Proxy support or else URL Rewriting turned on in the web server? Otherwise your HTTP requests default to port 80, so they will be eaten by the web server and never reach Tomcat, since Tomcat is listening on ports that the HTTP requests do not come to by default. Have you looked at http://jakarta.apache.org/tomcat/tomcat-4.1-doc/proxy-howto.html - Bill -Original Message- From: Wilson, Allen [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 8:54 AM To: Tomcat Users List Subject: RE: Connecting the HTTP Server and Tomcat Okay...that looks similar to the tomcat 4 information I haveis your connector working correctly? -Original Message- From: Emerson Cargnin [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 6:06 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat My configuration is for tomcat 5: Service name=Catalina Connector acceptCount=100 connectionTimeout=2 disableUploadTimeout=true port=8080 redirectPort=8443 /Connector Connector port=8009 enableLookups=false redirectPort=8443 debug=0 protocol=AJP/1.3 / Engine defaultHost=localhost name=Catalina Host appBase=webapps name=localhost Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_log. suffix=.txt timestamp=true/ ... ... Wilson, Allen wrote: Here are the lines. Connector className=org.apache.catalina.connector.http.HttpConnector port=8080 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=2 / !-- Define an AJP 1.3 Connector on port 8009 -- Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8009 minProcessors=5 maxProcessors=75 acceptCount=10 debug=0/ Let me know if there is something that is incorrect. -Original Message- From: Emerson Cargnin [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 4:28 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat You said you can connect through port 8009 through the browser??? The jk protocol is not http, so if the configuration was allright you can't connect through 8009 as http. Maybe the error is at your server.xml... Wilson, Allen wrote: Thanks but this is on a Windows system and will not help...I am on a Solaris and I have looked at documents like this before and they still do not give me a definitive way of setting everything and testing it... Right
Re: Connecting the HTTP Server and Tomcat
I may be way off but... I don't think http://myserver.com/portal maps to /portal/* ajp13 http://myserver.com/portal/ or http://myserver.com/portal/whatever.jsp probably will, though. Give it a go, may work, Jon Wilson, Allen wrote: Bill..thanks for the reply... I will read through the link you provide but isn't that what the connector is supposed to do. My understanding what that the Apache HTTP server would detect what the request was (Java or not) and pass it on to Tomcat. Is this not what the specification of /portal/* ajp13 in the configuration does. This is what I got from the document at: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk.quickhowto.html Here is a little from one of the pages in that area... ( http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk/aphowto.html ) In a nutshell a web server is waiting for client HTTP requests. When these requests arrive the server does whatever is needed to serve the requests by providing the necessary content. Adding a servlet container may somewhat change this behavior. Now the web server needs also to perform the following: Load the servlet container adapter library and initialize it (prior to serving requests). When a request arrives, it needs to check and see if a certain request belongs to a servlet, if so it needs to let the adapter take the request and handle it. The adapter on the other hand needs to know what requests it is going to serve, usually based on some pattern in the request URL, and to where to direct these requests. Is this not correct...or am I misunderstanding it -Original Message- From: Bill Bruns [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 12:26 PM To: Tomcat Users List Subject: RE: Connecting the HTTP Server and Tomcat Allen, do you have the web server configured to throw the requests over to Tomcat? In other words, have either Proxy support or else URL Rewriting turned on in the web server? Otherwise your HTTP requests default to port 80, so they will be eaten by the web server and never reach Tomcat, since Tomcat is listening on ports that the HTTP requests do not come to by default. Have you looked at http://jakarta.apache.org/tomcat/tomcat-4.1-doc/proxy-howto.html - Bill -Original Message- From: Wilson, Allen [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 8:54 AM To: Tomcat Users List Subject: RE: Connecting the HTTP Server and Tomcat Okay...that looks similar to the tomcat 4 information I haveis your connector working correctly? -Original Message- From: Emerson Cargnin [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 6:06 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat My configuration is for tomcat 5: Service name=Catalina Connector acceptCount=100 connectionTimeout=2 disableUploadTimeout=true port=8080 redirectPort=8443 /Connector Connector port=8009 enableLookups=false redirectPort=8443 debug=0 protocol=AJP/1.3 / Engine defaultHost=localhost name=Catalina Host appBase=webapps name=localhost Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_log. suffix=.txt timestamp=true/ ... ... Wilson, Allen wrote: Here are the lines. Connector className=org.apache.catalina.connector.http.HttpConnector port=8080 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=2 / !-- Define an AJP 1.3 Connector on port 8009 -- Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8009 minProcessors=5 maxProcessors=75 acceptCount=10 debug=0/ Let me know if there is something that is incorrect. -Original Message- From: Emerson Cargnin [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 4:28 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat You said you can connect through port 8009 through the browser??? The jk protocol is not http, so if the configuration was allright you can't connect through 8009 as http. Maybe the error is at your server.xml... Wilson, Allen wrote: Thanks but this is on a Windows system and will not help...I am on a Solaris and I have looked at documents like this before and they still do not give me a definitive way of setting everything and testing it... Right now I have the HTTP server (port 80), Tomcat (port 8080), and the connector (8009) running. I even looked at the netstat to see if each port was available...and they were. When a do the home page request (http://myserver.com) it works fine...but if I request the page for the Jetspeed Portal (http://myserver.com/portal), I get an error. If I request the portal page through port 8080 it works fine. If I request the same page on 8009 it works fine. In all cases there were no entries in my mod_jk.log. I am looking for something
RE: Connecting the HTTP Server and Tomcat
No you are not way off...at least not from my point of view because that is what I thought would work. But unless I specify the port (http://myserver.com:8080/portal) it will not get there... It makes me think that the connector is not function correctly but I do not know how to tell..when I check the running ports I see the 8009 port running but it does not hand to Tomcat -Original Message- From: Jon Wingfield [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 2:09 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat I may be way off but... I don't think http://myserver.com/portal maps to /portal/* ajp13 http://myserver.com/portal/ or http://myserver.com/portal/whatever.jsp probably will, though. Give it a go, may work, Jon Wilson, Allen wrote: Bill..thanks for the reply... I will read through the link you provide but isn't that what the connector is supposed to do. My understanding what that the Apache HTTP server would detect what the request was (Java or not) and pass it on to Tomcat. Is this not what the specification of /portal/* ajp13 in the configuration does. This is what I got from the document at: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk.quickhowto.html Here is a little from one of the pages in that area... ( http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk/aphowto.html ) In a nutshell a web server is waiting for client HTTP requests. When these requests arrive the server does whatever is needed to serve the requests by providing the necessary content. Adding a servlet container may somewhat change this behavior. Now the web server needs also to perform the following: Load the servlet container adapter library and initialize it (prior to serving requests). When a request arrives, it needs to check and see if a certain request belongs to a servlet, if so it needs to let the adapter take the request and handle it. The adapter on the other hand needs to know what requests it is going to serve, usually based on some pattern in the request URL, and to where to direct these requests. Is this not correct...or am I misunderstanding it -Original Message- From: Bill Bruns [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 12:26 PM To: Tomcat Users List Subject: RE: Connecting the HTTP Server and Tomcat Allen, do you have the web server configured to throw the requests over to Tomcat? In other words, have either Proxy support or else URL Rewriting turned on in the web server? Otherwise your HTTP requests default to port 80, so they will be eaten by the web server and never reach Tomcat, since Tomcat is listening on ports that the HTTP requests do not come to by default. Have you looked at http://jakarta.apache.org/tomcat/tomcat-4.1-doc/proxy-howto.html - Bill -Original Message- From: Wilson, Allen [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 8:54 AM To: Tomcat Users List Subject: RE: Connecting the HTTP Server and Tomcat Okay...that looks similar to the tomcat 4 information I haveis your connector working correctly? -Original Message- From: Emerson Cargnin [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 6:06 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat My configuration is for tomcat 5: Service name=Catalina Connector acceptCount=100 connectionTimeout=2 disableUploadTimeout=true port=8080 redirectPort=8443 /Connector Connector port=8009 enableLookups=false redirectPort=8443 debug=0 protocol=AJP/1.3 / Engine defaultHost=localhost name=Catalina Host appBase=webapps name=localhost Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_log. suffix=.txt timestamp=true/ ... ... Wilson, Allen wrote: Here are the lines. Connector className=org.apache.catalina.connector.http.HttpConnector port=8080 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=2 / !-- Define an AJP 1.3 Connector on port 8009 -- Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8009 minProcessors=5 maxProcessors=75 acceptCount=10 debug=0/ Let me know if there is something that is incorrect. -Original Message- From: Emerson Cargnin [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 4:28 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat You said you can connect through port 8009 through the browser??? The jk protocol is not http, so if the configuration was allright you can't connect through 8009 as http. Maybe the error is at your server.xml... Wilson, Allen wrote: Thanks but this is on a Windows system and will not help
RE: Connecting the HTTP Server and Tomcat
Okay...I've read the article and the way it look is that you are doing the connection without using a connector like mod_jk. You are doing it with the proxy module...mod_proxy.so Is that correct If so, then it provides me another method to go but before I start back tracking to do something new..I would like to see if I could get the mod_jk connector working... -Original Message- From: Bill Bruns [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 2:04 PM To: Wilson, Allen; Tomcat Users List Subject: RE: Connecting the HTTP Server and Tomcat Allen, you ask isn't that what the connector is supposed to do, but the connector is in Tomcat, not in your web server. It is the web server software that is monitoring port 80, and that is where your browser sends requests to by default, so the request must get past the web server first. To do that you need to tell the web server where to send them, namely to your Tomcat port. I think this accounts for the behaviour you told about, namely that Tomcat responds fine when you specify the port number in your URL. -Bill -Original Message- From: Wilson, Allen [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 11:32 AM To: Tomcat Users List; [EMAIL PROTECTED] Subject: RE: Connecting the HTTP Server and Tomcat Bill..thanks for the reply... I will read through the link you provide but isn't that what the connector is supposed to do. My understanding what that the Apache HTTP server would detect what the request was (Java or not) and pass it on to Tomcat. Is this not what the specification of /portal/* ajp13 in the configuration does. This is what I got from the document at: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk.quickhowto.html Here is a little from one of the pages in that area... ( http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk/aphowto.html ) In a nutshell a web server is waiting for client HTTP requests. When these requests arrive the server does whatever is needed to serve the requests by providing the necessary content. Adding a servlet container may somewhat change this behavior. Now the web server needs also to perform the following: Load the servlet container adapter library and initialize it (prior to serving requests). When a request arrives, it needs to check and see if a certain request belongs to a servlet, if so it needs to let the adapter take the request and handle it. The adapter on the other hand needs to know what requests it is going to serve, usually based on some pattern in the request URL, and to where to direct these requests. Is this not correct...or am I misunderstanding it -Original Message- From: Bill Bruns [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 12:26 PM To: Tomcat Users List Subject: RE: Connecting the HTTP Server and Tomcat Allen, do you have the web server configured to throw the requests over to Tomcat? In other words, have either Proxy support or else URL Rewriting turned on in the web server? Otherwise your HTTP requests default to port 80, so they will be eaten by the web server and never reach Tomcat, since Tomcat is listening on ports that the HTTP requests do not come to by default. Have you looked at http://jakarta.apache.org/tomcat/tomcat-4.1-doc/proxy-howto.html - Bill -Original Message- From: Wilson, Allen [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 8:54 AM To: Tomcat Users List Subject: RE: Connecting the HTTP Server and Tomcat Okay...that looks similar to the tomcat 4 information I haveis your connector working correctly? -Original Message- From: Emerson Cargnin [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 6:06 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat My configuration is for tomcat 5: Service name=Catalina Connector acceptCount=100 connectionTimeout=2 disableUploadTimeout=true port=8080 redirectPort=8443 /Connector Connector port=8009 enableLookups=false redirectPort=8443 debug=0 protocol=AJP/1.3 / Engine defaultHost=localhost name=Catalina Host appBase=webapps name=localhost Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_log. suffix=.txt timestamp=true/ ... ... Wilson, Allen wrote: Here are the lines. Connector className=org.apache.catalina.connector.http.HttpConnector port=8080 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=2 / !-- Define an AJP 1.3 Connector on port 8009 -- Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8009 minProcessors=5 maxProcessors=75 acceptCount=10 debug=0/ Let me know if there is something that is incorrect. -Original Message- From: Emerson Cargnin [mailto:[EMAIL PROTECTED] Sent
Re: Connecting the HTTP Server and Tomcat
Assuming the connector is working, what effect does adding an additional mapping of /portal ajp13 to your existing /portal/* ajp13 mapping have? I just double-checked on our dev box where jk is definitely up. I got a 404 from apache for /mapping but /mapping/stuff got routed through to tomcat. Jon Wilson, Allen wrote: No you are not way off...at least not from my point of view because that is what I thought would work. But unless I specify the port (http://myserver.com:8080/portal) it will not get there... It makes me think that the connector is not function correctly but I do not know how to tell..when I check the running ports I see the 8009 port running but it does not hand to Tomcat -Original Message- From: Jon Wingfield [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 2:09 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat I may be way off but... I don't think http://myserver.com/portal maps to /portal/* ajp13 http://myserver.com/portal/ or http://myserver.com/portal/whatever.jsp probably will, though. Give it a go, may work, Jon Wilson, Allen wrote: Bill..thanks for the reply... I will read through the link you provide but isn't that what the connector is supposed to do. My understanding what that the Apache HTTP server would detect what the request was (Java or not) and pass it on to Tomcat. Is this not what the specification of /portal/* ajp13 in the configuration does. This is what I got from the document at: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk.quickhowto.html Here is a little from one of the pages in that area... ( http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk/aphowto.html ) In a nutshell a web server is waiting for client HTTP requests. When these requests arrive the server does whatever is needed to serve the requests by providing the necessary content. Adding a servlet container may somewhat change this behavior. Now the web server needs also to perform the following: Load the servlet container adapter library and initialize it (prior to serving requests). When a request arrives, it needs to check and see if a certain request belongs to a servlet, if so it needs to let the adapter take the request and handle it. The adapter on the other hand needs to know what requests it is going to serve, usually based on some pattern in the request URL, and to where to direct these requests. Is this not correct...or am I misunderstanding it -Original Message- From: Bill Bruns [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 12:26 PM To: Tomcat Users List Subject: RE: Connecting the HTTP Server and Tomcat Allen, do you have the web server configured to throw the requests over to Tomcat? In other words, have either Proxy support or else URL Rewriting turned on in the web server? Otherwise your HTTP requests default to port 80, so they will be eaten by the web server and never reach Tomcat, since Tomcat is listening on ports that the HTTP requests do not come to by default. Have you looked at http://jakarta.apache.org/tomcat/tomcat-4.1-doc/proxy-howto.html - Bill -Original Message- From: Wilson, Allen [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 8:54 AM To: Tomcat Users List Subject: RE: Connecting the HTTP Server and Tomcat Okay...that looks similar to the tomcat 4 information I haveis your connector working correctly? -Original Message- From: Emerson Cargnin [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 6:06 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat My configuration is for tomcat 5: Service name=Catalina Connector acceptCount=100 connectionTimeout=2 disableUploadTimeout=true port=8080 redirectPort=8443 /Connector Connector port=8009 enableLookups=false redirectPort=8443 debug=0 protocol=AJP/1.3 / Engine defaultHost=localhost name=Catalina Host appBase=webapps name=localhost Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_log. suffix=.txt timestamp=true/ ... ... Wilson, Allen wrote: Here are the lines. Connector className=org.apache.catalina.connector.http.HttpConnector port=8080 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=2 / !-- Define an AJP 1.3 Connector on port 8009 -- Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8009 minProcessors=5 maxProcessors=75 acceptCount=10 debug=0/ Let me know if there is something that is incorrect. -Original Message- From: Emerson Cargnin [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 4:28 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat You said you can connect through port 8009 through the browser??? The jk protocol is not http, so
RE: Connecting the HTTP Server and Tomcat
I think I may have found the problem I tried to add the line AddModule mod_jk.c in the HTTP server config and it gave an error. I could not locate the file within my HTTP or Tomcat installation.even though I have the mod_jk.so file in the libexec directory. -Original Message- From: Jon Wingfield [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 2:35 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat Assuming the connector is working, what effect does adding an additional mapping of /portal ajp13 to your existing /portal/* ajp13 mapping have? I just double-checked on our dev box where jk is definitely up. I got a 404 from apache for /mapping but /mapping/stuff got routed through to tomcat. Jon Wilson, Allen wrote: No you are not way off...at least not from my point of view because that is what I thought would work. But unless I specify the port (http://myserver.com:8080/portal) it will not get there... It makes me think that the connector is not function correctly but I do not know how to tell..when I check the running ports I see the 8009 port running but it does not hand to Tomcat -Original Message- From: Jon Wingfield [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 2:09 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat I may be way off but... I don't think http://myserver.com/portal maps to /portal/* ajp13 http://myserver.com/portal/ or http://myserver.com/portal/whatever.jsp probably will, though. Give it a go, may work, Jon Wilson, Allen wrote: Bill..thanks for the reply... I will read through the link you provide but isn't that what the connector is supposed to do. My understanding what that the Apache HTTP server would detect what the request was (Java or not) and pass it on to Tomcat. Is this not what the specification of /portal/* ajp13 in the configuration does. This is what I got from the document at: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk.quickhowto.html Here is a little from one of the pages in that area... ( http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk/aphowto.html ) In a nutshell a web server is waiting for client HTTP requests. When these requests arrive the server does whatever is needed to serve the requests by providing the necessary content. Adding a servlet container may somewhat change this behavior. Now the web server needs also to perform the following: Load the servlet container adapter library and initialize it (prior to serving requests). When a request arrives, it needs to check and see if a certain request belongs to a servlet, if so it needs to let the adapter take the request and handle it. The adapter on the other hand needs to know what requests it is going to serve, usually based on some pattern in the request URL, and to where to direct these requests. Is this not correct...or am I misunderstanding it -Original Message- From: Bill Bruns [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 12:26 PM To: Tomcat Users List Subject: RE: Connecting the HTTP Server and Tomcat Allen, do you have the web server configured to throw the requests over to Tomcat? In other words, have either Proxy support or else URL Rewriting turned on in the web server? Otherwise your HTTP requests default to port 80, so they will be eaten by the web server and never reach Tomcat, since Tomcat is listening on ports that the HTTP requests do not come to by default. Have you looked at http://jakarta.apache.org/tomcat/tomcat-4.1-doc/proxy-howto.html - Bill -Original Message- From: Wilson, Allen [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 8:54 AM To: Tomcat Users List Subject: RE: Connecting the HTTP Server and Tomcat Okay...that looks similar to the tomcat 4 information I haveis your connector working correctly? -Original Message- From: Emerson Cargnin [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 6:06 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat My configuration is for tomcat 5: Service name=Catalina Connector acceptCount=100 connectionTimeout=2 disableUploadTimeout=true port=8080 redirectPort=8443 /Connector Connector port=8009 enableLookups=false redirectPort=8443 debug=0 protocol=AJP/1.3 / Engine defaultHost=localhost name=Catalina Host appBase=webapps name=localhost Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_log. suffix=.txt timestamp=true/ ... ... Wilson, Allen wrote: Here are the lines. Connector className=org.apache.catalina.connector.http.HttpConnector port=8080 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=100 debug=0 connectionTimeout
RE: Connecting the HTTP Server and Tomcat
Hi, The rest of this thread aside, are you sure you even need Apache? Do you particular CGI/SSI/PHP scripts you need to serve in a high concurrency environment? What's your expected load? Tomcat standalone might be good enough for your needs, in which case you could drop all this connector stuff. Yoav Shapira Millennium Research Informatics -Original Message- From: Bill Bruns [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 3:04 PM To: Wilson, Allen; Tomcat Users List Subject: RE: Connecting the HTTP Server and Tomcat Allen, you ask isn't that what the connector is supposed to do, but the connector is in Tomcat, not in your web server. It is the web server software that is monitoring port 80, and that is where your browser sends requests to by default, so the request must get past the web server first. To do that you need to tell the web server where to send them, namely to your Tomcat port. I think this accounts for the behaviour you told about, namely that Tomcat responds fine when you specify the port number in your URL. -Bill -Original Message- From: Wilson, Allen [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 11:32 AM To: Tomcat Users List; [EMAIL PROTECTED] Subject: RE: Connecting the HTTP Server and Tomcat Bill..thanks for the reply... I will read through the link you provide but isn't that what the connector is supposed to do. My understanding what that the Apache HTTP server would detect what the request was (Java or not) and pass it on to Tomcat. Is this not what the specification of /portal/* ajp13 in the configuration does. This is what I got from the document at: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk.quickhowto.html Here is a little from one of the pages in that area... ( http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk/aphowto.html ) In a nutshell a web server is waiting for client HTTP requests. When these requests arrive the server does whatever is needed to serve the requests by providing the necessary content. Adding a servlet container may somewhat change this behavior. Now the web server needs also to perform the following: Load the servlet container adapter library and initialize it (prior to serving requests). When a request arrives, it needs to check and see if a certain request belongs to a servlet, if so it needs to let the adapter take the request and handle it. The adapter on the other hand needs to know what requests it is going to serve, usually based on some pattern in the request URL, and to where to direct these requests. Is this not correct...or am I misunderstanding it -Original Message- From: Bill Bruns [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 12:26 PM To: Tomcat Users List Subject: RE: Connecting the HTTP Server and Tomcat Allen, do you have the web server configured to throw the requests over to Tomcat? In other words, have either Proxy support or else URL Rewriting turned on in the web server? Otherwise your HTTP requests default to port 80, so they will be eaten by the web server and never reach Tomcat, since Tomcat is listening on ports that the HTTP requests do not come to by default. Have you looked at http://jakarta.apache.org/tomcat/tomcat-4.1-doc/proxy-howto.html - Bill -Original Message- From: Wilson, Allen [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 8:54 AM To: Tomcat Users List Subject: RE: Connecting the HTTP Server and Tomcat Okay...that looks similar to the tomcat 4 information I haveis your connector working correctly? -Original Message- From: Emerson Cargnin [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 6:06 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat My configuration is for tomcat 5: Service name=Catalina Connector acceptCount=100 connectionTimeout=2 disableUploadTimeout=true port=8080 redirectPort=8443 /Connector Connector port=8009 enableLookups=false redirectPort=8443 debug=0 protocol=AJP/1.3 / Engine defaultHost=localhost name=Catalina Host appBase=webapps name=localhost Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_log. suffix=.txt timestamp=true/ ... ... Wilson, Allen wrote: Here are the lines. Connector className=org.apache.catalina.connector.http.HttpConnector port=8080 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=2 / !-- Define an AJP 1.3 Connector on port 8009 -- Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8009 minProcessors=5 maxProcessors=75 acceptCount=10 debug=0/ Let me know if there is something that is incorrect. -Original Message- From: Emerson Cargnin [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06
RE: Connecting the HTTP Server and Tomcat
My reason for the Apache..is that I do not want root to run the Tomcat process once I put the server into production and I saw no other way for Tomcat to run on port 80 without using root.. -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 2:44 PM To: Tomcat Users List Subject: RE: Connecting the HTTP Server and Tomcat Hi, The rest of this thread aside, are you sure you even need Apache? Do you particular CGI/SSI/PHP scripts you need to serve in a high concurrency environment? What's your expected load? Tomcat standalone might be good enough for your needs, in which case you could drop all this connector stuff. Yoav Shapira Millennium Research Informatics -Original Message- From: Bill Bruns [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 3:04 PM To: Wilson, Allen; Tomcat Users List Subject: RE: Connecting the HTTP Server and Tomcat Allen, you ask isn't that what the connector is supposed to do, but the connector is in Tomcat, not in your web server. It is the web server software that is monitoring port 80, and that is where your browser sends requests to by default, so the request must get past the web server first. To do that you need to tell the web server where to send them, namely to your Tomcat port. I think this accounts for the behaviour you told about, namely that Tomcat responds fine when you specify the port number in your URL. -Bill -Original Message- From: Wilson, Allen [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 11:32 AM To: Tomcat Users List; [EMAIL PROTECTED] Subject: RE: Connecting the HTTP Server and Tomcat Bill..thanks for the reply... I will read through the link you provide but isn't that what the connector is supposed to do. My understanding what that the Apache HTTP server would detect what the request was (Java or not) and pass it on to Tomcat. Is this not what the specification of /portal/* ajp13 in the configuration does. This is what I got from the document at: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk.quickhowto.html Here is a little from one of the pages in that area... ( http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk/aphowto.html ) In a nutshell a web server is waiting for client HTTP requests. When these requests arrive the server does whatever is needed to serve the requests by providing the necessary content. Adding a servlet container may somewhat change this behavior. Now the web server needs also to perform the following: Load the servlet container adapter library and initialize it (prior to serving requests). When a request arrives, it needs to check and see if a certain request belongs to a servlet, if so it needs to let the adapter take the request and handle it. The adapter on the other hand needs to know what requests it is going to serve, usually based on some pattern in the request URL, and to where to direct these requests. Is this not correct...or am I misunderstanding it -Original Message- From: Bill Bruns [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 12:26 PM To: Tomcat Users List Subject: RE: Connecting the HTTP Server and Tomcat Allen, do you have the web server configured to throw the requests over to Tomcat? In other words, have either Proxy support or else URL Rewriting turned on in the web server? Otherwise your HTTP requests default to port 80, so they will be eaten by the web server and never reach Tomcat, since Tomcat is listening on ports that the HTTP requests do not come to by default. Have you looked at http://jakarta.apache.org/tomcat/tomcat-4.1-doc/proxy-howto.html - Bill -Original Message- From: Wilson, Allen [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 8:54 AM To: Tomcat Users List Subject: RE: Connecting the HTTP Server and Tomcat Okay...that looks similar to the tomcat 4 information I haveis your connector working correctly? -Original Message- From: Emerson Cargnin [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 6:06 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat My configuration is for tomcat 5: Service name=Catalina Connector acceptCount=100 connectionTimeout=2 disableUploadTimeout=true port=8080 redirectPort=8443 /Connector Connector port=8009 enableLookups=false redirectPort=8443 debug=0 protocol=AJP/1.3 / Engine defaultHost=localhost name=Catalina Host appBase=webapps name=localhost Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_log. suffix=.txt timestamp=true/ ... ... Wilson, Allen wrote: Here are the lines. Connector className=org.apache.catalina.connector.http.HttpConnector port=8080 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=100 debug=0 connectionTimeout
Re: Connecting the HTTP Server and Tomcat
Hi. Can you post the relevant parts of your httpd.conf file? Also, I missed this in the thread if it was mentioned, but what version of Apache are you working with? I ask, because it looks like from my setup that Apache ditched the AddModule directive in Apache 2.0.xx. LoadModule needs to be in your httpd.conf file before the AddModule directive under Apache 1.3.x as in: # All the other LoadModule directive here. LoadModule jk_module modules/mod_jk.so # Further down, all the AddModule directives here AddModule mod_jk.c It'd be helpful to see the JkWorkersFile directive, JkMount directive, and the contents of the jk workers file. --David Just tack it on to the end of the list of LoadModule directives. Then use AddModule at the end of the list of AddModule directives. Wilson, Allen wrote: I think I may have found the problem I tried to add the line AddModule mod_jk.c in the HTTP server config and it gave an error. I could not locate the file within my HTTP or Tomcat installation.even though I have the mod_jk.so file in the libexec directory. -Original Message- From: Jon Wingfield [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 2:35 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat Assuming the connector is working, what effect does adding an additional mapping of /portal ajp13 to your existing /portal/* ajp13 mapping have? I just double-checked on our dev box where jk is definitely up. I got a 404 from apache for /mapping but /mapping/stuff got routed through to tomcat. Jon Wilson, Allen wrote: No you are not way off...at least not from my point of view because that is what I thought would work. But unless I specify the port (http://myserver.com:8080/portal) it will not get there... It makes me think that the connector is not function correctly but I do not know how to tell..when I check the running ports I see the 8009 port running but it does not hand to Tomcat -Original Message- From: Jon Wingfield [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 2:09 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat I may be way off but... I don't think http://myserver.com/portal maps to /portal/* ajp13 http://myserver.com/portal/ or http://myserver.com/portal/whatever.jsp probably will, though. Give it a go, may work, Jon Wilson, Allen wrote: Bill..thanks for the reply... I will read through the link you provide but isn't that what the connector is supposed to do. My understanding what that the Apache HTTP server would detect what the request was (Java or not) and pass it on to Tomcat. Is this not what the specification of /portal/* ajp13 in the configuration does. This is what I got from the document at: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk.quickhowto.html Here is a little from one of the pages in that area... ( http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk/aphowto.html ) In a nutshell a web server is waiting for client HTTP requests. When these requests arrive the server does whatever is needed to serve the requests by providing the necessary content. Adding a servlet container may somewhat change this behavior. Now the web server needs also to perform the following: Load the servlet container adapter library and initialize it (prior to serving requests). When a request arrives, it needs to check and see if a certain request belongs to a servlet, if so it needs to let the adapter take the request and handle it. The adapter on the other hand needs to know what requests it is going to serve, usually based on some pattern in the request URL, and to where to direct these requests. Is this not correct...or am I misunderstanding it -Original Message- From: Bill Bruns [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 12:26 PM To: Tomcat Users List Subject: RE: Connecting the HTTP Server and Tomcat Allen, do you have the web server configured to throw the requests over to Tomcat? In other words, have either Proxy support or else URL Rewriting turned on in the web server? Otherwise your HTTP requests default to port 80, so they will be eaten by the web server and never reach Tomcat, since Tomcat is listening on ports that the HTTP requests do not come to by default. Have you looked at http://jakarta.apache.org/tomcat/tomcat-4.1-doc/proxy-howto.html - Bill -Original Message- From: Wilson, Allen [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 8:54 AM To: Tomcat Users List Subject: RE: Connecting the HTTP Server and Tomcat Okay...that looks similar to the tomcat 4 information I haveis your connector working correctly? -Original Message- From: Emerson Cargnin [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 6:06 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server
RE: Connecting the HTTP Server and Tomcat
No a problem...I am using 2.0.48.. I have the LoadModule line and the other directives here...they are LoadModule jk_module /usr/WWW/libexec/mod_jk.so JkWorkersFile /usr/tomcat-4.1.18/conf/jk/workers.properties JkLogFile /usr/tomcat-4.1.18/logs/mod_jk.log JkLogLeveldebug JkMount /portal/* ajp13 I was unable to put in the AddModule line because I did not see it (the mod_jk.c file) loaded when I did the apachectl -l. I am working on getting that loaded now -Original Message- From: David Smith [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 3:19 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat Hi. Can you post the relevant parts of your httpd.conf file? Also, I missed this in the thread if it was mentioned, but what version of Apache are you working with? I ask, because it looks like from my setup that Apache ditched the AddModule directive in Apache 2.0.xx. LoadModule needs to be in your httpd.conf file before the AddModule directive under Apache 1.3.x as in: # All the other LoadModule directive here. LoadModule jk_module modules/mod_jk.so # Further down, all the AddModule directives here AddModule mod_jk.c It'd be helpful to see the JkWorkersFile directive, JkMount directive, and the contents of the jk workers file. --David Just tack it on to the end of the list of LoadModule directives. Then use AddModule at the end of the list of AddModule directives. Wilson, Allen wrote: I think I may have found the problem I tried to add the line AddModule mod_jk.c in the HTTP server config and it gave an error. I could not locate the file within my HTTP or Tomcat installation.even though I have the mod_jk.so file in the libexec directory. -Original Message- From: Jon Wingfield [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 2:35 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat Assuming the connector is working, what effect does adding an additional mapping of /portalajp13 to your existing /portal/* ajp13 mapping have? I just double-checked on our dev box where jk is definitely up. I got a 404 from apache for /mapping but /mapping/stuff got routed through to tomcat. Jon Wilson, Allen wrote: No you are not way off...at least not from my point of view because that is what I thought would work. But unless I specify the port (http://myserver.com:8080/portal) it will not get there... It makes me think that the connector is not function correctly but I do not know how to tell..when I check the running ports I see the 8009 port running but it does not hand to Tomcat -Original Message- From: Jon Wingfield [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 2:09 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat I may be way off but... I don't think http://myserver.com/portal maps to /portal/* ajp13 http://myserver.com/portal/ or http://myserver.com/portal/whatever.jsp probably will, though. Give it a go, may work, Jon Wilson, Allen wrote: Bill..thanks for the reply... I will read through the link you provide but isn't that what the connector is supposed to do. My understanding what that the Apache HTTP server would detect what the request was (Java or not) and pass it on to Tomcat. Is this not what the specification of /portal/* ajp13 in the configuration does. This is what I got from the document at: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk.quickhowto.htm l Here is a little from one of the pages in that area... ( http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk/aphowto.html ) In a nutshell a web server is waiting for client HTTP requests. When these requests arrive the server does whatever is needed to serve the requests by providing the necessary content. Adding a servlet container may somewhat change this behavior. Now the web server needs also to perform the following: Load the servlet container adapter library and initialize it (prior to serving requests). When a request arrives, it needs to check and see if a certain request belongs to a servlet, if so it needs to let the adapter take the request and handle it. The adapter on the other hand needs to know what requests it is going to serve, usually based on some pattern in the request URL, and to where to direct these requests. Is this not correct...or am I misunderstanding it -Original Message- From: Bill Bruns [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 12:26 PM To: Tomcat Users List Subject: RE: Connecting the HTTP Server and Tomcat Allen, do you have the web server configured to throw the requests over to Tomcat? In other words, have either Proxy support or else URL Rewriting turned on in the web server? Otherwise your HTTP requests default to port 80, so they will be eaten
RE: Connecting the HTTP Server and Tomcat
Hi, My reason for the Apache..is that I do not want root to run the Tomcat process once I put the server into production and I saw no other way for Tomcat to run on port 80 without using root.. Use commons-daemon for this. It ships with tomcat5 and works with tomcat4 as well: http://jakarta.apache.org/commons/daemon/index.html. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Connecting the HTTP Server and Tomcat
Yes...I think this is a better route to go...I will try it...thanks -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 3:43 PM To: Tomcat Users List Subject: RE: Connecting the HTTP Server and Tomcat Hi, My reason for the Apache..is that I do not want root to run the Tomcat process once I put the server into production and I saw no other way for Tomcat to run on port 80 without using root.. Use commons-daemon for this. It ships with tomcat5 and works with tomcat4 as well: http://jakarta.apache.org/commons/daemon/index.html. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message may contain proprietary or confidential company information. Any unauthorized use or disclosure is prohibited. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Connecting the HTTP Server and Tomcat
Hi Currently I use catalina.sh start | stop to control tomcat 4.1.x and 5.0.x running as root. Can I change it easily to use commons-daemon (running as non-root)? A lot of command line options are set in catalina.sh. Would I need to do this manually ? Regards, Steffen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Connecting the HTTP Server and Tomcat
Allen, thanks for pointing me at mod_jk. It works better than proxy or rewrite! I've implemented it here now on Apache 2.0 (under WinXP) connected to Tomcat 4.1.24 (Solaris). with mod_jk 1.2.5. Works great! In case it helps, I'll attach my config files: Tomcat's server.xml: - Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8113 minProcessors=5 maxProcessors=75 acceptCount=10 debug=20/ workers.properties: --- # Define 1 real worker using ajp13 worker.list=worker1 # Set properties for worker1 (ajp13) worker.worker1.type=ajp13 worker.worker1.host=192.168.1.62 worker.worker1.port=8113 worker.worker1.lbfactor=50 worker.worker1.cachesize=10 worker.worker1.cache_timeout=600 worker.worker1.socket_keepalive=1 worker.worker1.socket_timeout=300 Apache httpd.conf: -- # # Entries for connection to Tomcat # Load mod_jk module # Update this path to match your modules location LoadModule jk_module modules/mod_jk.dll # Declare the module for IfModule directive #AddModule mod_jk2.c # Where to find workers.properties # Update this path to match your conf directory location (put workers.properties next to httpd.conf) JkWorkersFile C:\Program Files\Apache Group\Apache2\conf\workers.properties # Where to put jk logs # Update this path to match your logs directory location (put mod_jk.log next to access_log) #JkLogFile /var/log/httpd/mod_jk.log # Set the jk log level [debug/error/info] #JkLogLevel info # Select the log format #JkLogStampFormat [%a %b %d %H:%M:%S %Y] # JkOptions indicate to send SSL KEY SIZE, #JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories # JkRequestLogFormat set the request format #JkRequestLogFormat %w %V %T # Send everything for context /examples to worker named worker1 (ajp13) JkMount /fitmesite/* worker1 jkMount /soap/* worker1 # # end of Tomcat connection info -Original Message- From: David Smith [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 1:19 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat Hi. Can you post the relevant parts of your httpd.conf file? Also, I missed this in the thread if it was mentioned, but what version of Apache are you working with? I ask, because it looks like from my setup that Apache ditched the AddModule directive in Apache 2.0.xx. LoadModule needs to be in your httpd.conf file before the AddModule directive under Apache 1.3.x as in: # All the other LoadModule directive here. LoadModule jk_module modules/mod_jk.so # Further down, all the AddModule directives here AddModule mod_jk.c It'd be helpful to see the JkWorkersFile directive, JkMount directive, and the contents of the jk workers file. --David Just tack it on to the end of the list of LoadModule directives. Then use AddModule at the end of the list of AddModule directives. Wilson, Allen wrote: I think I may have found the problem I tried to add the line AddModule mod_jk.c in the HTTP server config and it gave an error. I could not locate the file within my HTTP or Tomcat installation.even though I have the mod_jk.so file in the libexec directory. -Original Message- From: Jon Wingfield [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 2:35 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat Assuming the connector is working, what effect does adding an additional mapping of /portalajp13 to your existing /portal/* ajp13 mapping have? I just double-checked on our dev box where jk is definitely up. I got a 404 from apache for /mapping but /mapping/stuff got routed through to tomcat. Jon Wilson, Allen wrote: No you are not way off...at least not from my point of view because that is what I thought would work. But unless I specify the port (http://myserver.com:8080/portal) it will not get there... It makes me think that the connector is not function correctly but I do not know how to tell..when I check the running ports I see the 8009 port running but it does not hand to Tomcat -Original Message- From: Jon Wingfield [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 2:09 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat I may be way off but... I don't think http://myserver.com/portal maps to /portal/* ajp13 http://myserver.com/portal/ or http://myserver.com/portal/whatever.jsp probably will, though. Give it a go, may work, Jon Wilson, Allen wrote: Bill..thanks for the reply... I will read through the link you provide but isn't that what the connector is supposed to do. My understanding what that the Apache HTTP server would detect what the request was (Java or not) and pass it on to Tomcat. Is this not what the specification of /portal/* ajp13 in the configuration does
RE: Connecting the HTTP Server and Tomcat
Good evening.. Check this out http://johnturner.com/howto/apache2-tomcat4127-jk-rh9-howto.html --- regards, Anatol Pomozov EPAM Systems phone: +375 (17) 210-1662 ext. 1373 -Original Message- From: Wilson, Allen [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 6:42 PM To: Tomcat Users List Subject: Connecting the HTTP Server and Tomcat Good morning Can any provide some assistance on connecting the HTTP server and Tomcat together. I am using HTTP Server 2.0.48 and Tomcat-4.1.18 on a Sun Solaris machine. I think I have everything in place but when the only way I can reach the Tomcat stuff is my specifying the port number in the URL. Can someone point me in the direction of some How to connect Apache and Tomcat for Dummies instructions that will provide me some clear steps and methods for checking everything out. Thanks...and any help is appreciated. Allen
RE: Connecting the HTTP Server and Tomcat
http://www.greenfieldresearch.ca/technical/jk2_config.html This was a really good starting point. Ignore the fact it talks abut windows, I imstaled on SuSE8.2 using apache2.0.48 and both tomcat 4 and 5 Kevan -Original Message- From: Wilson, Allen [mailto:[EMAIL PROTECTED] Sent: 06 April 2004 16:42 To: Tomcat Users List Subject: Connecting the HTTP Server and Tomcat Good morning Can any provide some assistance on connecting the HTTP server and Tomcat together. I am using HTTP Server 2.0.48 and Tomcat-4.1.18 on a Sun Solaris machine. I think I have everything in place but when the only way I can reach the Tomcat stuff is my specifying the port number in the URL. Can someone point me in the direction of some How to connect Apache and Tomcat for Dummies instructions that will provide me some clear steps and methods for checking everything out. Thanks...and any help is appreciated. Allen
RE: Connecting the HTTP Server and Tomcat
Thanks but this is on a Windows system and will not help...I am on a Solaris and I have looked at documents like this before and they still do not give me a definitive way of setting everything and testing it... Right now I have the HTTP server (port 80), Tomcat (port 8080), and the connector (8009) running. I even looked at the netstat to see if each port was available...and they were. When a do the home page request (http://myserver.com) it works fine...but if I request the page for the Jetspeed Portal (http://myserver.com/portal), I get an error. If I request the portal page through port 8080 it works fine. If I request the same page on 8009 it works fine. In all cases there were no entries in my mod_jk.log. I am looking for something that will outline the steps for me on a Solaris machine or at least give me a better way to diagnose what I am doing wrong -Original Message- From: kwilding [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 10:55 AM To: 'Tomcat Users List' Subject: RE: Connecting the HTTP Server and Tomcat http://www.greenfieldresearch.ca/technical/jk2_config.html This was a really good starting point. Ignore the fact it talks abut windows, I imstaled on SuSE8.2 using apache2.0.48 and both tomcat 4 and 5 Kevan -Original Message- From: Wilson, Allen [mailto:[EMAIL PROTECTED] Sent: 06 April 2004 16:42 To: Tomcat Users List Subject: Connecting the HTTP Server and Tomcat Good morning Can any provide some assistance on connecting the HTTP server and Tomcat together. I am using HTTP Server 2.0.48 and Tomcat-4.1.18 on a Sun Solaris machine. I think I have everything in place but when the only way I can reach the Tomcat stuff is my specifying the port number in the URL. Can someone point me in the direction of some How to connect Apache and Tomcat for Dummies instructions that will provide me some clear steps and methods for checking everything out. Thanks...and any help is appreciated. Allen This message may contain proprietary or confidential company information. Any unauthorized use or disclosure is prohibited. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Connecting the HTTP Server and Tomcat
You said you can connect through port 8009 through the browser??? The jk protocol is not http, so if the configuration was allright you can't connect through 8009 as http. Maybe the error is at your server.xml... Wilson, Allen wrote: Thanks but this is on a Windows system and will not help...I am on a Solaris and I have looked at documents like this before and they still do not give me a definitive way of setting everything and testing it... Right now I have the HTTP server (port 80), Tomcat (port 8080), and the connector (8009) running. I even looked at the netstat to see if each port was available...and they were. When a do the home page request (http://myserver.com) it works fine...but if I request the page for the Jetspeed Portal (http://myserver.com/portal), I get an error. If I request the portal page through port 8080 it works fine. If I request the same page on 8009 it works fine. In all cases there were no entries in my mod_jk.log. I am looking for something that will outline the steps for me on a Solaris machine or at least give me a better way to diagnose what I am doing wrong -Original Message- From: kwilding [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 10:55 AM To: 'Tomcat Users List' Subject: RE: Connecting the HTTP Server and Tomcat http://www.greenfieldresearch.ca/technical/jk2_config.html This was a really good starting point. Ignore the fact it talks abut windows, I imstaled on SuSE8.2 using apache2.0.48 and both tomcat 4 and 5 Kevan -Original Message- From: Wilson, Allen [mailto:[EMAIL PROTECTED] Sent: 06 April 2004 16:42 To: Tomcat Users List Subject: Connecting the HTTP Server and Tomcat Good morning Can any provide some assistance on connecting the HTTP server and Tomcat together. I am using HTTP Server 2.0.48 and Tomcat-4.1.18 on a Sun Solaris machine. I think I have everything in place but when the only way I can reach the Tomcat stuff is my specifying the port number in the URL. Can someone point me in the direction of some How to connect Apache and Tomcat for Dummies instructions that will provide me some clear steps and methods for checking everything out. Thanks...and any help is appreciated. Allen This message may contain proprietary or confidential company information. Any unauthorized use or disclosure is prohibited. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Emerson Cargnin Analista de Sistemas Setor de Desenvolvimento de Sistemas - TRE-SC tel : (048) - 251-3700 - Ramal 3181 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Connecting the HTTP Server and Tomcat
Here are the lines. Connector className=org.apache.catalina.connector.http.HttpConnector port=8080 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=2 / !-- Define an AJP 1.3 Connector on port 8009 -- Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8009 minProcessors=5 maxProcessors=75 acceptCount=10 debug=0/ Let me know if there is something that is incorrect. -Original Message- From: Emerson Cargnin [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 4:28 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat You said you can connect through port 8009 through the browser??? The jk protocol is not http, so if the configuration was allright you can't connect through 8009 as http. Maybe the error is at your server.xml... Wilson, Allen wrote: Thanks but this is on a Windows system and will not help...I am on a Solaris and I have looked at documents like this before and they still do not give me a definitive way of setting everything and testing it... Right now I have the HTTP server (port 80), Tomcat (port 8080), and the connector (8009) running. I even looked at the netstat to see if each port was available...and they were. When a do the home page request (http://myserver.com) it works fine...but if I request the page for the Jetspeed Portal (http://myserver.com/portal), I get an error. If I request the portal page through port 8080 it works fine. If I request the same page on 8009 it works fine. In all cases there were no entries in my mod_jk.log. I am looking for something that will outline the steps for me on a Solaris machine or at least give me a better way to diagnose what I am doing wrong -Original Message- From: kwilding [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 10:55 AM To: 'Tomcat Users List' Subject: RE: Connecting the HTTP Server and Tomcat http://www.greenfieldresearch.ca/technical/jk2_config.html This was a really good starting point. Ignore the fact it talks abut windows, I imstaled on SuSE8.2 using apache2.0.48 and both tomcat 4 and 5 Kevan -Original Message- From: Wilson, Allen [mailto:[EMAIL PROTECTED] Sent: 06 April 2004 16:42 To: Tomcat Users List Subject: Connecting the HTTP Server and Tomcat Good morning Can any provide some assistance on connecting the HTTP server and Tomcat together. I am using HTTP Server 2.0.48 and Tomcat-4.1.18 on a Sun Solaris machine. I think I have everything in place but when the only way I can reach the Tomcat stuff is my specifying the port number in the URL. Can someone point me in the direction of some How to connect Apache and Tomcat for Dummies instructions that will provide me some clear steps and methods for checking everything out. Thanks...and any help is appreciated. Allen This message may contain proprietary or confidential company information. Any unauthorized use or disclosure is prohibited. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Emerson Cargnin Analista de Sistemas Setor de Desenvolvimento de Sistemas - TRE-SC tel : (048) - 251-3700 - Ramal 3181 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message may contain proprietary or confidential company information. Any unauthorized use or disclosure is prohibited. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Connecting the HTTP Server and Tomcat
My configuration is for tomcat 5: Service name=Catalina Connector acceptCount=100 connectionTimeout=2 disableUploadTimeout=true port=8080 redirectPort=8443 /Connector Connector port=8009 enableLookups=false redirectPort=8443 debug=0 protocol=AJP/1.3 / Engine defaultHost=localhost name=Catalina Host appBase=webapps name=localhost Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_log. suffix=.txt timestamp=true/ ... ... Wilson, Allen wrote: Here are the lines. Connector className=org.apache.catalina.connector.http.HttpConnector port=8080 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=2 / !-- Define an AJP 1.3 Connector on port 8009 -- Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8009 minProcessors=5 maxProcessors=75 acceptCount=10 debug=0/ Let me know if there is something that is incorrect. -Original Message- From: Emerson Cargnin [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 4:28 PM To: Tomcat Users List Subject: Re: Connecting the HTTP Server and Tomcat You said you can connect through port 8009 through the browser??? The jk protocol is not http, so if the configuration was allright you can't connect through 8009 as http. Maybe the error is at your server.xml... Wilson, Allen wrote: Thanks but this is on a Windows system and will not help...I am on a Solaris and I have looked at documents like this before and they still do not give me a definitive way of setting everything and testing it... Right now I have the HTTP server (port 80), Tomcat (port 8080), and the connector (8009) running. I even looked at the netstat to see if each port was available...and they were. When a do the home page request (http://myserver.com) it works fine...but if I request the page for the Jetspeed Portal (http://myserver.com/portal), I get an error. If I request the portal page through port 8080 it works fine. If I request the same page on 8009 it works fine. In all cases there were no entries in my mod_jk.log. I am looking for something that will outline the steps for me on a Solaris machine or at least give me a better way to diagnose what I am doing wrong -Original Message- From: kwilding [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 10:55 AM To: 'Tomcat Users List' Subject: RE: Connecting the HTTP Server and Tomcat http://www.greenfieldresearch.ca/technical/jk2_config.html This was a really good starting point. Ignore the fact it talks abut windows, I imstaled on SuSE8.2 using apache2.0.48 and both tomcat 4 and 5 Kevan -Original Message- From: Wilson, Allen [mailto:[EMAIL PROTECTED] Sent: 06 April 2004 16:42 To: Tomcat Users List Subject: Connecting the HTTP Server and Tomcat Good morning Can any provide some assistance on connecting the HTTP server and Tomcat together. I am using HTTP Server 2.0.48 and Tomcat-4.1.18 on a Sun Solaris machine. I think I have everything in place but when the only way I can reach the Tomcat stuff is my specifying the port number in the URL. Can someone point me in the direction of some How to connect Apache and Tomcat for Dummies instructions that will provide me some clear steps and methods for checking everything out. Thanks...and any help is appreciated. Allen This message may contain proprietary or confidential company information. Any unauthorized use or disclosure is prohibited. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message may contain proprietary or confidential company information. Any unauthorized use or disclosure is prohibited. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Emerson Cargnin Analista de Sistemas Setor de Desenvolvimento de Sistemas - TRE-SC tel : (048) - 251-3700 - Ramal 3181 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
