Re: JkUnMount is unknown to apache
to the best of my knowledge JkUnMount is only available at version mod_jk 1.2.7 and above if you are using apache2 mod_jk lives at apche2/modules/ as something like mod_jk.so if you check your apache startup log , maybe error_log you may see something like: [Wed Jul 13 12:22:26 2005] [notice] Apache/2.0.50 (Unix) mod_ssl/2.0.50 OpenSSL/0.9.7d mod_jk/1.2.5 configured -- resuming normal operations notice that the mod_jk is listed with version 1.2.5 in this case hope this is useful, this info is based on a Tomcat 5.5.9, Apache 2.0.5 on Solaris 9 Colby C. Meyer Applications Architect First Data Government Systems 303-967-7271office 719-649-9090 mobile Chris. Grobmeier [EMAIL PROTECTED] 07/13/2005 10:34 AM Please respond to Tomcat Users List tomcat-user@jakarta.apache.org To [EMAIL PROTECTED] cc Tomcat Users List tomcat-user@jakarta.apache.org Subject Re: JkUnMount is unknown to apache I think this is mod-webapp, and not mod-jk. Try to find libapache-mod-jk-[version] for Debian. I tried this and finally i did dpkg --list and searched manually. all i could get is this information again: libapache-mod-jk 3.3a-4woody1 Apache connector for Tomcat servlet engine Any other hints? Is there a file in which the current version is written? Thank you, Chris - 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: mod_jk configuration
One way to do this is to declare a host in your server.xml instance The server.xml will need to contain an entry within the engine like Host name=myotherdomain.tld appBase=webapps unpackWARs=true autoDeploy=true Logger className=org.apache.catalina.logger.FileLogger directory=logs prefix=YOUR_PREFIX. suffix=.txt timestamp=true/ !-- this takes all requests to myotherdomain.tld and associates them to the context , may need to play with this-- Context path= docBase=/path/to/your/appDir/or/war_file crossContext=false debug=10 reloadable=false trusted=false /Context !-- ** the deva application context ** -- /Host And in your httpd.conf virtual host ... servername myotherdomain.tld JkMount /* ajp13 -- My worker /virtual host ... This seems to work in our configuration to handle this type of operation. Have Fun... Colby C. Meyer [EMAIL PROTECTED] [EMAIL PROTECTED] 06/22/2005 01:31 AM Please respond to Tomcat Users List tomcat-user@jakarta.apache.org To Tomcat Users List tomcat-user@jakarta.apache.org cc Subject mod_jk configuration Hello all, i am using Tomcat 4.1.3x, mod_jk 1.x and Apache 1.3.x. I have read all the documentation available on apache.org, but i think i have not understood some principles of JK. Problem: I have java.domain.tld pointing to the root-directory of Tomcat. The default tomcat site appears. I guess my installations are ok. I want to have myotherdomain.tld pointing to a specific webapp. I have a worker (the same as the java.domain.tld Domain), but where must i declare which context is to use? In my vhosts i have: virtual host ... JkMount /* ajp13 -- My worker /virtual host ... In my workers.properties there is nothing about an context. Documentation told me nothin about tags to declare. Btw, i installed my app with the war-deploy feat. Maybe this is important. Any help is appreciated- thank you for reading. Regards Chris - 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]
Question on Configuring Virtual Hosts on different ports
We are attempting to configure tomcat with virtual hosts so that different ports represent different regions For example port 80 may represent a QA region port 90 may represent a dev region We are using apache as the front end for Tomcat in httpd.conf we have the following defined : # Definition for DEVA VirtualHost *:90 ServerAdmin [EMAIL PROTECTED] ServerName deva JkMount /* ajp13 ErrorLog /opt/bluepage/deva/logs/error_log CustomLog /opt/bluepage/deva/logs/access_log common /VirtualHost this should forward all requests to the Tomcat connector and hence to Tomcat in server.xml we have the following defined : Host name=deva appBase=webapps unpackWARs=true autoDeploy=true Logger className=org.apache.catalina.logger.FileLogger directory=logs prefix=deva_log. suffix=.txt timestamp=true/ Context path= docBase=/opt/tomcat/webapps/dva/BluePage.war crossContext=false debug=1 reloadable=false trusted=false /Context Context path=/BluePage docBase=/opt/tomcat/webapps/dva/BluePage.war crossContext=false debug=1 reloadable=false trusted=false /Context !-- ** the deva application context ** -- /Host and in /etc/hosts we have 127.0.0.1 localhost qaa qab qac deva devb devc 192.168.85.6qaa qab qac deva devb devc When we start tomcat and hit the URL : http://192.168.85.6:90/index.html we see some of the static html content that is defined in the root of the WAR file However when trying to access any of the servlets in the WAR , for example http://192.168.85.6:90/BluePage/Redirector?foo=usabar=caENTER.x=15ENTER.y=18 The following logs in the Apache access_log for this host - [08/Jun/2005:12:21:59 -0400] GET /BluePage/Redirector?foo=usabar=caENTER.x=15ENTER.y=18 HTTP/1.1 302 0 nothing logs in the associated tomcat log and the servlet doesn't appear to be getting called. The WAR was built on the same machine as the Tomcat Server so we are using the same java version and the structure of the WAR was initially built on Websphere, so I feel that the structure in terms of WEB-INF/classes and such is valid. We have exhaustively experimented with permutations of server settings, read everything on Virtual Host configuration and the proper course of action escapes us. I am thinking that this may be an issue with the application code itself, but I am not sure where to start looking. Does anyone have any thoughts or pointers they may be willing to share ? Thanks Colby C. Meyer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
