[org.apache.jk.common.ChannelSocket] connection timeout reac
Hello all.
I'm trying to configure Apache 2.0.48+Jboss 3.2.3+Tomcat-4.1.29+mod_jk 2.0.3 (Red Hat Linux OS, kernel 2.4.20).
I've followed some tutorials and howtos I've found, and I can see now the jkstatus pages.
However when I try to load some webapps examples (e.g jmx-console) the server displays 404 Not Found error message.
The logs files shows that the requests are redirected to Tomcat, but then something fails. Bellow you can see an example:
server.log file
[...]
2004-04-02 12:40:17,204 DEBUG [org.apache.jk.common.ChannelSocket] Accepted socket Socket[addr=/127.0.0.1,port=35882,localport=8009]
2004-04-02 12:40:17,206 DEBUG [org.apache.jk.common.ChannelSocket] receive()
2004-04-02 12:40:17,206 DEBUG [org.apache.jk.common.ChannelSocket] read() [B@104e330 8192 0 4 = 4
2004-04-02 12:40:17,206 DEBUG [org.apache.jk.common.MsgAjp] Received 474 18
2004-04-02 12:40:17,207 DEBUG [org.apache.jk.common.ChannelSocket] read() [B@104e330 8192 4 474 = 474
2004-04-02 12:40:17,207 DEBUG [org.apache.jk.common.ChannelSocket] Call next 0 org.apache.jk.common.HandlerRequest@82254d
2004-04-02 12:40:17,207 DEBUG [org.apache.jk.common.HandlerRequest] Handling 2
2004-04-02 12:40:17,208 DEBUG [org.apache.jk.common.HandlerRequest] R( /fibo/)
2004-04-02 12:40:17,208 DEBUG [org.apache.jk.common.HandlerRequest] Calling next container org.apache.jk.server.JkCoyoteHandler
2004-04-02 12:40:17,209 DEBUG [org.apache.jk.server.JkCoyoteHandler] Invoke R( /fibo/) org.apache.coyote.Response@1df87b6 /fibo/
2004-04-02 12:40:17,220 DEBUG [org.apache.jk.server.JkCoyoteHandler] ACK
2004-04-02 12:40:17,242 DEBUG [org.apache.jk.server.JkCoyoteHandler] CLOSE
2004-04-02 12:40:17,242 DEBUG [org.apache.jk.server.JkCoyoteHandler] COMMIT
2004-04-02 12:40:17,243 DEBUG [org.apache.jk.server.JkCoyoteHandler] COMMIT sending headers org.apache.coyote.Response@1df87b6 === MimeHeaders ===
Location = http://192.168.1.8/fibo/index.html
run.log file
[...]
12:40:37,250 INFO [ChannelSocket] connection timeout reached
How can I solve this problem?.
This is my workers2.properties file:
#
# Sample workers configuration file for mod_jk2.
# Install this into your Apache's SERVER_ROOT/conf/workers2.properties
# See http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/doc/
# for more info.
#
[logger]
level=DEBUG
[config:]
debug=0
debugEnv=0
[uriMap:]
info=Maps the requests. Options: debug
debug=0
# Alternate file logger
[logger.file:0]
level=DEBUG
file=/var/log/httpd/mod_jk2.log
[shm:]
info=Scoreboard. Required for reconfiguration and status with multiprocess servers
file=/var/run/jk2.shm
size=1000000
debug=0
disabled=0
[workerEnv:]
info=Global server options
timing=1
debug=0
# Default Native Logger (apache2 or win32 )
# can be overriden to a file logger, useful
# when tracing win32 related issues
#logger=logger.file:0
[lb:lb]
info=Default load balancer.
debug=0
[lb:lb_1]
info=A second load balancer.
Debug=0
[channel.socket:localhost:8009]
info=Ajp13 forwarding over socket
debug=0
tomcatId=localhost:8009
[channel.socket:localhost:8809]
info=Ajp13 forwarding over socket to JBoss/Jetty
debug=0
tomcatId=localhost:8809
[status:]
info=Status worker, displays runtime informations
[uri:/jkstatus]
info=Display status information and checks the config file for changes.
group=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:/jmx-console/*]
info=JBoss JMX console
[uri:/fibo/*]
worker=ajp13:localhost:8009
Regards.
Javi Garzon