Re: How To Build mod_jk?????
Eric J. Pinnell wrote: Hi, I don't use ant. I use make. It appears that you are trying to build JK2. In the native2 directory: ./configure --with-apxs2=/path/to/apache/bin/apxs make Yes, that was exactly what I was trying. configure and make both complete fine, however I never get the 2 resulting .so files anywhere in the filesystem. ??? -CC - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How To Build mod_jk2 with JNI Support
I get this error during configure: need to check for Perl first, apxs depends on it... checking for perl... /usr/bin/perl building connector for apache-2.0 configure: error: valid apr source dir location required Here is my configure command: ./configure --with-apxs2=/usr/local/apache2/bin/apxs --with-tomcat41=/usr/local/jakarta-tomcat-4.1.27 --with-java-home=/usr/local/jakarta-tomcat-4.1.27/j2sdk1.4.2 --with-jni --with-apache13=no --with-apr=/usr/local/src/httpd-2.0.47/srclib/apr Any ideas? Thx, CC - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How To Build mod_jk?????
I have been trying to build mod_jk and it seems the documentation is lacking and the instructions do not work. First my system: Solaris 8 64-bit with latest patch cluster gcc 3.3 AND Sun's Forte Dev 7 compiler Tomcat 4.1.27 (installed and running fine) Apache 2.0.47 (installed and running fine) j2sdk1.4.1_04 Ant 1.5.4 I downloaded jakarta-tomcat-connectors-jk2-2.0.2-src and extracted it. I then renamed build.properties.sample to build.properties and edited all the paths. The documentation says to run 'ant', here is the output: Buildfile: build.xml detect: [echo] jakarta-tomcat-connectors prepare: BUILD FAILED file:/root/jakarta-tomcat-connectors-jk2-2.0.2-src/jk/build.xml:105: Warning: Could not find file /root/jakarta-tomcat-connectors-jk2-2.0.2-src/coyote/build/lib/tomcat-coyote.jar to copy. Total time: 3 seconds I then changed to this directory: jakarta-tomcat-connectors-jk2-2.0.2-src/jk/native2 % CC=gcc ./configure --with-apxs2=/usr/local/apache2/bin/apxs --with-tom cat41=/usr/local/jakarta-tomcat-4.1.27 --with-java-home=/usr/j2sdk1.4.1_04 --with-jni % make Make completes and I then get these 2 files in /usr/local/apache2/modules: -rw-r--r-- 1 root other 945542 Aug 16 16:50 mod_jk.a -rw-r--r-- 1 root other663 Aug 16 16:50 mod_jk.la At then end of the make it also says this: libtool: install: warning: remember to run `libtool --finish /usr/local/apache2/modules' So, if I do that: hurley:~/jakarta-tomcat-connectors-jk2-2.0.2-src/jk/native2 #libtool --finish /usr/local/apache2/modules -- Libraries have been installed in: /usr/local/apache2/modules If you ever happen to want to link against installed libraries in a given directory, LIBDIR, you must either use libtool, and specify the full pathname of the library, or use the `-LLIBDIR' flag during linking and do at least one of the following: - add LIBDIR to the `LD_LIBRARY_PATH' environment variable during execution - use the `-RLIBDIR' linker flag See any operating system documentation about shared libraries for more information, such as the ld(1) and ld.so(8) manual pages. -- Now when I look in /usr/local/apache2/modules: -rw-r--r-- 1 root other 945542 Aug 16 16:50 mod_jk.a -rw-r--r-- 1 root other663 Aug 16 16:50 mod_jk.la What am I missing or what is the problem? Thanks, Chuck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem with allowLinking=true
I have the following symbolic link under webapps/ROOT lrwxrwxrwx1 root root 9 Aug 2 10:08 orca - /mnt/orca /mnt/orca is an NFS mounted filesytems containing some web content. I added allowLinking=true to the ROOT context in conf/server.xml !-- Tomcat Root Context -- Context path= docBase=ROOT debug=0 reloadable=true allowLinking=true / I then restarted the tomcat server and tried to access http://localhost/orca/ and I get error 404. I am running the HTTP connector on port 80. Nothing else seems to be logged anywhere. 10.250.200.68 - - [03/Aug/2003:11:28:58 -0800] GET /orca/ HTTP/1.1 404 683 What am I doing wrong? I am running jakarta-tomcat-4.1.18 and using j2sdk1.4.0_02. The OS is Red Hat 8.0. Thanks for any help, CC - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Following Symbolic Links under ROOT
I want to enable symbolic links under the ROOT webapp, but cannot find any documentatiob on configuring this. Is this possible to do? I have a directory of data that is symbolically links to the webapps/ROOT directory. ranger:/usr/local/tomcat/webapps/ROOT#ls -l total 192 lrwxrwxrwx1 root root 9Aug 2 10:08 data - /mnt/data drwxr-xr-x4 tomcat tomcat 4096 Aug 2 10:09 WEB-INF Thanks, CC - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Can't get Tomcat 4.X to startup on RH 9
[EMAIL PROTECTED] wrote: Hi, I'm in a new position and trying to put together a replacement webserver that can run an existing set of servlets. The servlets were previously executed with JServ but I want to switch to Tomcat. My environment is Red Hat Linux 9, Apache 2.0.40, JDBC classes12.zip jdk 1.2.2 and Tomcat 4.1.24. I installed Tomcat with the rpm tomcat4-4.1.24-full.2jpp. I'm trying to start Tomcat as root (for testing) and I've set the following environment variables in the root profile: JAVA_HOME=/usr/local/java CATALINA_HOME=/var/tomcat4 CLASSPATH=$CLASSPATH:/var/tomcat4/common/lib/servlet.jar:/usr/local/java/classes /classes12.zip export USERNAME BASH_ENV PATH JAVA_HOME CATALINA_HOME CLASSPATH When I start Tomcat via /etc/rc.d/init.d/tomacat4 start it fails and I get the text below in the Catalina log file. I'm not an experienced java programmerand any help would be greatly appreciated! Jeff H. [EMAIL PROTECTED] catalina log file: java.lang.UnsupportedClassVersionError: org/apache/commons/beanutils/BeanUtils (Unsupported major.minor version 47.0) at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:471) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:103) at java.net.URLClassLoader.defineClass(URLClassLoader.java:242) at java.net.URLClassLoader.access$1(URLClassLoader.java:210) at java.net.URLClassLoader$1.run(URLClassLoader.java:191) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:185) at org.apache.catalina.loader.StandardClassLoader.findClass(Unknown Source) at org.apache.catalina.loader.StandardClassLoader.loadClass(Unknown Source) at org.apache.catalina.loader.StandardClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:308) at org.apache.commons.digester.SetPropertiesRule.begin(SetPropertiesRule.java:255) at org.apache.commons.digester.Rule.begin(Rule.java:200) at org.apache.commons.digester.Digester.startElement(Digester.java:1268) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.impl.XMLNamespaceBinder.startElement(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.commons.digester.Digester.parse(Digester.java:1543) at org.apache.catalina.startup.Catalina.start(Unknown Source) at org.apache.catalina.startup.Catalina.execute(Unknown Source) at org.apache.catalina.startup.Catalina.process(Unknown Source) at java.lang.reflect.Method.invoke(Native Method) at org.apache.catalina.startup.Bootstrap.main(Unknown Source) [ERROR] Digester - -Begin event threw error java.lang.UnsupportedClassVersionError: org/apache/commons/beanutils/BeanUtils (Unsupported major.minor version 47.0) Exception during startup processing java.lang.reflect.InvocationTargetException: java.lang.UnsupportedClassVersionError: org/apache/commons/beanutils/BeanUtils (Unsupported major.minor version 47.0) at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:471) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:103) at java.net.URLClassLoader.defineClass(URLClassLoader.java:242) at java.net.URLClassLoader.access$1(URLClassLoader.java:210) at java.net.URLClassLoader$1.run(URLClassLoader.java:191) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:185) at org.apache.catalina.loader.StandardClassLoader.findClass(Unknown Source) at org.apache.catalina.loader.StandardClassLoader.loadClass(Unknown Source) at org.apache.catalina.loader.StandardClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:308) at org.apache.commons.digester.SetPropertiesRule.begin(SetPropertiesRule.java:255) at org.apache.commons.digester.Rule.begin(Rule.java:200) at
Re: Can't get Tomcat 4.X to startup on RH 9
Jeff Howard wrote: I agree there may be a versioning/compatibility problem. I'm using jdk1.2.2 because I believe I need that to work with the jdbc drivers. Bongrip wrote: [EMAIL PROTECTED] wrote: Hi, I'm in a new position and trying to put together a replacement webserver that can run an existing set of servlets. The servlets were previously executed with JServ but I want to switch to Tomcat. My environment is Red Hat Linux 9, Apache 2.0.40, JDBC classes12.zip jdk 1.2.2 and Tomcat 4.1.24. I installed Tomcat with the rpm tomcat4-4.1.24-full.2jpp. I'm trying to start Tomcat as root (for testing) and I've set the following environment variables in the root profile: JAVA_HOME=/usr/local/java CATALINA_HOME=/var/tomcat4 CLASSPATH=$CLASSPATH:/var/tomcat4/common/lib/servlet.jar:/usr/local/java/classes /classes12.zip export USERNAME BASH_ENV PATH JAVA_HOME CATALINA_HOME CLASSPATH When I start Tomcat via /etc/rc.d/init.d/tomacat4 start it fails and I get the text below in the Catalina log file. I'm not an experienced java programmerand any help would be greatly appreciated! Jeff H. [EMAIL PROTECTED] catalina log file: java.lang.UnsupportedClassVersionError: org/apache/commons/beanutils/BeanUtils (Unsupported major.minor version 47.0) at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:471) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:103) at java.net.URLClassLoader.defineClass(URLClassLoader.java:242) at java.net.URLClassLoader.access$1(URLClassLoader.java:210) at java.net.URLClassLoader$1.run(URLClassLoader.java:191) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:185) at org.apache.catalina.loader.StandardClassLoader.findClass(Unknown Source) at org.apache.catalina.loader.StandardClassLoader.loadClass(Unknown Source) at org.apache.catalina.loader.StandardClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:308) at org.apache.commons.digester.SetPropertiesRule.begin(SetPropertiesRule.java:255) at org.apache.commons.digester.Rule.begin(Rule.java:200) at org.apache.commons.digester.Digester.startElement(Digester.java:1268) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.impl.XMLNamespaceBinder.startElement(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.commons.digester.Digester.parse(Digester.java:1543) at org.apache.catalina.startup.Catalina.start(Unknown Source) at org.apache.catalina.startup.Catalina.execute(Unknown Source) at org.apache.catalina.startup.Catalina.process(Unknown Source) at java.lang.reflect.Method.invoke(Native Method) at org.apache.catalina.startup.Bootstrap.main(Unknown Source) [ERROR] Digester - -Begin event threw error java.lang.UnsupportedClassVersionError: org/apache/commons/beanutils/BeanUtils (Unsupported major.minor version 47.0) Exception during startup processing java.lang.reflect.InvocationTargetException: java.lang.UnsupportedClassVersionError: org/apache/commons/beanutils/BeanUtils (Unsupported major.minor version 47.0) at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:471) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:103) at java.net.URLClassLoader.defineClass(URLClassLoader.java:242) at java.net.URLClassLoader.access$1(URLClassLoader.java:210) at java.net.URLClassLoader$1.run(URLClassLoader.java:191) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:185) at org.apache.catalina.loader.StandardClassLoader.findClass(Unknown Source) at org.apache.catalina.loader.StandardClassLoader.loadClass(Unknown Source) at org.apache.catalina.loader.StandardClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClassInternal
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
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
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
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
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]
Is there a search engine for the mailing list archive?
I couild not find anywhere to search the mailing list archive. I am sure this question has been asked before, but how do I enable PHP support under Tomcat 4.x? I am porting a PHP based application to Java and need to have both running in parrallel until completed. Thx, CC - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
