Hi
We have just upgraded to 2.4 and the upgrade all seems to have run ok and we can get the login page on port 8080 ok, but the mod_jk setup that was running fine with 2.3.5 is giving "service temporarily unavailable" error on port 80 /lams
I have added jvmRoute="node1" attribute to Engine in $JBOSS_HOME/server/default/deploy/jbossweb.sar/server.xml
lams server loads with final message
2012-12-17 14:28:04,552 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy, ctxPath=/lams/www
2012-12-17 14:28:04,692 INFO [org.apache.coyote.http11.Http11Protocol] (main) Starting Coyote HTTP/1.1 on http-210.48.33.60-8080
2012-12-17 14:28:04,897 INFO [org.apache.coyote.ajp.AjpProtocol] (main) Starting Coyote AJP/1.3 on ajp-210.48.33.60-8009
2012-12-17 14:28:05,123 INFO [org.jboss.bootstrap.microcontainer.ServerImpl] (main) JBoss (Microcontainer) [5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] Started in 2m:20s:447ms
Which indicates that Ajp is running on port 8009, but apache error log shows
[Mon Dec 17 14:39:53 2012][2330:3458803520] [info] jk_open_socket::jk_connect.c (594): connect to 127.0.0.1:8009 failed (errno=111)
[Mon Dec 17 14:39:53 2012][2330:3458803520] [info] ajp_connect_to_endpoint::jk_ajp_common.c (922): Failed opening socket to (127.0.0.1:8009) (errno=111)
[Mon Dec 17 14:39:53 2012][2330:3458803520] [error] ajp_send_request::jk_ajp_common.c (1507): (node1) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=111)
[Mon Dec 17 14:39:53 2012][2330:3458803520] [info] ajp_service::jk_ajp_common.c (2447): (node1) sending request to tomcat failed (recoverable), because of error during request sending (attempt=2)
[Mon Dec 17 14:39:53 2012][2330:3458803520] [error] ajp_service::jk_ajp_common.c (2466): (node1) connecting to tomcat failed.
[Mon Dec 17 14:39:53 2012]node1 lams.vln.school.nz 0.101693
[Mon Dec 17 14:39:53 2012][2330:3458803520] [info] jk_handler::mod_jk.c (2615): Service error=-3 for worker=node1
Are there some other changes we need to make to apache conf files or jboss config files to get mod_jk running for 2.4? Any help/pointers gratefully received.
workers.properties is
####################################
# Define 1 real worker named ajp13
worker.list=node1
# Set properties for worker named ajp13 to use ajp13 protocol,
# and run on port 8009
worker.ajp13.type=ajp13
worker.ajp13.host=localhost
worker.ajp13.port=8009
worker.ajp13.lbfactor=50
worker.ajp13.cachesize=10
worker.ajp13.cache_timeout=600
worker.ajp13.socket_keepalive=1
worker.ajp13.socket_timeout=300
####################################
jk.conf is
####################################
# Where to find workers.properties
# Update this path to match your conf directory location
JkWorkersFile /etc/apache2/jk_workers.properties
# Where to put jk logs
# Update this path to match your logs directory location
JkLogFile /var/log/apache2/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"
# Shm log file
JkShmFile /var/log/apache2/jk-runtime-status
##########################################
Virtual host setting
############################
JkMount /lams/ node1
JkMount /lams/* node1
############################
Thanks
Glen
Posted by Glen Davies