Re: Getting Apache2 forwarding to tomcat5
Hello,
1) It is recommended to use mod_jk version 1 as version 2 is deprecated and
anything that is new in version 2 has been rolled into version 1.
2) All you need is this in server.xml:
!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 --
Connector port=8009
enableLookups=false redirectPort=8443 debug=0
protocol=AJP/1.3 /
You may comment out the sections about 8080 and 8443 as apache talks to tomcat
through 8009.
3) If you insist on using mod_jk version 2, here are sample config files that
worked for me:
In httpd.conf:
LoadModule jk2_module /usr/local/apache/modules/mod_jk2.so
JkSet config.file /usr/local/apache/config/workers2.properties
JkSet shm:file /usr/local/apache/logs/shm.file
JkSet shm:size 1048576
JkSet shm:disabled 0
In workers2.properties:
[channel.socket:server.domain.com:8009]
info=Ajp13 forwarding over socket
port=8009
host=server.domain.com
[ajp13:server.domain.com:8009]
channel=channel.socket:server.domain.com:8009
[uri:/*.jsp]
worker=ajp13:server.domain.com:8009
--
Lyndon Tiu
On Tue, 11 Oct 2005 18:22:21 -0500 tomcat-user@jakarta.apache.org wrote:
I have read about 25 different websites on getting this setup. I have
read through this list trying to find the answer I need. I have spent
the last 2 days and soon 3rd day trying to get this working. I need
Apache to forward port 80 and 443 requests to tomcat to 8080 and 8443. I
am working on the non-ssl right now. I get an error in Apache error_log
saying:
[error] uriEnv.init() map to invalid worker /*.jsp-0
ajp13:localhost:8009
[error] uriEnv.init() map to invalid worker /patientC
onnect-1 ajp13:localhost:8009
Let me give a bit of history and config files.
This is running on SLES9 x86-64 version.
Apache and tomcat and the connectors are from RPMs that came with SuSE.
Everything is installed in SuSE default install location.
httpd.conf.local:
LoadModule jk2_module /usr/lib64/apache2/mod_jk2.so
Location /*.jsp
JkUriSet worker ajp13:localhost:8009
/Location
Location /patientConnect
JkUriSet worker ajp13:localhost:8009
/Location
workers2.properties:
[logger]
level=DEBUG
[config:]
file=/etc/apache2/workers2.properties
debug=0
debugEnv=0
[uriMap:]
info=Maps the requests. Options: debug
debug=1
[shm]
info=Scoreboard. Required for reconfiguration and status with
multiprocess serve
rs
file=/usr/share/tomcat/logs/jk2.shm
size=1048576
debug=0
disabled=0
[workerEnv:]
info=Global server options
timing=1
debug=0
[status:]
info=Status worker, displays runtime informations
[uri:patientconnect.truchart.com/jkstatus/*]
info=Display status information and checks the config file for changes.
group=status:
[channel.socket:localhost:8009]
info=Ajp13 forwarding over socket
# Define the worker
[ajp13:localhost:8009]
channel=channel.socket:localhost:8009
[uri:patientconnect.truchart.com/patientConnect/*]
info=patientConnect
Both the workers2.properties and the httpd.conf.local are located
in /etc/apache2 directory.
In the /usr/share/tomcat/conf/ directory is the jk2.properties and the
server.xml
jk2.properties:
## THIS FILE MAY BE OVERRIDEN AT RUNTIME. MAKE SURE TOMCAT IS STOPED
## WHEN YOU EDIT THE FILE.
## COMMENTS WILL BE _LOST_
## DOCUMENTATION OF THE FORMAT IN JkMain javadoc.
# Set the desired handler list
# handler.list=apr,request,channelJni
#
# Override the default port for the socketChannel
channelSocket.port=8009
# Default:
# channelUnix.file=${jkHome}/work/jk2.socket
# Just to check if the the config is working
# shm.file=${jkHome}/work/jk2.shm
# In order to enable jni use any channelJni directive
# channelJni.disabled = 0
# And one of the following directives:
# apr.jniModeSo=/opt/apache2/modules/mod_jk2.so
# If set to inprocess the mod_jk2 will Register natives itself
# This will enable the starting of the Tomcat from mod_jk2
# apr.jniModeSo=inprocess
and the server.xml that was modified:
!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 --
Connector port=8080
maxThreads=150 minSpareThreads=25
maxSpareThreads=75
enableLookups=false redirectPort=8443
acceptCount=100
debug=0 connectionTimeout=2
disableUploadTimeout=true /
!-- Note : To disable connection timeouts, set connectionTimeout
value
to 0 --
!-- Note : To use gzip compression you could set the following
properti
es :
compression=on
compressionMinSize=2048
noCompressionUserAgents=gozilla, traviata
compressableMimeType=text/html,text/xml
--
!-- Define a SSL Coyote HTTP/1.1 Connector on port 8443 --
!--
Connector port=8443
maxThreads=150 minSpareThreads=25
maxSpareThreads=75
enableLookups=false
Re: apache -- tomcat (mod_jk) works on localhost but not other hosts
On Mon, 10 Oct 2005 09:01:04 -0700 (PDT) tomcat-user@jakarta.apache.org wrote: I'm very new to tomcat and apache. I've set up apache to forward to tomcat using mod_jk. It works fine on the localhost, but if I try to connect through to tomcat from any other host I get 404 file not found, Please send us your workers.properties and httpd.conf. -- Lyndon Tiu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: apache question [255819:132349]
Google is your friend. also, to get you started: http://jakarta.apache.org/tomcat/connectors-doc/index.html On Fri, 7 Oct 2005 17:39:34 0100 tomcat-user@jakarta.apache.org wrote: -Original Message- From: peter thesing [EMAIL PROTECTED] Received: 10/7/2005 5:38 PM To: tomcat-user@jakarta.apache.org Subject: apache question Hi All. Perhaps has this question answered in previous mails but i could not find it. I would like to put this question to the list... At home i have 2 webservers running . the one of my partner (iis) on port 80 and mine at port 8000. I would like to continue with Apache2 because it supports php. perl and so on and i have build my website around it. What i want to do is to include java server applets using jakarta tomcat but without disabling Apache2. Can this be done and if so how? What additional configuration needs to be done to let's say httpd.conf Thanks in advance Peter ps since apache has no means, that i can discover, to answer this technical question perhaps someone on the list can direct me to the proper way Thanks ;P - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Meridian Club Unit 5, Caxton Centre Porters Wood St Albans Herts UNITED KINGDOM AL3 6XT Tel: +44 1727 738855 Fax: +44 1700 578955 email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Lyndon Tiu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: tomcat and firefox ssl problem - no common encryption algorithms
On Thu, 22 Sep 2005 14:40:25 0100 [EMAIL PROTECTED] wrote: Lyndon Tiu wrote: Hello, I am using on server: - Tomcat 5.5.9 downloaded from Apache Tomcat website. - Tried both Java 1.4.2_09(using tomcat compat packages) and Java 1.5.0_03 - RH ES3 on client: - Firefox 1.0.6 - RH WS3 I have done ssl on Tomcat 4.x and 5.0.x a few times before with no problems and I am surprised to find this issue today. No error messages in Tomcat logs but Firefox complains about: Firefox and server host name cannot cummunicate securely because they have no common encryption algorithms. Have you set up a keystore with at least a self-signed certificate? Yes. Have you explicitly set the sslProtocol attribute in your SSL connector (despite the docs this is necessary in 5.5.9, fixed thereafter) Connector ... sslProtocol=TLS ... Yes. Have you tried another browser in case you get a more helpful message (what Firefox said is not true)? IE 6. Gave me that generic page cannot be displayed error. cheers As I said, I have done this successfully before and I am baffled that it is not working fo me now. Thanks. Paul Singleton -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.11.4/109 - Release Date: 21/Sep/2005 -- Lyndon Tiu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: tomcat and firefox ssl problem - no common encryption algorithms
Problem solved. I was generating ssl certs with openssl and apparently, I needed to use keytool. Thanks. On Thu, 22 Sep 2005 09:03:52 -0700 tomcat-user@jakarta.apache.org wrote: As I said, I have done this successfully before and I am baffled that it is not working fo me now. Perhaps you need send your server.xml along so others can see what you've done. It definitely works with Firefox and IE on 5.5.9 David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Lyndon Tiu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
tomcat and firefox ssl problem - no common encryption algorithms
Hello, I am using on server: - Tomcat 5.5.9 downloaded from Apache Tomcat website. - Tried both Java 1.4.2_09(using tomcat compat packages) and Java 1.5.0_03 - RH ES3 on client: - Firefox 1.0.6 - RH WS3 I have done ssl on Tomcat 4.x and 5.0.x a few times before with no problems and I am surprised to find this issue today. No error messages in Tomcat logs but Firefox complains about: Firefox and server host name cannot cummunicate securely because they have no common encryption algorithms. I have researched Google but there doesn't seem to be any straight answer. Any ideas? Thank you. -- Lyndon Tiu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
