Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 62178 invoked from network); 8 Jan 2003 20:33:49 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 8 Jan 2003 20:33:49 -0000 Received: (qmail 23601 invoked by uid 97); 8 Jan 2003 20:34:45 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 23574 invoked by uid 97); 8 Jan 2003 20:34:44 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 23562 invoked by uid 98); 8 Jan 2003 20:34:43 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) X-pair-Authenticated: 141.151.168.20 Subject: RE: Apache2 and mod_jk From: Bill To: Tomcat Users List In-Reply-To: <83F0258A9996D311B14200A0C98F173602F22B9B@aas-internet.aas.com> References: <83F0258A9996D311B14200A0C98F173602F22B9B@aas-internet.aas.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 08 Jan 2003 15:30:01 +0000 Message-Id: <1042039801.2658.101.camel@bill.collaborativefusion.com> Mime-Version: 1.0 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N John > > What URL are you trying to access? http://192.168.1.250/mrccores/some.jsp? I've been testing using http://192.168.1.250/examples . That url gets a 500 error. I figured if I got the example app working the rest would fall into place... > What are the contents of the JK logs and the Catalina logs? There is absolutely nothing in the JK logs. I included an excerpt of the catalina.log file in the original message. Besides the normal startup and shutdown stuff there is the "unable to open config file" and then there is a ton of packet data that corresponds to the bad reads in the host_log file. > Those "unable to open config file" messages are very strange, as is "bad > read". How much editing have you done to the default configuration files? This bugs me too. Not so much the bad reads but the "unable to read..." What files in particular are you referring too? The only file I can really thing of that I did a ton of editing too is server.xml. You saw the changes I made to apache-tomcat and I removed the standalone config. > > > -----Original Message----- > > From: Bill [mailto:bhalpin@collaborativefusion.com] > > Sent: Wednesday, January 08, 2003 9:59 AM > > To: Tomcat Users List > > Subject: RE: Apache2 and mod_jk > > > > > > The port designation was a typo in the file. Thanks for > > catching that, > > however it doesnt seemed to have made a difference. > > > > > > Here are the contexts I have defined currently: > > > > > docBase="ROOT" > > debug="0"> > > > > > docBase="tomcat-docs" > > reloadable="true" > > debug="0"> > > > > > docBase="examples" > > reloadable="true" > > debug="0"> > > > > > docBase="mrccores" > > reloadable="true" > > debug="0" > > trusted="false"> > > > > These are all defined after the AccessLogValve definition and > > before the > > tag. > > > > Here is the contents of of mod_jk.conf (minus the !IfModule block) : > > > > > > ServerName 192.168.1.250 > > > > JkMount /examples ajp13 > > JkMount /examples/* ajp13 > > > > JkMount /webdav ajp13 > > JkMount /webdav/* ajp13 > > > > JkMount /tomcat-docs ajp13 > > JkMount /tomcat-docs/* ajp13 > > > > JkMount /manager ajp13 > > JkMount /manager/* ajp13 > > > > JkMount /mrccores ajp13 > > JkMount /mrccores/* ajp13 > > > > > > > > On Wed, 2003-01-08 at 19:35, Turner, John wrote: > > > > > > Yep. > > > > > > 1. For Apache 2, you don't need AddModule > > > > > > 2. Unless it's a typo, your workers.properties says the > > Ajp13Connector is on > > > 8009, yet your server.xml has it on 8008. > > > > > > 3. You don't have a Context element in server.xml, unless > > you left it out > > > when pasting. > > > > > > If 2 is a typo, and 8009 is used for both, all is good. If > > 3 is deliberate, > > > please post your Context entry and the contents of mod_jk.conf. > > > > > > John > > > > > > > -----Original Message----- > > > > From: Bill [mailto:bhalpin@collaborativefusion.com] > > > > Sent: Wednesday, January 08, 2003 9:24 AM > > > > To: tomcat user > > > > Subject: Apache2 and mod_jk > > > > > > > > > > > > I've been holding off on posting on my problem because there > > > > have been a > > > > wealth of posts on this topic. However, the > > advice/suggestions I have > > > > seen havent led me to a working system. > > > > > > > > I'm trying to setup Tomcat 4.0.6 and HTTPD Server 2.0 > > using mod_jk. > > > > I've followed instructions for this task from several sources and > > > > nothing seems to be working. > > > > > > > > Here are the steps I followed: > > > > > > > > 1) Added the following to httpd.conf: > > > > > > > > LoadModule jk_module modules/mod_jk.so > > > > > > > > This step also says to add the AddModule directive. This > > > > directive does > > > > not exist for 2.0 nor was I able to find an analogous directive to > > > > replace it. > > > > > > > > 2) I have the following in > > > > /usr/local/tomcat/conf/jk/workers.properties > > > > > > > > workers.list= ajp13 > > > > worker.ajp13.type=ajp13 > > > > > > > > worker.ajp13.host=192.168.1.250 > > > > worker.ajp13.port=8009 > > > > > > > > worker.ajp13.cachesize=10 > > > > worker.ajp13.cache_timeout=600 > > > > worker.ajp13.socket_keepalive=1 > > > > worker.ajp13.socket_timeout=300 > > > > > > > > > > > > 3) I have the following in httpd.conf: > > > > > > > > JkWorkersFile /usr/local/tomcat/conf/jk/workers.properties > > > > JkLogFile /usr/local/apache2/log/mod_jk.log > > > > JkLogLevel info > > > > JkLogStampFormat "[%a %b %d %H:%M:%S %Y] " > > > > JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories > > > > JkRequestLogFormat "%w %V %T" > > > > > > > > Include /usr/local/tomcat/conf/auto/mod_jk.conf > > > > > > > > 4) Here is my server.xml entry: > > > > > > > > > > > > > className="org.apache.ajp.tomcat4.config.ApacheConfig"/> > > > > > > > > > > > > > > > > > > > port="8008" minProcessors="5" maxProcessors="75" > > > > enableLookups="true" > > > > acceptCount="10" debug="0"/> > > > > > > > > > debug="0" > > > > appBase="webapps"> > > > > > > > > > > > prefix="apache_log." suffix=".txt" > > > > timestamp="true"/> > > > > > > > > > > > > > > > unpackWARs="true"> > > > > > > > > > > > append="true"/> > > > > > > > > > className="org.apache.catalina.valves.AccessLogValve" > > > > directory="logs" > > prefix="192.168.1.250_access_log." > > > > suffix=".txt" pattern="common"/> > > > > > > > > > > > > > > > > > > > > > > > > No errors show up in the access log but the following error > > > > shows up in > > > > the host log ($TOMCAT_HOME/logs/apache_log.2003-01-08.txt): > > > > > > > > 2003-01-08 13:07:57 Ajp13Processor[8008][4] [Ajp13] > > incomplete read, > > > > waited #-1 got only 0 > > > > > > > > And this is what I get in catalina.log: > > > > > > > > Unable to open config file > > > > Starting service Tomcat-Apache > > > > Apache Tomcat/4.0.6 > > > > Unable to open config file > > > > BAD packet 18245 > > > > In: : [B@45fde0 4/21540 > > > > 47 45 54 20 00 00 00 00 00 00 00 00 00 00 00 00 | > > GET............. > > > > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | > > ................ > > > > > > > > This goes on forever so I only included to the first few > > lines of the > > > > first packet... > > > > > > > > Any ideas what I missed? I did a web search on the error > > and got a > > > > couple of hits but none of them panned out. > > > > > > > > Thanks > > > > > > > > -b > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > To unsubscribe, e-mail: > > > > > > For additional commands, e-mail: > > > > > > > > > -- > > > To unsubscribe, e-mail: > > > For additional commands, e-mail: > > > > > > > -- > To unsubscribe, e-mail: > > For additional commands, e-mail: > > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: > -- To unsubscribe, e-mail: For additional commands, e-mail: