Same results.
Jerry
PELOQUIN,JEFFREY (HP-Boise,ex1) wrote:
Just for chuckles try it without putting quote around the file names
this is how I have it my http.conf
JkWorkersFile /opt_apps/hpapache2/conf/workers.properties
JkLogFile /opt_apps/hpapache2/logs/mod_jk.log
JkLogLevel info
if that does not work try moving the files local to the apache conf and log
directories
Jeff
-----Original Message-----
From: Jerry Ford [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 26, 2002 11:54 AM
To: Tomcat Users List
Subject: Re: mod_jk---still trying, getting closer
Yes. Same results.
PELOQUIN,JEFFREY (HP-Boise,ex1) wrote:
Your http.conf shows that apache is running as nobodyi
have you tried changing that so it runs as the owner of the apache and
tomcat directory structure?
-----Original Message-----
From: Jerry Ford [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 26, 2002 12:32 AM
To: Tomcat Users List
Subject: Re: mod_jk---still trying, getting closer
John:
Sorry, I had changed ajp13 to worker1 in trying to emulate Denise's working setup, but that didn't do any good so I changed it back and inadvertently put the dot in. But it doesn't matter, it doesn't work either way.
As noted in earlier e-mails, I can get the Tomcat example servlets to work, as well as my own j_tools HelloWorld, when I specify port 8080, but not through Apache:
http://localhost opens Apache's index page
http://localhost:8080 opens Tomcat's index page, and servlets work
http://localhost/examples/servlets opens the servlets index page, but servlets don't work
Catalina.out in Tomcat's logs directory says mod_jk is running:
Dec 25, 2002 8:50:51 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on port 8080
Starting service Tomcat-Standalone
Apache Tomcat/4.1.12-LE-jdk14
Dec 25, 2002 8:50:57 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on port 8080
Dec 25, 2002 8:50:57 PM org.apache.jk.common.ChannelSocket init
INFO: JK2: ajp13 listening on tcp port 8009
Dec 25, 2002 8:50:57 PM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=2/121 config=/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk2.propert
esi
Stopping service Tomcat-Standalone
Dec 25, 2002 11:26:13 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on port 8080
Starting service Tomcat-Standalone
Apache Tomcat/4.1.12-LE-jdk14
Dec 25, 2002 11:26:18 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on port 8080
Dec 25, 2002 11:26:18 PM org.apache.jk.common.ChannelSocket init
INFO: JK2: ajp13 listening on tcp port 8009
Dec 25, 2002 11:26:19 PM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=1/277 config=/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk2.propert
essysvsem)
But the Apache error log says Apache cannot open the workers file, even though the path specified is correct and permissions to the file are -rw-rw-r-- and to all directories drwxrwxr-x:
[Wed Dec 25 15:14:36 2002] [error] (2)No such file or directory: Error while opening the workers, jk will not work
[Wed Dec 25 15:14:36 2002] [error] (2)No such file or directory: Error while opening the workers, jk will not work
[Wed Dec 25 15:14:36 2002] [notice] Apache/1.3.27 (Unix) mod_jk/1.2.0 configured -- resuming normal operations
[Wed Dec 25 15:14:36 2002] [notice] Accept mutex: sysvsem (Default:
Jerrynotice
Turner, John wrote:
theWhoa, I have NEVER seen a worker called "ajp.13" before. I can't imagine that that would work at all, as "." is a separator in workers.properties. Is there a reason you are using that instead of "ajp13" or something else?Also, what exact URL are you trying to access? What URL is not working?From your httpd.conf, the only possible URL that would work, aside from
examples, the manager app, and the admin app, is:
http://localhost/j_tools/servlet/HelloWorld
and
http://localhost/j_tools/some.jsp
Are those what you are trying?
John
-----Original Message-----
From: Jerry Ford [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 25, 2002 6:22 PM
To: Tomcat Users List
Subject: Re: mod_jk---still trying, getting closer
Denise:
Other than path names, the major differences between your set up and mine is that you use SSL, and I don't, and you have a lot more modules loaded than I do (in addition to mod_jk). But I don't see those differences as having anything to do with why yours works and mine doesn't. For one thing, this installation of Apache is on my development workstation, and I just installed it to test the tomcat connection. So, it doesn't need to be a fully functional web server. At least, not yet.
Also, I removed the comments from my conf file so I can find things :)
I have tried it both ways---with an include statement pointing to mod_jk.conf in tomcat/conf/auto, and with statements inside httpd.conf. Same results.
I have also experimented with a variety of permissions on both files and directories.
My configuration files are attached.
Thanks.
Jerry
Denise Mangano wrote:
Jerry -
My config is now working with the files that I had posted. Did you
wouldButany major differences between those and yours?
I had also gotten this same Apache error message at one point as well.
it just sort of "went away" when I put the JkMount statements right into
httpd.conf and made a different workers.properties file than the one that
was posted on the HOW-TO. Here are the contents of my workers.properties
file. With this properties file I use worker1 instead of ajp13 in the
JkMount statements: (For example JkMount /examples/* worker1)
worker.list=worker1 worker.worker1.type=ajp13 worker.worker1.host=localhost
worker.worker1.port=8009
On a side note, my workers.properties has 644 permissions (-rw-r--r--).
Would you post your files and error logs? I am sure someone in here
ptake a look... I can also look just to see any major differences against
mine..
Denise
-----Original Message-----
From: Jerry Ford [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 24, 2002 4:31 PM
To: Tomcat Users List
Subject: Re: mod_jk---still trying, getting closer
Yes, good idea about the symbolic links. I have done now so---sym links for both apache and tomcat.
I have also moved all mod_jk configs into httpd.conf.
And I'm still getting the same results---catalina.out says Jk is okay, apache works, tomcat works (with servlets) but the apache error_log says "error while opening the workers, jk will not work." And sure enough, no servlets through Apache.
Jerry
Milt Epstein wrote:
On Tue, 24 Dec 2002, Jerry Ford wrote:
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.FWIW, you still might want to create a symbolic link tomcat (under
webserver) that points to jakarta-tomcat-4.1.12-LE-jdk14. This might not fix your problem here, but it could save you some hassle if/when you upgrade to new versions.
PELOQUIN,JEFFREY (HP-Boise,ex1) wrote:
Jerry,
The confusion as to the name arises from your printour of your directory structure
drwxrwxr-x...usr/there is no jakarta-tomcat-4.12.12-LE-jdk14 mentioned which implies there is a mismatch of names
drwxrwxr-x......local/
drwxrwxr-x.........webserver/
drwxrwxr-x............apache/
drwxrwxr-x............tomcat/ drwxrwxr-x...............conf/
drwxrwxr-x..................jk/
-rw-rw-r-x.....................workers.properties
-----Original Message-----
From: Jerry Ford [mailto:[EMAIL PROTECTED]]
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.
pr
o
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.
or
o
perties"
JKLogFile
"/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk/mod_jk.l
rg
"
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:[EMAIL PROTECTED]]
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.p
<mailto:[EMAIL PROTECTED]>o
<mailto:[EMAIL PROTECTED]>p
<mailto:[EMAIL PROTECTED]><mailto:[EMAIL PROTECTED]>erties<mailto:[EMAIL PROTECTED]>
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:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail:
For additional commands, e-mail:<mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>Milt Epstein
Research Programmer
Integration and Software Engineering (ISE)
Campus Information Technologies and Educational Services (CITES) University of Illinois at Urbana-Champaign (UIUC) [EMAIL PROTECTED]
--
To unsubscribe, e-mail:
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail:
For additional commands, e-mail:<mailto:[EMAIL PROTECTED]>
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.419 / Virus Database: 235 - Release Date: 11/13/2002
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.419 / Virus Database: 235 - Release Date: 11/13/2002
--
To unsubscribe, e-mail:
For additional commands, e-mail:<mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail:
For additional commands, e-mail:<mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
