tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jerry Ford <je...@katzenjammer.us>
Subject Re: mod_jk---still trying, getting closer
Date Tue, 24 Dec 2002 20:13:08 GMT
Ooops, sorry, I was using shorthand in showing the directory gtree; 
actual name of the directory is the full jakarta-tomcat-4.1.12-LE-jdk14; 
same for apache, it's acutally apache_1.3.27  (whew, guess I need to 
change those anyway, that's a lot of typing!!! :)  I just untarred them 
and kept the default names.

Jerry

PELOQUIN,JEFFREY (HP-Boise,ex1) wrote:

>Jerry,
>
>The confusion as to the name arises from your printour of your directory
>structure
>  
>
>>drwxrwxr-x...usr/
>>drwxrwxr-x......local/
>>drwxrwxr-x.........webserver/
>>drwxrwxr-x............apache/
>>drwxrwxr-x............tomcat/
>>drwxrwxr-x...............conf/
>>drwxrwxr-x..................jk/
>>-rw-rw-r-x.....................workers.properties
>>    
>>
>
>there is no jakarta-tomcat-4.12.12-LE-jdk14 mentioned which implies there is
>a mismatch of names
>
>
>
>-----Original Message-----
>From: Jerry Ford [mailto:jerry@katzenjammer.us]
>Sent: Tuesday, December 24, 2002 12:49 PM
>To: Tomcat Users List
>Subject: Re: mod_jk---still trying, getting closer
>
>
>Justin:
>
>My bad.  I didn't copy and paste, I retyped the JkLogFile reference.  In 
>the config, it correctly says mod_jk.log.
>
>I don't understand what would be accomplished by changing 
>"jakarta-tomcat-4.12.12-LE-jdk14" to simply "tomcat".  The name of the 
>directory is the full name, as it was created when I untarred Tomcat. 
> If I change the reference in the configs to "tomcat" and change the 
>name of the directory to "tomcat" how is that any different?
>
>As for auto-conf, you are right.  I think I will do as you suggest and 
>move everything into httpd.
>
>Jerry
>
>Justin L. Spies wrote:
>
>  
>
>>Jerry,
>>I've never used the auto/mod_jk stuff, so I can't comment on that.  What
>>is weird to me though, is the line that reads:
>>JkLogFile
>>"/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk/workers.pro
>>perties"
>>
>>That leads me to believe that mod_jk is configured to overwrite the
>>workers.properties file with the mod_jk log.  I would have expected to
>>see the lines:
>>JkWorkersFile
>>"/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk/workers.pro
>>perties"
>>JKLogFile
>>"/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk/mod_jk.log"
>>
>>Changing those as suggested by Jeffrey (I agree with him on these
>>changes), they would like this:
>>JkWorkersFile
>>"/usr/local/webserver/apache/tomcat/conf/jk/workers.properties"
>>JKLogFile "/usr/local/webserver/apache/tomcat/conf/jk/mod_jk.log"
>>
>>If I were in your shoes, I think that I would try to get mod_jk working
>>without the auto configuration.  Once I had that working, I would then
>>focus on the autoconfig.  I don't know about you, but in my experience,
>>when I try to get everything working in the first run, I usually miss
>>something and have to take a step back and start with the basics.
>>That's just me though.
>>
>>Sincerely,
>>Pantek Incorporated
>>Justin L. Spies
>>
>>URI: http://www.pantek.com
>>Ph   440.519.1802
>>Fax  440.248.5274
>>Cell 440.336.3317
>>
>>
>>
>>-----Original Message-----
>>From: Jerry Ford [mailto:jford@katzenjammer.us] 
>>Sent: Tuesday, December 24, 2002 12:42 PM
>>To: tomcat-user
>>Subject: mod_jk---still trying, getting closer
>>
>>
>>Thanks to some examples of working configs provided by  several people 
>>here, I am making progress in getting Apache 1.3.27 and Tomcat 4.1.12 to
>>
>>work together through mod_jk, but it still isn't working yet.
>>
>>Tomcat and Apache run fine independently:
>>
>>http://localhost opens Apache's index.html http://localhost:8080 opens
>>Tomcat's index and servlet examples work fine.
>>http://localhost/examples/servlets opens the servlets index, but 
>>servlets themselves don't work (generate an Apache port 80 Internal 
>>Server error)
>>
>>I see in the catalina.out logfile that Tomcat is now able to start Jk 
>>(this is new for me---one key element was specifying an absolute path to
>>
>>mod_jk.so):
>>
>>Starting service Tomcat-Standalone
>>Apache Tomcat/4.1.12-LE-jdk14
>>Dec 24, 2002 9:13:48 AM org.apache.coyote.http11.Http11Protocol start
>>INFO: Starting Coyote HTTP/1.1 on port 8080
>>Dec 24, 2002 9:13:48 AM org.apache.jk.common.ChannelSocket init
>>INFO: JK2: ajp13 listening on tcp port 8009
>>Dec 24, 2002 9:13:48 AM org.apache.jk.server.JkMain start
>>INFO: Jk running ID=0 time=2/179  
>>config=/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk2.prop
>>erties
>>
>>But the Apache error_log says Apache can't open the workers.properties
>>file:
>>
>>[Tue Dec 24 09:13:59 2002] [error] (2)No such file or directory: Error 
>>while opening the workers, jk will not work
>>
>>[Tue Dec 24 09:13:59 2002] [error] (2)No such file or directory: Error 
>>while opening the workers, jk will not work
>>
>>[Tue Dec 24 09:13:59 2002] [notice] Apache/1.3.27 (Unix) mod_jk/1.2.0 
>>configured -- resuming normal operations
>>[Tue Dec 24 09:13:59 2002] [notice] Accept mutex: sysvsem (Default:
>>sysvsem)
>>
>>Worker file is identified as follows, in the auto/mod_jk.conf file:
>>
>>JkLogFile 
>>"/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk/workers.pro
>>perties"
>>
>>I know some have recommended that the contents of mod_jk.conf be 
>>hardwired into httpd.conf, but auto/mod_jk.conf seems to be working fine
>>
>>in every other respect, so I am inclined to continue using it.  
>>Still, I did put the log file directive in httpd.conf just to see of it 
>>would make a difference.  It did not.
>>
>>The directory tree is set up as follows:
>>
>>drwxrwxr-x...usr/
>>drwxrwxr-x......local/
>>drwxrwxr-x.........webserver/
>>drwxrwxr-x............apache/
>>drwxrwxr-x............tomcat/
>>drwxrwxr-x...............conf/
>>drwxrwxr-x..................jk/
>>-rw-rw-r-x.....................workers.properties
>>
>>Ownership of the apache tree was changed from root:root to jford:jford; 
>>so I changed it back to root:root and tried it, and I still get the 
>>errors (so I changed it back to jford:jford).
>>
>>Any suggestions?
>>
>>Thanks.
>>
>>Jerry
>>
>>
>>--
>>To unsubscribe, e-mail:
>><mailto:tomcat-user-unsubscribe@jakarta.apache.org>
>>For additional commands, e-mail:
>><mailto:tomcat-user-help@jakarta.apache.org>
>>
>>
>>
>>--
>>To unsubscribe, e-mail:
>>    
>>
><mailto:tomcat-user-unsubscribe@jakarta.apache.org>
>  
>
>>For additional commands, e-mail:
>>    
>>
><mailto:tomcat-user-help@jakarta.apache.org>
>  
>
>> 
>>
>>    
>>
>
>
>--
>To unsubscribe, e-mail:
><mailto:tomcat-user-unsubscribe@jakarta.apache.org>
>For additional commands, e-mail:
><mailto:tomcat-user-help@jakarta.apache.org>
>
>--
>To unsubscribe, e-mail:   <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
>For additional commands, e-mail: <mailto:tomcat-user-help@jakarta.apache.org>
>  
>


--
To unsubscribe, e-mail:   <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-user-help@jakarta.apache.org>


Mime
View raw message