Re: Apache 1.3.27, Tomcat 4.1 mod_jk, not working
A Tomcat 404 generally means there is no Context configured in server.xml to match the request. In your case, it would typically mean that you're missing something like: Context path=/webapp docBase=webapp /Context John On Wed, 16 Jul 2003 19:57:16 -0700, Bongrip [EMAIL PROTECTED] wrote: Simon Pabst wrote: Since the 404 comes from Tomcat, Apache/mod_jk should be working. Can you call the jsp over Tomcat's HTTP Connector (port 8080)? like this http://localhost:8080/myapp/index.jsp instead of http://localhost/myapp/index.jsp Are there any errors in tomcat/logs/catalina.out or snip Oh my god, just shoot me. When I copied the test.jsp file I put it in $TOMCAT_HOME/webapps/test.jsp instead of $TOMCAT_HOME/webapps/ROOT/test.jsp. That works now. However one final problem, I am sure it is a configuration error. First, I created and alias under apache as so: Alias /webapp/ /usr/local/tomcat/webapps/ROOT/ Directory /usr/local/tomcat/webapps/ROOT Options Indexes FollowSymLinks MultiViews AllowOverride None Order allow,deny Allow from all /Directory Second, I added a JkMount to httpd.conf file as so: JkMount /webapp/*.jsp worker1 So why do I get a 404 with this URL: http://www.mydomain.com/webapp/test.jsp The 404 error I get comes from Tomcat. Thanks for all the help, CC - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Apache 1.3.27, Tomcat 4.1 mod_jk, not working
I build an apache 1.3.27 server and mod_jk as a DSO and it loads correctly and is recognized by the apache server. The mod_info module shows the module as being active and it lists my custom config. Here is my config: worker.list=worker1 worker.worker1.type=ajp13 worker.worker1.host=localhost worker.worker1.port=8009 worker.worker1.lbfactor=50 worker.worker1.cachesize=10 worker.worker1.cache_timeout=600 worker.worker1.socket_keepalive=1 worker.worker1.socket_timeout=300 I am enabled the Coyote connector on my Tomcat server. Apache Tomcat/4.1.24 Jul 16, 2003 11:53:28 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Jul 16, 2003 11:53:28 AM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on /0.0.0.0:8009 Jul 16, 2003 11:53:28 AM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=1/174 config=/usr/local/tomcat/conf/jk2.properties Jul 16, 2003 11:53:59 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection Jul 16, 2003 11:53:59 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection Jul 16, 2003 11:56:43 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection When I try to access a jsp page it gives me error 404. But the file is there and is readable by all. (0644) I am running tomcat 4.1.24 and using Sun's j2sdk 1.4.1 rev 03. I get nothing logged to either the apache logs or the tomcat logs when I make a request. Any ideas? Thxc, CC - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Apache 1.3.27, Tomcat 4.1 mod_jk, not working
Try using the AJP13 connector in http.conf instead of the Coyote/AJP13 connector. Also, comment out tomcat-standalone. i.e. comment out where Coyote starts on port 80. Hope this helps. -Ruchi -Original Message- From: Bongrip [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 16, 2003 3:51 PM To: Tomcat Users List Subject: Apache 1.3.27, Tomcat 4.1 mod_jk, not working I build an apache 1.3.27 server and mod_jk as a DSO and it loads correctly and is recognized by the apache server. The mod_info module shows the module as being active and it lists my custom config. Here is my config: worker.list=worker1 worker.worker1.type=ajp13 worker.worker1.host=localhost worker.worker1.port=8009 worker.worker1.lbfactor=50 worker.worker1.cachesize=10 worker.worker1.cache_timeout=600 worker.worker1.socket_keepalive=1 worker.worker1.socket_timeout=300 I am enabled the Coyote connector on my Tomcat server. Apache Tomcat/4.1.24 Jul 16, 2003 11:53:28 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Jul 16, 2003 11:53:28 AM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on /0.0.0.0:8009 Jul 16, 2003 11:53:28 AM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=1/174 config=/usr/local/tomcat/conf/jk2.properties Jul 16, 2003 11:53:59 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection Jul 16, 2003 11:53:59 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection Jul 16, 2003 11:56:43 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection When I try to access a jsp page it gives me error 404. But the file is there and is readable by all. (0644) I am running tomcat 4.1.24 and using Sun's j2sdk 1.4.1 rev 03. I get nothing logged to either the apache logs or the tomcat logs when I make a request. Any ideas? Thxc, CC - 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: Apache 1.3.27, Tomcat 4.1 mod_jk, not working
Did you configure mod_jk? JkMount, JkLogLevel, etc? - change JkLogLevel to info and post the results from mod_jk log file - post JkMount and the URL you are trying to use, as well as your Apache virtual host config John On Wed, 16 Jul 2003 12:50:57 -0700, Bongrip [EMAIL PROTECTED] wrote: I build an apache 1.3.27 server and mod_jk as a DSO and it loads correctly and is recognized by the apache server. The mod_info module shows the module as being active and it lists my custom config. Here is my config: worker.list=worker1 worker.worker1.type=ajp13 worker.worker1.host=localhost worker.worker1.port=8009 worker.worker1.lbfactor=50 worker.worker1.cachesize=10 worker.worker1.cache_timeout=600 worker.worker1.socket_keepalive=1 worker.worker1.socket_timeout=300 I am enabled the Coyote connector on my Tomcat server. Apache Tomcat/4.1.24 Jul 16, 2003 11:53:28 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Jul 16, 2003 11:53:28 AM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on /0.0.0.0:8009 Jul 16, 2003 11:53:28 AM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=1/174 config=/usr/local/tomcat/conf/jk2.properties Jul 16, 2003 11:53:59 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection Jul 16, 2003 11:53:59 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection Jul 16, 2003 11:56:43 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection When I try to access a jsp page it gives me error 404. But the file is there and is readable by all. (0644) I am running tomcat 4.1.24 and using Sun's j2sdk 1.4.1 rev 03. I get nothing logged to either the apache logs or the tomcat logs when I make a request. Any ideas? Thxc, CC - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Apache 1.3.27, Tomcat 4.1 mod_jk, not working
Tomcat never starts on port 80 by default. John On Wed, 16 Jul 2003 15:57:43 -0400, Ruchi Dayal [EMAIL PROTECTED] wrote: Try using the AJP13 connector in http.conf instead of the Coyote/AJP13 connector. Also, comment out tomcat-standalone. i.e. comment out where Coyote starts on port 80. Hope this helps. -Ruchi -Original Message- From: Bongrip [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 16, 2003 3:51 PM To: Tomcat Users List Subject: Apache 1.3.27, Tomcat 4.1 mod_jk, not working I build an apache 1.3.27 server and mod_jk as a DSO and it loads correctly and is recognized by the apache server. The mod_info module shows the module as being active and it lists my custom config. Here is my config: worker.list=worker1 worker.worker1.type=ajp13 worker.worker1.host=localhost worker.worker1.port=8009 worker.worker1.lbfactor=50 worker.worker1.cachesize=10 worker.worker1.cache_timeout=600 worker.worker1.socket_keepalive=1 worker.worker1.socket_timeout=300 I am enabled the Coyote connector on my Tomcat server. Apache Tomcat/4.1.24 Jul 16, 2003 11:53:28 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Jul 16, 2003 11:53:28 AM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on /0.0.0.0:8009 Jul 16, 2003 11:53:28 AM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=1/174 config=/usr/local/tomcat/conf/jk2.properties Jul 16, 2003 11:53:59 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection Jul 16, 2003 11:53:59 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection Jul 16, 2003 11:56:43 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection When I try to access a jsp page it gives me error 404. But the file is there and is readable by all. (0644) I am running tomcat 4.1.24 and using Sun's j2sdk 1.4.1 rev 03. I get nothing logged to either the apache logs or the tomcat logs when I make a request. Any ideas? Thxc, CC - 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] -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Apache 1.3.27, Tomcat 4.1 mod_jk, not working
I apologize. It was a typo. -Ruchi -Original Message- From: John Turner [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 16, 2003 4:08 PM To: Tomcat Users List Subject: Re: Apache 1.3.27, Tomcat 4.1 mod_jk, not working Tomcat never starts on port 80 by default. John On Wed, 16 Jul 2003 15:57:43 -0400, Ruchi Dayal [EMAIL PROTECTED] wrote: Try using the AJP13 connector in http.conf instead of the Coyote/AJP13 connector. Also, comment out tomcat-standalone. i.e. comment out where Coyote starts on port 80. Hope this helps. -Ruchi -Original Message- From: Bongrip [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 16, 2003 3:51 PM To: Tomcat Users List Subject: Apache 1.3.27, Tomcat 4.1 mod_jk, not working I build an apache 1.3.27 server and mod_jk as a DSO and it loads correctly and is recognized by the apache server. The mod_info module shows the module as being active and it lists my custom config. Here is my config: worker.list=worker1 worker.worker1.type=ajp13 worker.worker1.host=localhost worker.worker1.port=8009 worker.worker1.lbfactor=50 worker.worker1.cachesize=10 worker.worker1.cache_timeout=600 worker.worker1.socket_keepalive=1 worker.worker1.socket_timeout=300 I am enabled the Coyote connector on my Tomcat server. Apache Tomcat/4.1.24 Jul 16, 2003 11:53:28 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Jul 16, 2003 11:53:28 AM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on /0.0.0.0:8009 Jul 16, 2003 11:53:28 AM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=1/174 config=/usr/local/tomcat/conf/jk2.properties Jul 16, 2003 11:53:59 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection Jul 16, 2003 11:53:59 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection Jul 16, 2003 11:56:43 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection When I try to access a jsp page it gives me error 404. But the file is there and is readable by all. (0644) I am running tomcat 4.1.24 and using Sun's j2sdk 1.4.1 rev 03. I get nothing logged to either the apache logs or the tomcat logs when I make a request. Any ideas? Thxc, CC - 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] -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ - 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: Apache 1.3.27, Tomcat 4.1 mod_jk, not working
What does your mod_jk configuration in httpd.conf look like? Any errors in mod_jk.log? Does the 404 error come from tomcat or apache? At 12:50 16.07.2003 -0700, you wrote: I build an apache 1.3.27 server and mod_jk as a DSO and it loads correctly and is recognized by the apache server. The mod_info module shows the module as being active and it lists my custom config. Here is my config: worker.list=worker1 worker.worker1.type=ajp13 worker.worker1.host=localhost worker.worker1.port=8009 worker.worker1.lbfactor=50 worker.worker1.cachesize=10 worker.worker1.cache_timeout=600 worker.worker1.socket_keepalive=1 worker.worker1.socket_timeout=300 I am enabled the Coyote connector on my Tomcat server. Apache Tomcat/4.1.24 Jul 16, 2003 11:53:28 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Jul 16, 2003 11:53:28 AM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on /0.0.0.0:8009 Jul 16, 2003 11:53:28 AM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=1/174 config=/usr/local/tomcat/conf/jk2.properties Jul 16, 2003 11:53:59 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection Jul 16, 2003 11:53:59 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection Jul 16, 2003 11:56:43 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection When I try to access a jsp page it gives me error 404. But the file is there and is readable by all. (0644) I am running tomcat 4.1.24 and using Sun's j2sdk 1.4.1 rev 03. I get nothing logged to either the apache logs or the tomcat logs when I make a request. Any ideas? Thxc, CC - 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: Apache 1.3.27, Tomcat 4.1 mod_jk, not working
I think mod_jk works both with Coyote and old AJP13 connector (did for me at least). The tomcat http port on 8080 shouldn't cause any trouble, besides it helps with testing - if the JSP Page is accessible over 8080 then Apache/mod_jk is the problem. At 15:57 16.07.2003 -0400, you wrote: Try using the AJP13 connector in http.conf instead of the Coyote/AJP13 connector. Also, comment out tomcat-standalone. i.e. comment out where Coyote starts on port 80. Hope this helps. -Ruchi -Original Message- From: Bongrip [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 16, 2003 3:51 PM To: Tomcat Users List Subject: Apache 1.3.27, Tomcat 4.1 mod_jk, not working I build an apache 1.3.27 server and mod_jk as a DSO and it loads correctly and is recognized by the apache server. The mod_info module shows the module as being active and it lists my custom config. Here is my config: worker.list=worker1 worker.worker1.type=ajp13 worker.worker1.host=localhost worker.worker1.port=8009 worker.worker1.lbfactor=50 worker.worker1.cachesize=10 worker.worker1.cache_timeout=600 worker.worker1.socket_keepalive=1 worker.worker1.socket_timeout=300 I am enabled the Coyote connector on my Tomcat server. Apache Tomcat/4.1.24 Jul 16, 2003 11:53:28 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Jul 16, 2003 11:53:28 AM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on /0.0.0.0:8009 Jul 16, 2003 11:53:28 AM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=1/174 config=/usr/local/tomcat/conf/jk2.properties Jul 16, 2003 11:53:59 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection Jul 16, 2003 11:53:59 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection Jul 16, 2003 11:56:43 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection When I try to access a jsp page it gives me error 404. But the file is there and is readable by all. (0644) I am running tomcat 4.1.24 and using Sun's j2sdk 1.4.1 rev 03. I get nothing logged to either the apache logs or the tomcat logs when I make a request. Any ideas? Thxc, CC - 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: Apache 1.3.27, Tomcat 4.1 mod_jk, not working
John Turner wrote: Did you configure mod_jk? JkMount, JkLogLevel, etc? - change JkLogLevel to info and post the results from mod_jk log file - post JkMount and the URL you are trying to use, as well as your Apache virtual host config John On Wed, 16 Jul 2003 12:50:57 -0700, Bongrip [EMAIL PROTECTED] wrote: I build an apache 1.3.27 server and mod_jk as a DSO and it loads correctly and is recognized by the apache server. The mod_info module shows the module as being active and it lists my custom config. Here is my config: worker.list=worker1 worker.worker1.type=ajp13 worker.worker1.host=localhost worker.worker1.port=8009 worker.worker1.lbfactor=50 worker.worker1.cachesize=10 worker.worker1.cache_timeout=600 worker.worker1.socket_keepalive=1 worker.worker1.socket_timeout=300 I am enabled the Coyote connector on my Tomcat server. Apache Tomcat/4.1.24 Jul 16, 2003 11:53:28 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Jul 16, 2003 11:53:28 AM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on /0.0.0.0:8009 Jul 16, 2003 11:53:28 AM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=1/174 config=/usr/local/tomcat/conf/jk2.properties Jul 16, 2003 11:53:59 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection Jul 16, 2003 11:53:59 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection Jul 16, 2003 11:56:43 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection When I try to access a jsp page it gives me error 404. But the file is there and is readable by all. (0644) I am running tomcat 4.1.24 and using Sun's j2sdk 1.4.1 rev 03. I get nothing logged to either the apache logs or the tomcat logs when I make a request. Any ideas? Thxc, CC - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Okay, I think I fixed one problem but still getting 404 error. Here is my mod_jk.log after a fresh server start and a single request for a file called test.jsp: cheeba:/usr/local/apache/logs #cat mod_jk.log [Wed Jul 16 13:20:55 2003] [jk_uri_worker_map.c (172)]: Into jk_uri_worker_map_t::uri_worker_map_alloc [Wed Jul 16 13:20:55 2003] [jk_uri_worker_map.c (375)]: Into jk_uri_worker_map_t::uri_worker_map_open [Wed Jul 16 13:20:55 2003] [jk_uri_worker_map.c (396)]: jk_uri_worker_map_t::uri_worker_map_open, rule map size is 2 [Wed Jul 16 13:20:55 2003] [jk_uri_worker_map.c (299)]: Into jk_uri_worker_map_t::uri_worker_map_open, suffix rule /.jsp=worker1 was added [Wed Jul 16 13:20:55 2003] [jk_uri_worker_map.c (299)]: Into jk_uri_worker_map_t::uri_worker_map_open, suffix rule /webapp/.jsp=worker1 was added [Wed Jul 16 13:20:55 2003] [jk_uri_worker_map.c (408)]: Into jk_uri_worker_map_t::uri_worker_map_open, there are 2 rules [Wed Jul 16 13:20:55 2003] [jk_uri_worker_map.c (422)]: jk_uri_worker_map_t::uri_worker_map_open, done [Wed Jul 16 13:20:55 2003] [jk_worker.c (88)]: Into wc_open [Wed Jul 16 13:20:55 2003] [jk_worker.c (222)]: Into build_worker_map, creating 1 workers [Wed Jul 16 13:20:55 2003] [jk_worker.c (228)]: build_worker_map, creating worker worker1 [Wed Jul 16 13:20:55 2003] [jk_worker.c (148)]: Into wc_create_worker [Wed Jul 16 13:20:55 2003] [jk_worker.c (162)]: wc_create_worker, about to create instance worker1 of ajp13 [Wed Jul 16 13:20:55 2003] [jk_ajp13_worker.c (108)]: Into ajp13_worker_factory [Wed Jul 16 13:20:55 2003] [jk_worker.c (171)]: wc_create_worker, about to validate and init worker1 [Wed Jul 16 13:20:55 2003] [jk_ajp_common.c (1343)]: Into jk_worker_t::validate [Wed Jul 16 13:20:55 2003] [jk_ajp_common.c (1364)]: In jk_worker_t::validate for worker worker1 contact is localhost:8009 [Wed Jul 16 13:20:55 2003] [jk_ajp_common.c (1397)]: Into jk_worker_t::init [Wed Jul 16 13:20:55 2003] [jk_ajp_common.c (1421)]: In jk_worker_t::init, setting socket timeout to 300 [Wed Jul 16 13:20:55 2003] [jk_worker.c (187)]: wc_create_worker, done [Wed Jul 16 13:20:55 2003] [jk_worker.c (238)]: build_worker_map, removing old worker1 worker [Wed Jul 16 13:20:55 2003] [jk_worker.c (250)]: build_worker_map, done [Wed Jul 16 13:20:55 2003] [jk_worker.c (111)]: wc_open, done 1 [Wed Jul 16 13:20:55 2003] [jk_uri_worker_map.c (172)]: Into jk_uri_worker_map_t::uri_worker_map_alloc [Wed Jul 16 13:20:55 2003] [jk_uri_worker_map.c (375)]: Into jk_uri_worker_map_t::uri_worker_map_open [Wed Jul 16 13:20:55 2003] [jk_uri_worker_map.c (396)]: jk_uri_worker_map_t::uri_worker_map_open, rule map size is 2 [Wed Jul 16 13:20:55 2003] [jk_uri_worker_map.c (299)]: Into jk_uri_worker_map_t::uri_worker_map_open, suffix rule /.jsp=worker1 was added [Wed Jul 16 13:20:55 2003] [jk_uri_worker_map.c (299)]: Into
Re: Apache 1.3.27, Tomcat 4.1 mod_jk, not working
Simon Pabst wrote: What does your mod_jk configuration in httpd.conf look like? Any errors in mod_jk.log? Does the 404 error come from tomcat or apache? At 12:50 16.07.2003 -0700, you wrote: I build an apache 1.3.27 server and mod_jk as a DSO and it loads correctly and is recognized by the apache server. The mod_info module shows the module as being active and it lists my custom config. Here is my config: worker.list=worker1 worker.worker1.type=ajp13 worker.worker1.host=localhost worker.worker1.port=8009 worker.worker1.lbfactor=50 worker.worker1.cachesize=10 worker.worker1.cache_timeout=600 worker.worker1.socket_keepalive=1 worker.worker1.socket_timeout=300 I am enabled the Coyote connector on my Tomcat server. Apache Tomcat/4.1.24 Jul 16, 2003 11:53:28 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Jul 16, 2003 11:53:28 AM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on /0.0.0.0:8009 Jul 16, 2003 11:53:28 AM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=1/174 config=/usr/local/tomcat/conf/jk2.properties Jul 16, 2003 11:53:59 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection Jul 16, 2003 11:53:59 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection Jul 16, 2003 11:56:43 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection When I try to access a jsp page it gives me error 404. But the file is there and is readable by all. (0644) I am running tomcat 4.1.24 and using Sun's j2sdk 1.4.1 rev 03. I get nothing logged to either the apache logs or the tomcat logs when I make a request. Any ideas? Thxc, CC - 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] The 404 error comes from Tomcat. -Chuck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Apache 1.3.27, Tomcat 4.1 mod_jk, not working
This will go a lot faster if you please post your JK configuration. It could be as simple as you having the JkMount messed up, or it could be something else. John On Wed, 16 Jul 2003 13:24:01 -0700, Bongrip [EMAIL PROTECTED] wrote: John Turner wrote: Did you configure mod_jk? JkMount, JkLogLevel, etc? - change JkLogLevel to info and post the results from mod_jk log file - post JkMount and the URL you are trying to use, as well as your Apache virtual host config John On Wed, 16 Jul 2003 12:50:57 -0700, Bongrip [EMAIL PROTECTED] wrote: I build an apache 1.3.27 server and mod_jk as a DSO and it loads correctly and is recognized by the apache server. The mod_info module shows the module as being active and it lists my custom config. Here is my config: worker.list=worker1 worker.worker1.type=ajp13 worker.worker1.host=localhost worker.worker1.port=8009 worker.worker1.lbfactor=50 worker.worker1.cachesize=10 worker.worker1.cache_timeout=600 worker.worker1.socket_keepalive=1 worker.worker1.socket_timeout=300 I am enabled the Coyote connector on my Tomcat server. Apache Tomcat/4.1.24 Jul 16, 2003 11:53:28 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Jul 16, 2003 11:53:28 AM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on /0.0.0.0:8009 Jul 16, 2003 11:53:28 AM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=1/174 config=/usr/local/tomcat/conf/jk2.properties Jul 16, 2003 11:53:59 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection Jul 16, 2003 11:53:59 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection Jul 16, 2003 11:56:43 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection When I try to access a jsp page it gives me error 404. But the file is there and is readable by all. (0644) I am running tomcat 4.1.24 and using Sun's j2sdk 1.4.1 rev 03. I get nothing logged to either the apache logs or the tomcat logs when I make a request. Any ideas? Thxc, CC - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Okay, I think I fixed one problem but still getting 404 error. Here is my mod_jk.log after a fresh server start and a single request for a file called test.jsp: cheeba:/usr/local/apache/logs #cat mod_jk.log [Wed Jul 16 13:20:55 2003] [jk_uri_worker_map.c (172)]: Into jk_uri_worker_map_t::uri_worker_map_alloc [Wed Jul 16 13:20:55 2003] [jk_uri_worker_map.c (375)]: Into jk_uri_worker_map_t::uri_worker_map_open [Wed Jul 16 13:20:55 2003] [jk_uri_worker_map.c (396)]: jk_uri_worker_map_t::uri_worker_map_open, rule map size is 2 [Wed Jul 16 13:20:55 2003] [jk_uri_worker_map.c (299)]: Into jk_uri_worker_map_t::uri_worker_map_open, suffix rule /.jsp=worker1 was added [Wed Jul 16 13:20:55 2003] [jk_uri_worker_map.c (299)]: Into jk_uri_worker_map_t::uri_worker_map_open, suffix rule /webapp/.jsp=worker1 was added [Wed Jul 16 13:20:55 2003] [jk_uri_worker_map.c (408)]: Into jk_uri_worker_map_t::uri_worker_map_open, there are 2 rules [Wed Jul 16 13:20:55 2003] [jk_uri_worker_map.c (422)]: jk_uri_worker_map_t::uri_worker_map_open, done [Wed Jul 16 13:20:55 2003] [jk_worker.c (88)]: Into wc_open [Wed Jul 16 13:20:55 2003] [jk_worker.c (222)]: Into build_worker_map, creating 1 workers [Wed Jul 16 13:20:55 2003] [jk_worker.c (228)]: build_worker_map, creating worker worker1 [Wed Jul 16 13:20:55 2003] [jk_worker.c (148)]: Into wc_create_worker [Wed Jul 16 13:20:55 2003] [jk_worker.c (162)]: wc_create_worker, about to create instance worker1 of ajp13 [Wed Jul 16 13:20:55 2003] [jk_ajp13_worker.c (108)]: Into ajp13_worker_factory [Wed Jul 16 13:20:55 2003] [jk_worker.c (171)]: wc_create_worker, about to validate and init worker1 [Wed Jul 16 13:20:55 2003] [jk_ajp_common.c (1343)]: Into jk_worker_t::validate [Wed Jul 16 13:20:55 2003] [jk_ajp_common.c (1364)]: In jk_worker_t::validate for worker worker1 contact is localhost:8009 [Wed Jul 16 13:20:55 2003] [jk_ajp_common.c (1397)]: Into jk_worker_t::init [Wed Jul 16 13:20:55 2003] [jk_ajp_common.c (1421)]: In jk_worker_t::init, setting socket timeout to 300 [Wed Jul 16 13:20:55 2003] [jk_worker.c (187)]: wc_create_worker, done [Wed Jul 16 13:20:55 2003] [jk_worker.c (238)]: build_worker_map, removing old worker1 worker [Wed Jul 16 13:20:55 2003] [jk_worker.c (250)]: build_worker_map, done [Wed Jul 16 13:20:55 2003] [jk_worker.c (111)]: wc_open, done 1 [Wed Jul 16 13:20:55 2003] [jk_uri_worker_map.c (172)]: Into jk_uri_worker_map_t::uri_worker_map_alloc [Wed Jul 16 13:20:55 2003] [jk_uri_worker_map.c (375)]: Into jk_uri_worker_map_t::uri_worker_map_open [Wed Jul 16 13:20:55 2003] [jk_uri_worker_map.c (396)]:
Re: Apache 1.3.27, Tomcat 4.1 mod_jk, not working
From: Bongrip [EMAIL PROTECTED] When I try to access a jsp page it gives me error 404. But the file is there and is readable by all. (0644) I am running tomcat 4.1.24 and using Sun's j2sdk 1.4.1 rev 03. I get nothing logged to either the apache logs or the tomcat logs when I make a request. is it under CATALINA_HOME/webapps ? what's the permissions in that directory? I had to change the permissions it had after installing from RPM in order not to get a 404 error.. I did: # chmod 775 /var/tomcat4/webapps # ls -l /var/tomcat4/ | grep webapps drwxrwxr-x7 root tomcat4 1024 Jul 16 11:34 webapps is this ok, or am I having some security isse? if not, any idea why the RPM installed it with permissions that didn't allow the access?? Juan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Apache 1.3.27, Tomcat 4.1 mod_jk, not working
John Turner wrote: This will go a lot faster if you please post your JK configuration. It could be as simple as you having the JkMount messed up, or it could be something else. John On Wed, 16 Jul 2003 13:24:01 -0700, Bongrip [EMAIL PROTECTED] wrote: John Turner wrote: Did you configure mod_jk? JkMount, JkLogLevel, etc? - change JkLogLevel to info and post the results from mod_jk log file - post JkMount and the URL you are trying to use, as well as your Apache virtual host config John On Wed, 16 Jul 2003 12:50:57 -0700, Bongrip [EMAIL PROTECTED] wrote: I build an apache 1.3.27 server and mod_jk as a DSO and it loads correctly and is recognized by the apache server. The mod_info module shows the module as being active and it lists my custom config. Here is my config: worker.list=worker1 worker.worker1.type=ajp13 worker.worker1.host=localhost worker.worker1.port=8009 worker.worker1.lbfactor=50 worker.worker1.cachesize=10 worker.worker1.cache_timeout=600 worker.worker1.socket_keepalive=1 worker.worker1.socket_timeout=300 I am enabled the Coyote connector on my Tomcat server. Apache Tomcat/4.1.24 Jul 16, 2003 11:53:28 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Jul 16, 2003 11:53:28 AM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on /0.0.0.0:8009 Jul 16, 2003 11:53:28 AM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=1/174 config=/usr/local/tomcat/conf/jk2.properties Jul 16, 2003 11:53:59 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection Jul 16, 2003 11:53:59 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection Jul 16, 2003 11:56:43 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection When I try to access a jsp page it gives me error 404. But the file is there and is readable by all. (0644) I am running tomcat 4.1.24 and using Sun's j2sdk 1.4.1 rev 03. I get nothing logged to either the apache logs or the tomcat logs when I make a request. Any ideas? Thxc, CC - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Okay, I think I fixed one problem but still getting 404 error. Here is my mod_jk.log after a fresh server start and a single request for a file called test.jsp: cheeba:/usr/local/apache/logs #cat mod_jk.log [Wed Jul 16 13:20:55 2003] [jk_uri_worker_map.c (172)]: Into jk_uri_worker_map_t::uri_worker_map_alloc [Wed Jul 16 13:20:55 2003] [jk_uri_worker_map.c (375)]: Into jk_uri_worker_map_t::uri_worker_map_open [Wed Jul 16 13:20:55 2003] [jk_uri_worker_map.c (396)]: jk_uri_worker_map_t::uri_worker_map_open, rule map size is 2 [Wed Jul 16 13:20:55 2003] [jk_uri_worker_map.c (299)]: Into jk_uri_worker_map_t::uri_worker_map_open, suffix rule /.jsp=worker1 was added [Wed Jul 16 13:20:55 2003] [jk_uri_worker_map.c (299)]: Into jk_uri_worker_map_t::uri_worker_map_open, suffix rule /webapp/.jsp=worker1 was added [Wed Jul 16 13:20:55 2003] [jk_uri_worker_map.c (408)]: Into jk_uri_worker_map_t::uri_worker_map_open, there are 2 rules [Wed Jul 16 13:20:55 2003] [jk_uri_worker_map.c (422)]: jk_uri_worker_map_t::uri_worker_map_open, done [Wed Jul 16 13:20:55 2003] [jk_worker.c (88)]: Into wc_open [Wed Jul 16 13:20:55 2003] [jk_worker.c (222)]: Into build_worker_map, creating 1 workers [Wed Jul 16 13:20:55 2003] [jk_worker.c (228)]: build_worker_map, creating worker worker1 [Wed Jul 16 13:20:55 2003] [jk_worker.c (148)]: Into wc_create_worker [Wed Jul 16 13:20:55 2003] [jk_worker.c (162)]: wc_create_worker, about to create instance worker1 of ajp13 [Wed Jul 16 13:20:55 2003] [jk_ajp13_worker.c (108)]: Into ajp13_worker_factory [Wed Jul 16 13:20:55 2003] [jk_worker.c (171)]: wc_create_worker, about to validate and init worker1 [Wed Jul 16 13:20:55 2003] [jk_ajp_common.c (1343)]: Into jk_worker_t::validate [Wed Jul 16 13:20:55 2003] [jk_ajp_common.c (1364)]: In jk_worker_t::validate for worker worker1 contact is localhost:8009 [Wed Jul 16 13:20:55 2003] [jk_ajp_common.c (1397)]: Into jk_worker_t::init [Wed Jul 16 13:20:55 2003] [jk_ajp_common.c (1421)]: In jk_worker_t::init, setting socket timeout to 300 [Wed Jul 16 13:20:55 2003] [jk_worker.c (187)]: wc_create_worker, done [Wed Jul 16 13:20:55 2003] [jk_worker.c (238)]: build_worker_map, removing old worker1 worker [Wed Jul 16 13:20:55 2003] [jk_worker.c (250)]: build_worker_map, done [Wed Jul 16 13:20:55 2003] [jk_worker.c (111)]: wc_open, done 1 [Wed Jul 16 13:20:55 2003] [jk_uri_worker_map.c (172)]: Into jk_uri_worker_map_t::uri_worker_map_alloc [Wed Jul 16 13:20:55 2003] [jk_uri_worker_map.c (375)]: Into jk_uri_worker_map_t::uri_worker_map_open [Wed Jul 16 13:20:55 2003] [jk_uri_worker_map.c (396)]:
Re: Apache 1.3.27, Tomcat 4.1 mod_jk, not working
Juan Nin wrote: From: Bongrip [EMAIL PROTECTED] When I try to access a jsp page it gives me error 404. But the file is there and is readable by all. (0644) I am running tomcat 4.1.24 and using Sun's j2sdk 1.4.1 rev 03. I get nothing logged to either the apache logs or the tomcat logs when I make a request. is it under CATALINA_HOME/webapps ? what's the permissions in that directory? I had to change the permissions it had after installing from RPM in order not to get a 404 error.. I did: # chmod 775 /var/tomcat4/webapps # ls -l /var/tomcat4/ | grep webapps drwxrwxr-x7 root tomcat4 1024 Jul 16 11:34 webapps is this ok, or am I having some security isse? if not, any idea why the RPM installed it with permissions that didn't allow the access?? Juan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] No, perms are all okay. /usr/local/tomcat = 0755 /usr/local/tomcat/webapps = 0755 /usr/local/tomcat/webapps/ROOT/ = 0755 /usr/local/tomcat/webapps/ROOT/test.jsp = 0644 ?? -CC - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Apache 1.3.27, Tomcat 4.1 mod_jk, not working
Since the 404 comes from Tomcat, Apache/mod_jk should be working. Can you call the jsp over Tomcat's HTTP Connector (port 8080)? like this http://localhost:8080/myapp/index.jsp instead of http://localhost/myapp/index.jsp Are there any errors in tomcat/logs/catalina.out or The 404 error comes from Tomcat. -Chuck - 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: Apache 1.3.27, Tomcat 4.1 mod_jk, not working
Think John meant the Jk Configuration entries of your httpd.conf, not your worers.properties - i also asked for that in a previous post. If you want help, answer the questions :-) At 14:35 16.07.2003 -0700, you wrote: John Turner wrote: This will go a lot faster if you please post your JK configuration. It could be as simple as you having the JkMount messed up, or it could be something else. John Yea, it was in the original post: worker.list=worker1 worker.worker1.type=ajp13 worker.worker1.host=localhost worker.worker1.port=8009 worker.worker1.lbfactor=50 worker.worker1.cachesize=10 worker.worker1.cache_timeout=600 worker.worker1.socket_keepalive=1 worker.worker1.socket_timeout=300 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Apache 1.3.27, Tomcat 4.1 mod_jk, not working
Simon Pabst wrote: Since the 404 comes from Tomcat, Apache/mod_jk should be working. Can you call the jsp over Tomcat's HTTP Connector (port 8080)? like this http://localhost:8080/myapp/index.jsp instead of http://localhost/myapp/index.jsp Are there any errors in tomcat/logs/catalina.out or snip Oh my god, just shoot me. When I copied the test.jsp file I put it in $TOMCAT_HOME/webapps/test.jsp instead of $TOMCAT_HOME/webapps/ROOT/test.jsp. That works now. However one final problem, I am sure it is a configuration error. First, I created and alias under apache as so: Alias /webapp/ /usr/local/tomcat/webapps/ROOT/ Directory /usr/local/tomcat/webapps/ROOT Options Indexes FollowSymLinks MultiViews AllowOverride None Order allow,deny Allow from all /Directory Second, I added a JkMount to httpd.conf file as so: JkMount /webapp/*.jsp worker1 So why do I get a 404 with this URL: http://www.mydomain.com/webapp/test.jsp The 404 error I get comes from Tomcat. Thanks for all the help, CC - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Apache 1.3.27, Tomcat 4.1 mod_jk, not working
Simon Pabst wrote: Think John meant the Jk Configuration entries of your httpd.conf, not your worers.properties - i also asked for that in a previous post. If you want help, answer the questions :-) At 14:35 16.07.2003 -0700, you wrote: John Turner wrote: This will go a lot faster if you please post your JK configuration. It could be as simple as you having the JkMount messed up, or it could be something else. John Yea, it was in the original post: worker.list=worker1 worker.worker1.type=ajp13 worker.worker1.host=localhost worker.worker1.port=8009 worker.worker1.lbfactor=50 worker.worker1.cachesize=10 worker.worker1.cache_timeout=600 worker.worker1.socket_keepalive=1 worker.worker1.socket_timeout=300 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] My bad, I thought I posted those too: Here is the httpd.conf mod_jk config entries: # MOD_JK Config JkWorkersFile conf/workers.properties JkLogFile /usr/local/apache/logs/mod_jk.log JkLogLevel debug JkLogStampFormat[%a %b %d %H:%M:%S %Y] JkMount /*.jsp worker1 JkMount /webapp/*.jsp worker1 I placed these entries right after the AddModule directives. -Chuck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
