Problem with mod_jk2 modifying the port numbers of original URL
Apache 2.0.50/mod_jk2 2.0.4/Linux/Tomcat5 Hello, in this deployment scenario a request is coming in on standard port 80, is forwarded to Apache listening on port 8000 and then forwarded to Tomcat through mod_jk2. Everything worked well until Apache port was changed from 80 to 8000. Suddenly Tomcat started to see URLs with port number 8000 added, though the original request was still addressed to the same externally visible standard port. Finally we found that mod_jk2 is rewriting the URL to include the Apache port number 8000. Normally I would expect the URL to remain as seen in the browser, regardless through which ports and proxy servers it passes before it arrives at the destinaion. We could not find a way to control this behavior through the worker2.properties, do we actually have to tweak the mod_jk2 source code? Is this the intended behavior? The problem I'm stuck here is that the applciation can no longer determine the URL sent by the browser. Any help greatly appreciated, Tim _ Overwhelmed by debt? Find out how to Dig Yourself Out of Debt from MSN Money. http://special.msn.com/money/0407debt.armx - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
one great problem with mod_jk2 and workers2.properties
I have configure the tomcat + apache2 + mod_jk2 but i have find one great problem (error?) and is this: if i have this web structure: / |-index.jsp |-images/ | |-image.gif | |-otherimage.gif |-js/ | |-file.js |-otherdirectory/ | |-file1.htm | |-file2.png |-WEB-INF there is one great problem if one jsp page has images or other files that are into (inside) one directory. if i not map the directories into the workers2.properties file the sistem doesn't show well the page. if i not writte into the workers2.properties file: [uri:www.domain.com/*.jsp] worker_ajp:localhost:8009 [uri:www.domain.com/images/*] worker_ajp:localhost:8009 [uri:www.doamin.com/js/*] worker_ajp:localhost:8009 .. this has one great problem an dis that if one use, using ftp, creates one dir and files, the system'll not show well the pages. How can i solve this great (form me) problem? thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with mod_jk2
Ok, I'm still pretty new to Tomcat and mod_jk2, but here's how I understand it: The mod_jk2 doesn't take any config arguments from the apache conf file. I think those arguments you're using are for mod_jk (not mod_jk2). As I understand it mod_jk2 will look for its config file when it's loaded in apache. That file is workers.properties, and (on my config anyway) it sits in the same dir as httpd.conf. Use workers.properties to specify how and when mod_jk2 should intercept page requests, and where they should be sent. The jk2.properties file sits in tomcat's config dir, and is used to give the tomcat side of mod_jk2 special instructions on how it should expect its connection. With the default setup I don't think jk2.properties needs to have any actual config lines in it (everything comes commented out by default). If push came to shove I imagine you could find a httpd.conf config parameter that would tell mod_jk2 where to find its workers.properties. I don't know what that parameter is, so for now I just use the default path and filename, and mod_jk2 seems to find the file easily enough. My personal tomcat/apache/jk2 headache has been because I tried to switch from the default mod_jk2 connection type (TCP sockets) to a more efficient option (unix sockets), but that's a tale of woe for another day. Sam - Original Message - From: Andrew Davis [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, November 05, 2003 5:36 PM Subject: Problem with mod_jk2 Two prefaces... 1) I hope this is the right list. I didn't see one specifically for mod_jk/mod_jk2. 2) I've read all the doc's I can find. I've been reading and trying for the last two days. Please don't send me replies telling me to RTM. The whole reason for my post is that I'm stuck and think I'm dealing with mod_jk docs not being updated for mod_jk2. I have a RH Linux ES 2.1 server. It has apache 1.3.27 installed via RH's up2date. I also have mod_ssl, and a few other mod's. The apache part is up and running correctly on non-standard ports, but I've tested it with local telnets and remotely through a web-browser. Our original configuration on the server was just pure Tomcat (4.1.27) listening on port 80. We wanted to add SSL support (port 443) and split our services at the same time, allowing us to later have Tomcat and Apache on different servers, hence why I installed Apache. I've spent the last two days reading the relevant portions of WROX's Professional Apache Tomcat and loads of information on the jakarta.apache.org site. Unfortunately, it seems that a lot of the docs (and my book) are still referencing mod_jk syntax options and causing me confusion trying to use mod_jk2. My apache and mod_ssl are from RPM, not source. My Tomcat (ver. 4.1.27... need to get this working before going to 4.1.29) is from a binary (jakarta-tomcat-4.1.27.tar.gz). My mod_jk2 is from jakarta-tomcat-connectors-jk2-src-current.tar.gz and was built by cd'ing into ~/jk/native2, then running 'buildconf.sh' and then 'configure --with-apxs=/usr/sbin/apxs'. The file mod_jk2.so was created and I copied it to my modules directory (/usr/lib/apache - stock on RH ES 2.1). I have the following in my server.xml: !-- 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/ I've created a workers.properties file in /usr/jakarta-tomcat-4.1.27/conf/jk. It looks like this: # Setting variables workers.tomcat_home=/usr/tomcat workers.java_home=/usr/java/j2sdk1.4.1_04 ps=/ worker.list=TomcatWorker1 # Settings for TomcatWorker1 worker worker.TomcatWorker1.port=8009 worker.TomcatWorker1.host=localhost worker.TomcatWorker1.type=ajp13 Lastly, I've added the following to the end of my httpd.conf: # Load mod_jk2 LoadModule jk2_module modules/mod_jk2.so # Configure mod_jk2 JkWorkersFile /etc/httpd/conf/workers2.properties JkLogFile /var/log/httpd/mod_jk.log JkLogLevel info JkMount /usr/tomcat/webapps/Genvault/*.jsp TomcatWorker1 Here's my problem. When I run apachectl configtest, I get: [Wed Nov 05 23:27:15 2003] ( info) [mod_jk2.c (208)]: Set serverRoot /etc/httpd Create config for main host Syntax error on line 1499 of /etc/httpd/conf/httpd.conf: Invalid command 'JkWorkersFile', perhaps mis-spelled or defined by a module not included in the server configuration Obviously the module is loading. I even tried the AddModule directive, but it just tells me the module is already loaded. I tried commenting out the 'JkWorkersFile' parameter, but it just errors on the next line: [Wed Nov 05 23:28:56 2003] ( info) [mod_jk2.c (208)]: Set serverRoot /etc/httpd Create config for main host Syntax error on line 1500 of /etc/httpd/conf/httpd.conf: Invalid command 'JkLogFile', perhaps mis-spelled or defined by a module not included in the server configuration Any
Problem with mod_jk2 and ssl
I have a test server setup with Apache 1.3.27, Tomcat 4.1.27, and
mod_jk2. Its all running on RH Linux ES 2.1.
Apache is setup on ports 80 443. The port 80 config has only the
basics defined, then has a mod_rewrite rule to send *ALL* traffic to the
same URL but via https. It also has mod_jk2 setup to forward all .jsp
.do requests to tomcat. Tomcat is listening on ports 8080 and 8009.
All seems to work fine, but there's a hole. If I go to http://qa-wap1, I
am properly redirected to https://qa-wap1. As I login, follow links,
etc., I stay on the secure URL. However, if get into a secure URL... say
https://qa-wap1/submitProfile.jsp and change the URL in my browser to
http://qa-wap1:80/submitProfile.jsp and refresh the browser, the entire
page (content and images, both) reloads and looks perfect. The obvious
problem is that I just circumvented the secure URL concept. There's a
hole somewhere that I haven't been able to plug. This occurs with
multiple browsers.
Interestingly, I have an almost identical setup using Apache 1.3.26 and
Resin via mod_caucho. The mod_rewrite rule is the same, but if I try to
substitute the URL as mentioned above, it immediately puts me back on
the secure URL as it should.
I'm including all the relevant portions of the config files below...
httpd.conf:
VirtualHost qa-wap1:80
ServerName qa-wap1
ServerAlias qa-wap1.sd.mydomain.com
ServerAdmin [EMAIL PROTECTED]
ErrorLog /var/log/httpd/qa-wap1_error_log
TransferLog /var/log/httpd/qa-wap1_access_log
CustomLog /var/log/httpd/qa-wap1_referer_log referer
CustomLog /var/log/httpd/qa-wap1_agent_log agent
#
RewriteEngine on
RewriteLogLevel 0
RewriteRule ^(.*) https://qa-wap1$1 [R=301]
/VirtualHost
VirtualHost qa-wap1:443
ServerName qa-wap1
ServerAlias qa-wap1.sd.genvault.com
ServerAdmin [EMAIL PROTECTED]
DocumentRoot /usr/tomcat/webapps/Genvault
ErrorLog /var/log/httpd/qa-wap1_ssl_error_log
TransferLog /var/log/httpd/qa-wap1_ssl_access_log
CustomLog /var/log/httpd/qa-wap1_ssl_referer_log referer
CustomLog /var/log/httpd/qa-wap1_ssl_agent_log agent
DirectoryIndex index.htm
# SSL Options
SSLEngine on
SSLCipherSuite
ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL
SSLCertificateFile /etc/httpd/certs/qa-wap1.crt
SSLCertificateKeyFile /etc/httpd/certs/qa-wap1.key
# End SSL Options
/VirtualHost
# Load mod_jk2
LoadModule jk2_module modules/mod_jk2.so
AddModule mod_jk2.c
workers2.properties:
#[logger.apache13]
#level=DEBUG
[shm]
file=/var/log/httpd/shm.file
size=1048576
[workerEnv:]
info=Global server options
timing=1
debug=0
[channel.socket:localhost:8009]
port=8009
host=127.0.0.1
# define the worker
[ajp13:localhost:8009]
channel=channel.socket.localhost:8009
# Uri mapping
[uri:/*.jsp]
worker=ajp13:localhost:8009
[uri:/*.do]
worker=ajp13:localhost:8009
[uri:/servlet/*]
worker=ajp13:localhost:8009
[uri:/services/*]
worker=ajp13:localhost:8009
server.xml (snip - this is what correlates to the workers2.properties
file for mapping to tomcat):
!-- Define an AJP 1.3 Connector on port 8009 --
Connector className=org.apache.ajp.tomcat4.Ajp13Connector
port=8009
protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler
minProcessors=5
maxProcessors=75
acceptCount=10
debug=0/
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=8019
# 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
handler.list=request,container,channelSocket
channelSocket.port=8009
channelSocket.address=127.0.0.1
channelSocket.maxPort=port+10
Most interestingly, I decided to circumvent the problem by setting a
different DocumentRoot for the port 80 vhost, and having only a single
index.html in the folder and have it do an immediate refresh to the
secure URL (https://qa-wap1), plus I removed the rewrite rules. I would
think that in doing this, if I change the URL to
Re: Problem with mod_jk2 and ssl
All seems to work fine, but there's a hole. If I go to http://qa-wap1, I am properly redirected to https://qa-wap1. As I login, follow links, etc., I stay on the secure URL. However, if get into a secure URL... say https://qa-wap1/submitProfile.jsp and change the URL in my browser to http://qa-wap1:80/submitProfile.jsp and refresh the browser, the entire page (content and images, both) reloads and looks perfect. The obvious problem is that I just circumvented the secure URL concept. There's a hole somewhere that I haven't been able to plug. This occurs with multiple browsers. I think I see where the hiccup is. LoadModule jk2_module modules/mod_jk2.so AddModule mod_jk2.c If this is at the bottom of your httpd.conf, if effectively appends the AddModule for mod_jk2.c to the bottom of the AddModule list. If you haven't rearranged the other AddModules, that means that mod_jk2 gets a chance to handle the request before mod_rewrite does. You want mod rewrite to get it first. (AddModule works like a stack, the _last_ one added gets the request _first_. So, the AddModule for mod_jk2 should appear *before* the AddModule for mod_rewrite). mod_rewrite will get a chance to handle http://qa-wap1/, because none of your jk2.properties because none of the [uri:] blocks in your jk2.properties match it. Finally, When moving the AddModule, don't forget to move the corresponding LoadModule directive. -- Steve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem with mod_jk2
Two prefaces... 1) I hope this is the right list. I didn't see one specifically for mod_jk/mod_jk2. 2) I've read all the doc's I can find. I've been reading and trying for the last two days. Please don't send me replies telling me to RTM. The whole reason for my post is that I'm stuck and think I'm dealing with mod_jk docs not being updated for mod_jk2. I have a RH Linux ES 2.1 server. It has apache 1.3.27 installed via RH's up2date. I also have mod_ssl, and a few other mod's. The apache part is up and running correctly on non-standard ports, but I've tested it with local telnets and remotely through a web-browser. Our original configuration on the server was just pure Tomcat (4.1.27) listening on port 80. We wanted to add SSL support (port 443) and split our services at the same time, allowing us to later have Tomcat and Apache on different servers, hence why I installed Apache. I've spent the last two days reading the relevant portions of WROX's Professional Apache Tomcat and loads of information on the jakarta.apache.org site. Unfortunately, it seems that a lot of the docs (and my book) are still referencing mod_jk syntax options and causing me confusion trying to use mod_jk2. My apache and mod_ssl are from RPM, not source. My Tomcat (ver. 4.1.27... need to get this working before going to 4.1.29) is from a binary (jakarta-tomcat-4.1.27.tar.gz). My mod_jk2 is from jakarta-tomcat-connectors-jk2-src-current.tar.gz and was built by cd'ing into ~/jk/native2, then running 'buildconf.sh' and then 'configure --with-apxs=/usr/sbin/apxs'. The file mod_jk2.so was created and I copied it to my modules directory (/usr/lib/apache - stock on RH ES 2.1). I have the following in my server.xml: !-- 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/ I've created a workers.properties file in /usr/jakarta-tomcat-4.1.27/conf/jk. It looks like this: # Setting variables workers.tomcat_home=/usr/tomcat workers.java_home=/usr/java/j2sdk1.4.1_04 ps=/ worker.list=TomcatWorker1 # Settings for TomcatWorker1 worker worker.TomcatWorker1.port=8009 worker.TomcatWorker1.host=localhost worker.TomcatWorker1.type=ajp13 Lastly, I've added the following to the end of my httpd.conf: # Load mod_jk2 LoadModule jk2_module modules/mod_jk2.so # Configure mod_jk2 JkWorkersFile /etc/httpd/conf/workers2.properties JkLogFile /var/log/httpd/mod_jk.log JkLogLevel info JkMount /usr/tomcat/webapps/Genvault/*.jsp TomcatWorker1 Here's my problem. When I run apachectl configtest, I get: [Wed Nov 05 23:27:15 2003] ( info) [mod_jk2.c (208)]: Set serverRoot /etc/httpd Create config for main host Syntax error on line 1499 of /etc/httpd/conf/httpd.conf: Invalid command 'JkWorkersFile', perhaps mis-spelled or defined by a module not included in the server configuration Obviously the module is loading. I even tried the AddModule directive, but it just tells me the module is already loaded. I tried commenting out the 'JkWorkersFile' parameter, but it just errors on the next line: [Wed Nov 05 23:28:56 2003] ( info) [mod_jk2.c (208)]: Set serverRoot /etc/httpd Create config for main host Syntax error on line 1500 of /etc/httpd/conf/httpd.conf: Invalid command 'JkLogFile', perhaps mis-spelled or defined by a module not included in the server configuration Any thoughts on how to get this working? I feel like I'm real close, but missing something obvious. I've searched around google and found a post saying to use jk2.properties instead of workers.properties for mod_jk2. I've tried this and the appropriate path change, but it didn't work. The post also said to put in in apache's conf dir and it will look for it there (/etc/httpd/conf). I tried that and it didn't work either. Reference: http://zarb.org/pipermail/jpackage-discuss/2003-July/002573.html -- Andrew Davis, Founder SoCalLinuxSolutions [EMAIL PROTECTED] 760-525-4689 SoCalLinuxSolutions.com Linux Consultation Integration Services - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with mod_jk2
On Wed, 5 Nov 2003, Andrew Davis wrote: I've created a workers.properties file in /usr/jakarta-tomcat-4.1.27/conf/jk. It looks like this: # Setting variables workers.tomcat_home=/usr/tomcat workers.java_home=/usr/java/j2sdk1.4.1_04 ps=/ worker.list=TomcatWorker1 # Settings for TomcatWorker1 worker worker.TomcatWorker1.port=8009 worker.TomcatWorker1.host=localhost worker.TomcatWorker1.type=ajp13 The syntax of the workers file is different for jk2. It should be called workers2.properties and be put in your apache conf directory. The documentation is a little light, but you can see the tomcat website for some examples of what it should look like at http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk2/configwebex.html Lastly, I've added the following to the end of my httpd.conf: # Load mod_jk2 LoadModule jk2_module modules/mod_jk2.so # Configure mod_jk2 JkWorkersFile /etc/httpd/conf/workers2.properties JkLogFile /var/log/httpd/mod_jk.log JkLogLevel info JkMount /usr/tomcat/webapps/Genvault/*.jsp TomcatWorker1 You don't need anything but the LoadModule line for jk2. The other stuff is configured in the workers2.properties file. The documentation for this is extremely light, but might be somewhat helpful. Check http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk2/installhowto.html Jonathan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with mod_jk2
Thanks. That helps. I'm playing with the options now. I notice, however, that in the examples at: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk2/configwebex.html there are no options for specifying the path to java or tomcat anymore as there were in the mod_jk workers.properties file. Is this oversight, assumption, or is it simply no longer needed? AD [EMAIL PROTECTED] wrote: On Wed, 5 Nov 2003, Andrew Davis wrote: I've created a workers.properties file in /usr/jakarta-tomcat-4.1.27/conf/jk. It looks like this: # Setting variables workers.tomcat_home=/usr/tomcat workers.java_home=/usr/java/j2sdk1.4.1_04 ps=/ worker.list=TomcatWorker1 # Settings for TomcatWorker1 worker worker.TomcatWorker1.port=8009 worker.TomcatWorker1.host=localhost worker.TomcatWorker1.type=ajp13 The syntax of the workers file is different for jk2. It should be called workers2.properties and be put in your apache conf directory. The documentation is a little light, but you can see the tomcat website for some examples of what it should look like at http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk2/configwebex.html Lastly, I've added the following to the end of my httpd.conf: # Load mod_jk2 LoadModule jk2_module modules/mod_jk2.so # Configure mod_jk2 JkWorkersFile /etc/httpd/conf/workers2.properties JkLogFile /var/log/httpd/mod_jk.log JkLogLevel info JkMount /usr/tomcat/webapps/Genvault/*.jsp TomcatWorker1 You don't need anything but the LoadModule line for jk2. The other stuff is configured in the workers2.properties file. The documentation for this is extremely light, but might be somewhat helpful. Check http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk2/installhowto.html Jonathan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Andrew Davis, Founder SoCalLinuxSolutions [EMAIL PROTECTED] 760-525-4689 SoCalLinuxSolutions.com Linux Consultation Integration Services - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with mod_jk2
On Wed, 5 Nov 2003, Andrew Davis wrote: Thanks. That helps. I'm playing with the options now. I notice, however, that in the examples at: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk2/configwebex.html there are no options for specifying the path to java or tomcat anymore as there were in the mod_jk workers.properties file. Is this oversight, assumption, or is it simply no longer needed? I believe you will only need the location of java and tomcat if you are trying to do a JNI integration between them. There is a more detailed workers2.properties example in the jakarta-tomcat-connectors-jk2-2.0.2-src/jk/conf directory of the source bundle. It has examples for setting up JNI startup, etc. I haven't used that feature, so I won't be able to offer that much help on it. Jonathan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with mod_jk2
Thanks... I was able to get everything working. Your help was much appreciated. :) [EMAIL PROTECTED] wrote: On Wed, 5 Nov 2003, Andrew Davis wrote: Thanks. That helps. I'm playing with the options now. I notice, however, that in the examples at: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk2/configwebex.html there are no options for specifying the path to java or tomcat anymore as there were in the mod_jk workers.properties file. Is this oversight, assumption, or is it simply no longer needed? I believe you will only need the location of java and tomcat if you are trying to do a JNI integration between them. There is a more detailed workers2.properties example in the jakarta-tomcat-connectors-jk2-2.0.2-src/jk/conf directory of the source bundle. It has examples for setting up JNI startup, etc. I haven't used that feature, so I won't be able to offer that much help on it. Jonathan -- Andrew Davis, Founder SoCalLinuxSolutions [EMAIL PROTECTED] 760-525-4689 SoCalLinuxSolutions.com Linux Consultation Integration Services - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem configurimg mod_jk2 for Cocoon 2.1.2
Hello everyone,
I have instaled and configure:
-Apache Web Server 2.0.47
- Tomcat 4.1
- Mod_Jk2
- JDK 1.4.2
- Cocoon 2.1.2
- Solaris 8 SPARC
I allready have working all of the them, just cant get Cocoon to respond
directly to Apache Web Server on port 80 (http://my.server.com/cocoon).
Cocoon responds on port 8080 of Tomcat
(http://my.server.com:8080/cocoon) but no 80, i get an Internal Server
Error.
I think is mod_jk2 configuration that i dont have just right via the
worker2.properties, jk2.properties, httpd.conf or server.xml i seached
the web for info but can find anything, cam any one help?
Here are my configuration Files, i dont now what i'm missing to get this
to work:
- httpd.conf
LoadModule jk2_module modules/mod_jk2.so
-jk2.properties
# Set the desired handler list
handler.list=request,container,channelSocket
# Socket Configuration
channelSocket.port=8009
channelSocket.address=127.0.0.1
channelSocket.maxPort=port+10
-server.xml
!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 --
Connector className=org.apache.coyote.tomcat4.CoyoteConnector
port=8080 minProcessors=5 maxProcessors=75
enableLookups=true redirectPort=8443
acceptCount=100 debug=0 connectionTimeout=2
useURIValidationHack=false disableUploadTimeout=true /
!-- Note : To disable connection timeouts, set connectionTimeout value
to -1 --
!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 --
Connector className=org.apache.coyote.tomcat4.CoyoteConnector
port=8009 minProcessors=5 maxProcessors=75
enableLookups=true redirectPort=8443
acceptCount=10 debug=0 connectionTimeout=0
useURIValidationHack=false
protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/
-workers2.properties
[logger]
level=DEBUG
[config:]
file=/usr/local/apache/conf/workers2.properties
debug=0
debugEnv=0
[uriMap:]
info=Maps the requests. Options: debug
debug=0
# Alternate file logger
[logger.file:0]
level=DEBUG
file=/usr/local/apache/logs/jk2.log
#Share memory handling. Needs To be set.
[shm:]
info=Scoreboard. Required for reconfiguration and status with
multiprocess servers
file=/usr/local/apache/logs/jk2.shm
size=1048576
debug=0
disabled=0
[workerEnv:]
info=Global server options
timing=1
debug=0
#Socket Channel, explicity set port and host
[channel.socket:localhost:8009]
info=Ajp13 forwarding over socket
debug=0
tomcatId=localhost:8009
#define the worker
[ajp13:localhost:8009]
channel=channel.socket:localhost:8009
[status:status]
info=Status worker, displays runtime informations
[vm:]
info=Parameters used to load a JVM in the server process
classpath=${TOMCAT_HOME}/bin/tomcat-jni.jar
classpath=${TOMCAT_HOME}/server/lib/commons-logging.jar
OPT=-Djava.class.path=${TOMCAT_HOME}/bin/tomcat-jni.jar;${TOMCAT_HOME}/server/lib/commons-logging.jar
OPT=-Dtomcat.home=${TOMCAT_HOME}
OPT=-Dcatalina.home=${TOMCAT_HOME}
OPT=-Xmx128M
disabled=1
[uri:/jkstatus/*]
info=Display status information and checks the config file for changes
group=status:
worker=status:status
[uri:/examples]
info=Example webapp in the default context.
context=/examples
debug=0
[uri:/examples/servlet/*]
info=Prefix mapping
[uri:/examples/*.jsp]
info=Extension mapping
[uri:/examples/*]
info=Map the whole webapp
[uri:/cocoon/*]
worker=apj13:localhost:8009
#context=/cocoon
Thanks
Julio
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem building mod_jk2 on Freebsd 4.8-RELEASE
Hi Dean, I have the same Apache and Tomcat versions on Redhat 9. I'm not sure if setup is the same but what I did was a lot shorter and worked, no probs, first you need the jk2 connectors file jakarta-tomcat-connectors-jk2-2.0.2-src.tar.gz untar it somewhere, then cd to the jk/native2 directory and do: ./configure --with-apxs2=/usr/local/apache2/bin/apxs \ --with-tomcat41=/usr/local/tomcat/jakarta-tomcat-4.1.27 \ --with-apache2-lib=/usr/local/apache2/lib \ --with-apr-lib=/usr/local/apache2/lib --with-jni then make, then cp build/jk2/apache2/mod_jk2.so /usr/local/apache2/modules/ cp build/jk2/apache2/jkjni.so /usr/local/apache2/modules/ then ## from tomcat-docs/jk2/jk2/confighowto.html # Minimum configuration is the simplest one to make the JK2 working. The used channel will be socket, and lot of options are used by default. Both the Tomcat and web server are on the same computer. jk2.properties: # The default port is 8009 but you can use another one # channelSocket.port=8019 That is all needed on the Tomcat side to configure the JK2. workers2.properties: # Define the communication channel [channel.socket:localhost:8009] info=Ajp13 forwarding over socket tomcatId=localhost:8009 # Map the Tomcat examples webapp to the Web server uri space [uri:/examples/*] info=Map the whole webapp Start the Tomcat and Web server and browse to the http://localhost/examples/ ### for me that worked hope this helps, kind regards, Luke On Mon, 2003-09-01 at 16:13, Dean Searle wrote: Hello All! I am new to this mailing list and somewhat new to Apache and Tomcat. I recently have rebuilt my server from the ground up and need to rebuild mod_jk2. Here is what I have so far: Freebsd 4.8 Release Apache 2.0.47 Tomcat 4.1.27 Ant 1.5.4 JDK 1.4.1p3_3 I was following the instructions outline in the book called Tomcat: The Definitive Guide by O'Reilly: ---BEGIN SNIPPET--- 1. Download a new source code release of jakarta-tomcat-connectors from http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release. 2. Unpack the archive and change directory into the new jakarta-tomcat-connectors source directory: # gunzip jakarta-tomcat-connectors-4.1.24-src.tar.gz # tar xvf jakarta-tomcat-connectors-4.1.24-src.tar # cd jakarta-tomcat-connectors-4.1.24-src 3. Make sure that your PATH environment variable points to the bin/ directory of the latest release of Apache Ant. Download Ant from http://ant.apache.org and add $ANT_HOME/bin to your PATH if you haven't already: # PATH=$PATH:/usr/local/apache-ant-1.5.2 # export PATH # which ant /usr/local/apache-ant-1.5.2/bin/ant 4. Make sure that your JAVA_HOME environment variable is set and points to your JDK: # JAVA_HOME=/usr/local/jdk1.3.1_02 # export JAVA_HOME # echo $JAVA_HOME /usr/local/jdk1.3.1_02 5. Create a usable copy of the util/build.properties file: # cp util/build.properties.sample util/build.properties 6. Create a usable copy of the jk/build.properties file: # cp jk/build.properties.sample jk/build.properties 7. Edit the new jk/build.properties file, changing only the lines that apply to the Tomcat and Apache httpd versions that you have and want to use. For example, if you have Tomcat 4.1 and Apache httpd 2, change the following lines to point to where yours are installed (leave everything else in this file alone): tomcat41.home=/usr/local/jakarta-tomcat-4.1.24 apache2.home=/usr/local/apache2 8. Create a usable copy of the coyote/build.properties file: # cp coyote/build.properties.sample coyote/build.properties 9. Edit the new coyote/build.properties file, changing the value of catalina.home to point to your Tomcat installation directory: catalina.home=/usr/local/jakarta-tomcat-4.1.24 10. Run ant from the top level of the jakarta-tomcat-connectors source directory to build mod_jk2 and the Java side of the connector: # cd /usr/local/jakarta-tomcat-connectors-4.1.24-src # ant 11. If you're building on Linux, copy the linux headers into the root of the JDK's include directory (this will allow you to avoid a known build problem with mod_jk2 and Linux): # cd $JAVA_HOME/include # cp linux/* . 12. Build mod_jk2 by calling the native build target from within the jk directory: # cd jk # ant native ---END SNIPPET--- When I ran ant native here is the response I get: fbsd2# ant native Buildfile: build.xml jkant: [mkdir] Created dir: /usr/ports/distfiles/jakarta-tomcat-connectors-4.1.27-src/jk/build/class es [mkdir] Created dir: /usr/ports/distfiles/jakarta-tomcat-connectors-4.1.27-src/jk/build/class es/META-INF [mkdir] Created dir: /usr/ports/distfiles/jakarta-tomcat-connectors-4.1.27-src/jk/build/lib [javac] Compiling 17 source files to /usr/ports/distfiles/jakarta-tomcat-connectors-4.1.27-src/jk/build/class es [copy] Copying 1 file to /usr/ports/distfiles/jakarta-tomcat
Problem building mod_jk2 on Freebsd 4.8-RELEASE
Hello All!
I am new to this mailing list and somewhat new to Apache and Tomcat. I
recently have rebuilt my server from the ground up and need to rebuild
mod_jk2.
Here is what I have so far:
Freebsd 4.8 Release
Apache 2.0.47
Tomcat 4.1.27
Ant 1.5.4
JDK 1.4.1p3_3
I was following the instructions outline in the book called Tomcat: The
Definitive Guide by O'Reilly:
---BEGIN SNIPPET---
1. Download a new source code release of jakarta-tomcat-connectors from
http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release.
2. Unpack the archive and change directory into the new
jakarta-tomcat-connectors source directory:
# gunzip jakarta-tomcat-connectors-4.1.24-src.tar.gz
# tar xvf jakarta-tomcat-connectors-4.1.24-src.tar
# cd jakarta-tomcat-connectors-4.1.24-src
3. Make sure that your PATH environment variable points to the bin/
directory of the latest release of Apache Ant. Download Ant
from http://ant.apache.org and add $ANT_HOME/bin to your PATH if you
haven't already:
# PATH=$PATH:/usr/local/apache-ant-1.5.2
# export PATH
# which ant
/usr/local/apache-ant-1.5.2/bin/ant
4. Make sure that your JAVA_HOME environment variable is set and points
to your JDK:
# JAVA_HOME=/usr/local/jdk1.3.1_02
# export JAVA_HOME
# echo $JAVA_HOME
/usr/local/jdk1.3.1_02
5. Create a usable copy of the util/build.properties file:
# cp util/build.properties.sample util/build.properties
6. Create a usable copy of the jk/build.properties file:
# cp jk/build.properties.sample jk/build.properties
7. Edit the new jk/build.properties file, changing only the lines that
apply to the Tomcat and Apache httpd versions that you have
and want to use. For example, if you have Tomcat 4.1 and Apache httpd 2,
change the following lines to point to where yours
are installed (leave everything else in this file alone):
tomcat41.home=/usr/local/jakarta-tomcat-4.1.24
apache2.home=/usr/local/apache2
8. Create a usable copy of the coyote/build.properties file:
# cp coyote/build.properties.sample coyote/build.properties
9. Edit the new coyote/build.properties file, changing the value of
catalina.home to point to your Tomcat installation directory:
catalina.home=/usr/local/jakarta-tomcat-4.1.24
10. Run ant from the top level of the jakarta-tomcat-connectors source
directory to build mod_jk2 and the Java side of the
connector:
# cd /usr/local/jakarta-tomcat-connectors-4.1.24-src
# ant
11. If you're building on Linux, copy the linux headers into the root of
the JDK's include directory (this will allow you to avoid a
known build problem with mod_jk2 and Linux):
# cd $JAVA_HOME/include
# cp linux/* .
12. Build mod_jk2 by calling the native build target from within the jk
directory:
# cd jk
# ant native
---END SNIPPET---
When I ran ant native here is the response I get:
fbsd2# ant native
Buildfile: build.xml
jkant:
[mkdir] Created dir:
/usr/ports/distfiles/jakarta-tomcat-connectors-4.1.27-src/jk/build/class
es
[mkdir] Created dir:
/usr/ports/distfiles/jakarta-tomcat-connectors-4.1.27-src/jk/build/class
es/META-INF
[mkdir] Created dir:
/usr/ports/distfiles/jakarta-tomcat-connectors-4.1.27-src/jk/build/lib
[javac] Compiling 17 source files to
/usr/ports/distfiles/jakarta-tomcat-connectors-4.1.27-src/jk/build/class
es
[copy] Copying 1 file to
/usr/ports/distfiles/jakarta-tomcat-connectors-4.1.27-src/jk/build/class
es/META-INF
[jar] Building jar:
/usr/ports/distfiles/jakarta-tomcat-connectors-4.1.27-src/jk/build/lib/j
kant.jar
detect:
[echo] jakarta-tomcat-connectors
report:
[echo] Tomcat33: ${tomcat33.detect}
../../jakarta-tomcat/build/tomcat
[echo] Tomcat40: ${tomcat40.detect} ../../jakarta-tomcat-4.0/build
[echo] Tomcat41: true /usr/local/jakarta-tomcat4.1
[echo] Tomcat5: ${tomcat5.detect} ../../jakarta-tomcat-5/build
[echo] Apache13: ${apache13.detect} /opt/apache13
[echo] Apache2: true /usr/local
[echo] iPlanet: ${iplanet.detect} /opt/iplanet6
[echo] IIS: ${iis.detect} ${iis.home}
native:
init:
[echo] /root
[mkdir] Created dir:
/usr/ports/distfiles/jakarta-tomcat-connectors-4.1.27-src/jk/build/jk
apache20:
[mkdir] Created dir:
/usr/ports/distfiles/jakarta-tomcat-connectors-4.1.27-src/jk/build/jk/ap
ache2
[so] Compiling 19 out of 19
Compiling
/usr/ports/distfiles/jakarta-tomcat-connectors-4.1.27-src/jk/native/comm
on/jk_msg_buff.c
Compiling
/usr/ports/distfiles/jakarta-tomcat-connectors-4.1.27-src/jk/native/comm
on/jk_ajp13_worker.c
Compiling
/usr/ports/distfiles/jakarta-tomcat-connectors-4.1.27-src/jk/native/comm
on/jk_md5.c
[so] Compile failed 1
/usr/ports/distfiles/jakarta-tomcat-connectors-4.1.27-src/jk/native/comm
on/jk_md5.c
[so] Command:libtool --mode=compile cc -c -o
/usr/ports/distfiles/jakarta-tomcat-connectors-4.1.27-src/jk/build/jk/ap
ache2/common/jk_md5.o
-I/usr/ports/distfiles/jakarta-tomcat-connectors-4.1.27-src/jk/native/co
mmon -I/usr/local/include -I/usr/local/jdk1.4.1/jre/../include -g -W
Problem with mod_jk2
Hello,
I've compiled mod_jk2, and installed it intirely according to the
instructions on the website.
I'm using apache 2.0.47 and tomcat 4.1.24
I have the impression that the mod_jk2 modules is loaded correctly, but that
it is completely ignoring my workers2.properties file. No URL mappings work.
I do have an apache installation that is a bit peculiar. To make ist short,
conf is not a subdir of ${serverroot}.
Now the website says the following:
The config file is named workers2.properties, located by default in
${serverRoot}/conf, where ${serverRoot} is the web server dir, like
/usr/local/apache. It is possible to modify the location of the file using
server-specific directives.
Can someone enlighten me as to which server-specific directive I can use
to tell mod_jk2 where the workers2.properties file is? (JkWorkersFile as in
mod_jk doesn't work, it throws a syntax error from Apache...)
TIA
Krist van Besien
---
Krist van Besien
Unix Specialist BZBD
Bundesamt für Informatik und Telekommunikation BIT
Monbijoustrasse 74, CH-3003 Bern
Tel. +41 31 322 24 46
added interaction www.informatik.admin.ch
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with mod_jk2
Hi,
http://jakarta.apache.org/tomcat/faq/connectors.html
-e
On Wed, 6 Aug 2003 [EMAIL PROTECTED] wrote:
Hello,
I've compiled mod_jk2, and installed it intirely according to the
instructions on the website.
I'm using apache 2.0.47 and tomcat 4.1.24
I have the impression that the mod_jk2 modules is loaded correctly, but that
it is completely ignoring my workers2.properties file. No URL mappings work.
I do have an apache installation that is a bit peculiar. To make ist short,
conf is not a subdir of ${serverroot}.
Now the website says the following:
The config file is named workers2.properties, located by default in
${serverRoot}/conf, where ${serverRoot} is the web server dir, like
/usr/local/apache. It is possible to modify the location of the file using
server-specific directives.
Can someone enlighten me as to which server-specific directive I can use
to tell mod_jk2 where the workers2.properties file is? (JkWorkersFile as in
mod_jk doesn't work, it throws a syntax error from Apache...)
TIA
Krist van Besien
---
Krist van Besien
Unix Specialist BZBD
Bundesamt für Informatik und Telekommunikation BIT
Monbijoustrasse 74, CH-3003 Bern
Tel. +41 31 322 24 46
added interaction www.informatik.admin.ch
-
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]
problem about mod_jk2 maybe
I'm using: windows2k sp3 apache httpd 2.0.43 tomcat 4.1.24 jk2 2.0.43 struts 1.1 Actually I'm trying to build my first struts application. Previously I've made the struts-example.war running on my machine. But when I turn to my own one, It suckes. Similiar to many tutorials in the world, it's a simple user logging-in and registration application. When I press the login button. Apache complains: [Tue Jul 29 14:02:26 2003] [error] msgAjp.receive(): Incoming message is too big 8196 [Tue Jul 29 14:02:26 2003] [error] channelSocket.receive(): Bad header [Tue Jul 29 14:02:27 2003] [error] workerEnv.processCallbacks() Error reading reply [Tue Jul 29 14:02:27 2003] [error] ajp13.service() ajpGetReply unrecoverable error 12 [Tue Jul 29 14:02:27 2003] [error] ajp13.service() Error forwarding ajp13:localhost:8009 0 1 [Tue Jul 29 14:02:27 2003] [notice] ajp13.done() close endpoint ajp13:localhost:8009 error_state 1 [Tue Jul 29 14:02:27 2003] [error] mod_jk.handler() Error connecting to tomcat 12 I have no idea about what message is so big. Does anyone could help? Thanks in advance! Haisheng HU -- Airport Project Team TravelSky Technology Limited [mail] [EMAIL PROTECTED] [tel.] 86-10-8401-9083 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
problem compile mod_jk2
Hello I have compile the mod_jk2 (see below). And when I run make, I received follow error: ../../common/jk_vm_default.c: In function `jk2_vm_guessJvmDll': ../../common/jk_vm_default.c:449: stray '\' in program make[1]: *** [../../../build/jk2/apache2/jk_vm_default.lo] Error 1 make[1]: Leaving directory `/opt/mod_jk/jakarta-tomcat-connectors-4.1.24-src/jk/native2/server/apache2' make: *** [jk2-build] Error 1 I have Linux SUSE 8.0 Can somewhere help me? gianni I made this steps: jakarta-tomcat-connectors-jk2-2.0.2-src.tar.gz from http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/release/v2.0 .2/src/ 2. Uncompress it and extract the tar file. 3. cd to jakarta-tomcat-connectors-jk2-2.0.2-src/jk/native2 4. chmod u+x configure 5. Run configure with: ./configure --with-apxs2=apache-root-directory/bin/apxs \ --with-tomcat41=tomcat-root-directory \ --with-java-home=java-root-directory \ --with-jni \ --with-pcre For example: ./configure --with-apxs2=/home/apache/bin/apxs \ --with-tomcat41=/home/tomcat \ --with-java-home=/usr/java \ --with-jni \ --with-pcre 6. Run make - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
problem compile mod_jk2
Hello I have compile the mod_jk2 (see below). And when I run make, I received follow error: ../../common/jk_vm_default.c: In function `jk2_vm_guessJvmDll': ../../common/jk_vm_default.c:449: stray '\' in program make[1]: *** [../../../build/jk2/apache2/jk_vm_default.lo] Error 1 make[1]: Leaving directory `/opt/mod_jk/jakarta-tomcat-connectors-4.1.24-src/jk/native2/server/apache2' make: *** [jk2-build] Error 1 I have Linux SUSE 8.0 Can somewhere help me? gianni I made this steps: jakarta-tomcat-connectors-jk2-2.0.2-src.tar.gz from http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/release/v2.0 .2/src/ 2. Uncompress it and extract the tar file. 3. cd to jakarta-tomcat-connectors-jk2-2.0.2-src/jk/native2 4. chmod u+x configure 5. Run configure with: ./configure --with-apxs2=apache-root-directory/bin/apxs \ --with-tomcat41=tomcat-root-directory \ --with-java-home=java-root-directory \ --with-jni \ --with-pcre For example: ./configure --with-apxs2=/home/apache/bin/apxs \ --with-tomcat41=/home/tomcat \ --with-java-home=/usr/java \ --with-jni \ --with-pcre 6. Run make - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: problem compile mod_jk2
Hi, Try just using the --use-apxs2 option. -e On Tue, 8 Jul 2003, Gianni Martiradonna wrote: Hello I have compile the mod_jk2 (see below). And when I run make, I received follow error: ../../common/jk_vm_default.c: In function `jk2_vm_guessJvmDll': ../../common/jk_vm_default.c:449: stray '\' in program make[1]: *** [../../../build/jk2/apache2/jk_vm_default.lo] Error 1 make[1]: Leaving directory `/opt/mod_jk/jakarta-tomcat-connectors-4.1.24-src/jk/native2/server/apache2' make: *** [jk2-build] Error 1 I have Linux SUSE 8.0 Can somewhere help me? gianni I made this steps: jakarta-tomcat-connectors-jk2-2.0.2-src.tar.gz from http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/release/v2.0 .2/src/ 2. Uncompress it and extract the tar file. 3. cd to jakarta-tomcat-connectors-jk2-2.0.2-src/jk/native2 4. chmod u+x configure 5. Run configure with: ./configure --with-apxs2=apache-root-directory/bin/apxs \ --with-tomcat41=tomcat-root-directory \ --with-java-home=java-root-directory \ --with-jni \ --with-pcre For example: ./configure --with-apxs2=/home/apache/bin/apxs \ --with-tomcat41=/home/tomcat \ --with-java-home=/usr/java \ --with-jni \ --with-pcre 6. Run make - 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]
AW: problem compile mod_jk2
Ok. thanks It works! -gianni -Ursprungliche Nachricht- Von: Eric J. Pinnell [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 8. Juli 2003 15:40 An: Tomcat Users List Betreff: Re: problem compile mod_jk2 Hi, Try just using the --use-apxs2 option. -e On Tue, 8 Jul 2003, Gianni Martiradonna wrote: Hello I have compile the mod_jk2 (see below). And when I run make, I received follow error: ../../common/jk_vm_default.c: In function `jk2_vm_guessJvmDll': ../../common/jk_vm_default.c:449: stray '\' in program make[1]: *** [../../../build/jk2/apache2/jk_vm_default.lo] Error 1 make[1]: Leaving directory `/opt/mod_jk/jakarta-tomcat-connectors-4.1.24-src/jk/native2/server/apache2' make: *** [jk2-build] Error 1 I have Linux SUSE 8.0 Can somewhere help me? gianni I made this steps: jakarta-tomcat-connectors-jk2-2.0.2-src.tar.gz from http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/release/v2.0 .2/src/ 2. Uncompress it and extract the tar file. 3. cd to jakarta-tomcat-connectors-jk2-2.0.2-src/jk/native2 4. chmod u+x configure 5. Run configure with: ./configure --with-apxs2=apache-root-directory/bin/apxs \ --with-tomcat41=tomcat-root-directory \ --with-java-home=java-root-directory \ --with-jni \ --with-pcre For example: ./configure --with-apxs2=/home/apache/bin/apxs \ --with-tomcat41=/home/tomcat \ --with-java-home=/usr/java \ --with-jni \ --with-pcre 6. Run make - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Problem compiling mod_jk2 connector in Solaris 8 Apache 2.0.39
Yowzer, that was a lot of scrolling. I had lots of problems with gcc 3.2 on Solaris 8. I ended up going back to 2.95. The library it can't find is the APR library. On my Solaris 8 development server: bash-2.03# find / -name libapr* -print /usr/local/apache2/lib/libapr-0.so.0.9.2 /usr/local/apache2/lib/libapr-0.so.0 /usr/local/apache2/lib/libapr-0.so /usr/local/apache2/lib/libapr-0.la /usr/local/apache2/lib/libapr-0.a /usr/local/apache2/lib/libaprutil-0.so /usr/local/apache2/lib/libaprutil-0.so.0.9.2 /usr/local/apache2/lib/libaprutil-0.so.0 /usr/local/apache2/lib/libaprutil-0.la /usr/local/apache2/lib/libaprutil-0.a /usr/local/apache2/lib/libapr.so bash-2.03# John -Original Message- From: Julio César Mejia Vergara [mailto:[EMAIL PROTECTED] Sent: Monday, February 24, 2003 10:44 PM To: [EMAIL PROTECTED] Subject: Problem compiling mod_jk2 connector in Solaris 8 Apache 2.0.39 Hello, I have a Sun Blade 100 (SPARC) running Solaris 8 with all its bundled patches. I'm traing to configure Apache HTTP 2.0.39 with Tomcat 4.1.18, i got Apache and Tomcat working seperatly but i'm traing to make it work together via Coyote mod_jk2, but when i try to compile mod_jk2 connectors a get an error. Can any one help I dont now if i'm missing a package that i need to install or is something else that i'm missing. It traid the compiled mod_jk2 thats in http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2 /release/v2.0.2/bin/solaris8/ but its compiled for Apache HTTPD 2.0.43 and it dosent let apache version of apache start. In the Solaris Machine i have installed: - Solaris 8 (SPARC) - Apache HTTP 2.0.39 (i need to make it work whit this version) - Tomcat 4.1.18 - Tomcat Connectors 4.1.18 - GNU gcc 3.2.2 - GNUmake 3.80 - Perl 5.8.0 - Jakarta ant 1.5.1 - autocong 2.57 - expect 5.38 - gd 1.8.3 - j2sdk 1.4.1 - libtool 1.4 - GNU tar 1.13. - tcl 8.4.1 - tk 8.4.1 - openssl 0.9.6g Here is the what i'm doing to compile the connectors and at the end the error message # pwd /opt/jakarta-tomcat-connectors-4.1.18-src/jk/native2 #*sh ./buildconf.sh* libtoolize --force --automake --copy aclocal automake --copy --add-missing configure.in: installing `scripts/build/unix/install-sh' configure.in: installing `scripts/build/unix/mkinstalldirs' configure.in: installing `scripts/build/unix/missing' autoconf # cp /usr/j2se/include/solaris/* /usr/java/include/ # pwd /opt/jakarta-tomcat-connectors-4.1.18-src/jk/native2 #*CPPFLAGS=-DBSD_COMP ./configure --with-apxs2=/usr/local/apache/bin/apxs --with-tomcat41=/opt/jakarta-tomcat-4.1.18 --with-java-home=/usr/j2se --with-java-platform=2 --with-jni* checking for a BSD-compatible install... scripts/build/unix/install-sh -c checking whether build environment is sane... yes checking for gawk... no checking for mawk... no checking for nawk... nawk checking whether make sets $(MAKE)... yes checking for gcc... gcc checking for C compiler default output... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for style of include used by make... GNU checking dependency style of gcc... none checking build system type... sparc-sun-solaris2.8 checking host system type... sparc-sun-solaris2.8 checking for ld used by GCC... /usr/ccs/bin/ld checking if the linker (/usr/ccs/bin/ld) is GNU ld... no checking for /usr/ccs/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/ccs/bin/nm -p checking whether ln -s works... yes checking how to recognise dependant libraries... pass_all checking command to parse /usr/ccs/bin/nm -p output... ok checking how to run the C preprocessor... gcc -E checking for egrep... Broken Pipe egrep checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... no checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking for ranlib... ranlib checking for strip... strip checking for objdir... .libs checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.lo... checking if gcc supports -fno-rtti -fno-exceptions... yes checking whether the linker (/usr/ccs/bin/ld) supports shared libraries... yes checking how to hardcode library paths into programs... immediate checking whether
Problem compiling mod_jk2 connector in Solaris 8 Apache 2.0.39
Hello, I have a Sun Blade 100 (SPARC) running Solaris 8 with all its bundled patches. I'm traing to configure Apache HTTP 2.0.39 with Tomcat 4.1.18, i got Apache and Tomcat working seperatly but i'm traing to make it work together via Coyote mod_jk2, but when i try to compile mod_jk2 connectors a get an error. Can any one help I dont now if i'm missing a package that i need to install or is something else that i'm missing. It traid the compiled mod_jk2 thats in http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/release/v2.0.2/bin/solaris8/ but its compiled for Apache HTTPD 2.0.43 and it dosent let apache version of apache start. In the Solaris Machine i have installed: - Solaris 8 (SPARC) - Apache HTTP 2.0.39 (i need to make it work whit this version) - Tomcat 4.1.18 - Tomcat Connectors 4.1.18 - GNU gcc 3.2.2 - GNUmake 3.80 - Perl 5.8.0 - Jakarta ant 1.5.1 - autocong 2.57 - expect 5.38 - gd 1.8.3 - j2sdk 1.4.1 - libtool 1.4 - GNU tar 1.13. - tcl 8.4.1 - tk 8.4.1 - openssl 0.9.6g Here is the what i'm doing to compile the connectors and at the end the error message # pwd /opt/jakarta-tomcat-connectors-4.1.18-src/jk/native2 #*sh ./buildconf.sh* libtoolize --force --automake --copy aclocal automake --copy --add-missing configure.in: installing `scripts/build/unix/install-sh' configure.in: installing `scripts/build/unix/mkinstalldirs' configure.in: installing `scripts/build/unix/missing' autoconf # cp /usr/j2se/include/solaris/* /usr/java/include/ # pwd /opt/jakarta-tomcat-connectors-4.1.18-src/jk/native2 #*CPPFLAGS=-DBSD_COMP ./configure --with-apxs2=/usr/local/apache/bin/apxs --with-tomcat41=/opt/jakarta-tomcat-4.1.18 --with-java-home=/usr/j2se --with-java-platform=2 --with-jni* checking for a BSD-compatible install... scripts/build/unix/install-sh -c checking whether build environment is sane... yes checking for gawk... no checking for mawk... no checking for nawk... nawk checking whether make sets $(MAKE)... yes checking for gcc... gcc checking for C compiler default output... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for style of include used by make... GNU checking dependency style of gcc... none checking build system type... sparc-sun-solaris2.8 checking host system type... sparc-sun-solaris2.8 checking for ld used by GCC... /usr/ccs/bin/ld checking if the linker (/usr/ccs/bin/ld) is GNU ld... no checking for /usr/ccs/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/ccs/bin/nm -p checking whether ln -s works... yes checking how to recognise dependant libraries... pass_all checking command to parse /usr/ccs/bin/nm -p output... ok checking how to run the C preprocessor... gcc -E checking for egrep... Broken Pipe egrep checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... no checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking for ranlib... ranlib checking for strip... strip checking for objdir... .libs checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.lo... checking if gcc supports -fno-rtti -fno-exceptions... yes checking whether the linker (/usr/ccs/bin/ld) supports shared libraries... yes checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... no checking dynamic linker characteristics... solaris2.8 ld.so checking if libtool supports shared libraries... yes creating libtool checking for test... /usr/bin/test checking for rm... /usr/bin/rm checking for grep... /usr/bin/grep checking for echo... /usr/bin/echo checking for sed... /usr/bin/sed checking for cp... /usr/bin/cp checking for mkdir... /usr/bin/mkdir no apxs given need to check for Perl first, apxs depends on it... checking for perl... /usr/local/bin/perl building connector for apache-2.0 checking for tomcat33 location... not provided checking for tomcat40 location... not provided checking for tomcat41 location... /opt/jakarta-tomcat-4.1.18 checking for JDK location (please wait)... /usr/j2se checking Java platform... 2 checking os_type directory... configure: creating ./config.status config.status: creating Makefile config.status: creating server/apache13/Makefile config.status: creating server/apache13/Makefile.apxs config.status: creating server/apache2/Makefile
FreeBSD 4.7 Apache2.0.43 tomcat 4.1.12 - problem with mod_jk2.so
Hi. I have installed apache2 - no problem. It works fine. I have installed tomcat4.1 from binaries - no problem. This too works fine for standalone. The problem I am having is when I try to build the mod_jk2.so module for apache. I am using ant to build the connector (jdk1.3.1). When I first built the connector, apache complained about undefined symbols for apr. I changed the build.xml file to link against the apr libraries that came with apache2. The next problem I found was that I needed to then rebuild apr using --enable-threads as a configure option. I also passed LIBS=-lc_r to the configuration script. Now with the current apr libraries, when I start apache. /usr/local/apache2/bin/apachectl start /usr/libexec/ld-elf.so.1: /usr/local/apache2/lib/libapr-0.so.9: Undefined symbol pthread_mutexattr_init platform is: uname -a FreeBSD removed 4.7-RELEASE FreeBSD 4.7-RELEASE #0: Wed Oct 9 15:08:34 GMT 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 Any help on how to build the mod_jk2.so module for this platform would be greatly appreciated. Many thanks in advance. Michael (ps. I also received the same error message when I tried the prebuilt mod_jk.so module that I downloaded for FreeBSD)
problem with mod_jk2 and apache
Hello All, I seem to be having problems using the mod_jk2.dll with apache2.0.43 on win2k. Complaints about invalid module structure The mod_jk.dll seems to work OK. Any ideas? Thanks! -- john -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
problem making mod_jk2 with Apache 2.0.42
Hi I can't compile mod_jk2 on MDK 7.2 from jakarta-tomcat-connectors-4.1.12-src with Apache 2.0.42. I had successfully build it with 2.0.39 and 2.0.40 The error is : /usr/bin/ld: cannot find -lapr collect2: ld returned 1 exit status make[1]: *** [../../../build/jk2/apache2/jkjni.la] Erreur 1 In fact, in build/jk2/apache2, mod_jk2.so exists, but not jkjni.so What can I do ? Dom -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Problem with mod_jk2
I have Tomcat 4.04 with Apache 2.0.39 installed on a Sun (sparc) machine. I have to do minor edit, but everything is up and running. I was checking out the jkstatus link, when I noticed a concern. It says my arch = i386 rather than sparc. Anyone have any idea how to change this? I do see a couple errors in Apache's error log, but none of them complain about not finding a directory i386 or any other i386 type files. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
