RE: mod_jk---still trying, getting closer

[PELOQUIN,JEFFREY (HP-Boise,ex1)]

Jerry,

given the directory structure you provide you might try chaging these

"/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk/workers.propert
ies"
config=/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk2.properti
es


to

"/usr/local/webserver/tomcat/conf/jk/workers.properties"
config=/usr/local/webserver/tomcat/conf/jk2.properties



Not sure where those are set in the server.xml as I hard code my http.conf
Jeff

-Original Message-
From: Jerry Ford [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 24, 2002 10:42 AM
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.properti
es

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.propert
ies"

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-xapache/
drwxrwxr-xtomcat/
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:

For additional commands, e-mail:


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: mod_jk---still trying, getting closer

[Justin L. Spies]

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:[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.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-xapache/
drwxrwxr-xtomcat/
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:

For additional commands, e-mail:




--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: mod_jk---still trying, getting closer

[Jerry Ford]

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:[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.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-xapache/
drwxrwxr-xtomcat/
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:

For additional commands, e-mail:




--
To unsubscribe, e-mail:   
For additional commands, e-mail: 
 



--
To unsubscribe, e-mail:   

RE: mod_jk---still trying, getting closer

[PELOQUIN,JEFFREY (HP-Boise,ex1)]

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-xapache/
>drwxrwxr-xtomcat/
>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:[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.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:[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.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/we

Re: mod_jk---still trying, getting closer

[Jerry Ford]

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-xapache/
drwxrwxr-xtomcat/
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:[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.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:[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.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-L

Re: mod_jk---still trying, getting closer

[Milt Epstein]

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/
> >>drwxrwxr-x..local/
> >>drwxrwxr-x.webserver/
> >>drwxrwxr-xapache/
> >>drwxrwxr-xtomcat/
> >>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:[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.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:[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.htm

Re: mod_jk---still trying, getting closer

[Jerry Ford]

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/
drwxrwxr-x..local/
drwxrwxr-x.webserver/
drwxrwxr-xapache/
drwxrwxr-xtomcat/
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:[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.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:[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

RE: mod_jk---still trying, getting closer

[Denise Mangano]

Jerry -

My config is now working with the files that I had posted.  Did you notice
any major differences between those and yours? 

I had also gotten this same Apache error message at one point as well.  But
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 would
take 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/
>>>>drwxrwxr-x..local/
>>>>drwxrwxr-x.webserver/
>>>>drwxrwxr-xapache/
>>>>drwxrwxr-xtomcat/ 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:[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.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.pr

Re: mod_jk---still trying, getting closer

[Jerry Ford]

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 notice
any major differences between those and yours? 

I had also gotten this same Apache error message at one point as well.  But
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 would
take 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/
drwxrwxr-x..local/
drwxrwxr-x.webserver/
drwxrwxr-xapache/
drwxrwxr-xtomcat/ 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:[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.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"
JKLogFil

RE: mod_jk---still trying, getting closer

[Turner, John]

Easiest thing to do, in my opinion, is setup symlinks.  Makes version
changing very easy.  For example, Tomcat may be in
/usr/local/Jakarta-tomcat-4.1.12.  I would setup a symlink that linked
/usr/local/tomcat to that directory, then I would use /usr/local/tomcat in
all of my start/stop scripts, etc.  That way, changing to 4.1.18 is a simple
change of the symbolic link, not of anything else, and if you have to fall
back to a known-good installation, you just change the symlink back.

Ditto Apache.  Apache might be in /usr/local/apache-2.0.43, but on my boxes
/usr/local/apache is a symlink to that directory.  Also makes testing and
moving between 1.3.27 and 2.0.x a piece of cake.

John


-Original Message-
From: Jerry Ford [mailto:[EMAIL PROTECTED]] 
Sent: Tuesday, December 24, 2002 3:13 PM
To: Tomcat Users List
Subject: Re: mod_jk---still trying, getting closer

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-xapache/
>>drwxrwxr-xtomcat/
>>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:[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.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:[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 indep

RE: mod_jk---still trying, getting closer

[Turner, John]

Whoa, 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 the
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 notice
>any major differences between those and yours? 
>
>I had also gotten this same Apache error message at one point as well.  But
>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 would
>take 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/
>>>>>drwxrwxr-x..local/
>>>>>drwxrwxr-x.webserver/
>>>>>drwxrwxr-xapache/
>>>>>drwxrwxr-xtomcat/ drwxrwxr-x...conf/
>>>

Re: mod_jk---still trying, getting closer

[Jerry Ford]

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.properties
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.properties

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: sysvsem)

Jerry


Turner, John wrote:

Whoa, 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 the

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 notice
any major differences between those and yours? 

I had also gotten this same Apache error message at one point as well.  But
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

RE: mod_jk---still trying, getting closer

[PELOQUIN,JEFFREY (HP-Boise,ex1)]

Your http.conf shows that apache is running as nobody
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.properti
es
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.properti
es

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: sysvsem)

Jerry


Turner, John wrote:

>Whoa, 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
the
>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 notice
>>any major differences between those an

Re: mod_jk---still trying, getting closer

[Milt Epstein]

On Wed, 25 Dec 2002, Jerry Ford wrote:

> 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.

One things I don't understand, it seems like you have JK2 running on
the Tomcat side, but you refer to workers.properties, which is a JK
file, JK2 doesn't use it, I don't believe.  Could that be related to
the problem?


> 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.properties
> 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.properties
>
> 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: sysvsem)
[ ... ]

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: 

Re: mod_jk---still trying, getting closer

[Jerry Ford]

Yes.  Same results.

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


Your http.conf shows that apache is running as nobody
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.properti
es
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.properti
es

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: sysvsem)

Jerry


Turner, John wrote:

 

Whoa, 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

   

the
 

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 notice
any major differences between those and yours? 

I had also gotten this same Apache error message at one point as well.
 

But
 

it just sort of "went away" when I put the JkMount statements right into
httpd.conf and made a 

Re: mod_jk---still trying, getting closer

[Jerry Ford]

I use the mod_jk binary obtained from John Turner's how-to page, and the 
httpd.conf and server.xml statements are the same as the statements in 
the configurations several other people here have provided as examples, 
I think.  I have also tried to follow John Turner's suggested 
confuguration statements.  

I've tried just about every combination of configurations that have been 
suggested. It's possible that by now I have mixed up different people's 
advice, but I don't know what needs to be changed.  

I don't know why JK2 is in there, other than the coyote packages that 
are referenced in sever.xml.  But if I don't use those, what do I use?

I'm beginning to think mod_webapp.so is looking like my only hope of 
getting Tomcat and Apache to work together.

Jerry

Jerry

Milt Epstein wrote:

On Wed, 25 Dec 2002, Jerry Ford wrote:

 

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.
   


One things I don't understand, it seems like you have JK2 running on
the Tomcat side, but you refer to workers.properties, which is a JK
file, JK2 doesn't use it, I don't believe.  Could that be related to
the problem?


 

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.properties
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.properties

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: sysvsem)
   

[ ... ]

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: 
 



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: mod_jk---still trying, getting closer

[PELOQUIN,JEFFREY (HP-Boise,ex1)]

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 nobody
>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
i
>es
>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
i
>es
>
>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:
sysvsem)
>
>Jerry
>
>
>Turner, John wrote:
>
>  
>
>>Whoa, 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
>>
>>
>the
>  
>
>>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

RE: mod_jk---still trying, getting closer

[Justin L. Spies]

Jerry,
Just to clarify, are you using the mod_jk.so or mod_jk2.so?

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: Thursday, December 26, 2002 2:00 PM
To: Tomcat Users List
Subject: Re: mod_jk---still trying, getting closer


I use the mod_jk binary obtained from John Turner's how-to page, and the

httpd.conf and server.xml statements are the same as the statements in 
the configurations several other people here have provided as examples, 
I think.  I have also tried to follow John Turner's suggested 
confuguration statements.  

I've tried just about every combination of configurations that have been

suggested. It's possible that by now I have mixed up different people's 
advice, but I don't know what needs to be changed.  

I don't know why JK2 is in there, other than the coyote packages that 
are referenced in sever.xml.  But if I don't use those, what do I use?

I'm beginning to think mod_webapp.so is looking like my only hope of 
getting Tomcat and Apache to work together.

Jerry

Jerry

Milt Epstein wrote:

>On Wed, 25 Dec 2002, Jerry Ford wrote:
>
>  
>
>>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.
>>
>>
>
>One things I don't understand, it seems like you have JK2 running on 
>the Tomcat side, but you refer to workers.properties, which is a JK 
>file, JK2 doesn't use it, I don't believe.  Could that be related to 
>the problem?
>
>
>  
>
>>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.pr
>>operties
>>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.pr
operties
>>
>>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: sysvsem)
>>
>>
>[ ... ]
>
>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:
<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]>

RE: mod_jk---still trying, getting closer

[Justin L. Spies]

Jerry,
I've updated and simplified the configuration files that you supplied
previously.  Any changes I made are denoted by the following:
  NOTE NOTE NOTE NOTE

These changes cause your system to have the same config that I first
used to get my system working.  I'm not sure about your directory
structure and whether or not you have symlinks setup, however I did
notice that in some of the configuration files you were using two
different directories that should point to the same directories.  Here
is an example from httpd.conf:

You had the following for the JkWorkersFile:
JkWorkersFile
"/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk/workers.pro
perties"

But just below that you had the following apache directive:


These should be the same directory above the /conf directory and above
the /webapps directory.  On my system, I have tomcat installed in
/var/tomcat4, so I have the following directives:

JkWorkersFile "/var/tomcat4/conf/jk/workers.properties"
  --  and  --



See how they are the same first two?  /conf and /webapps should be a
subdirectory of /tomcat4 (in my case) or /tomcat (in your case), unless
you have a symlink (in your case) from
/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14 to
/usr/local/webserver/tomcat.  Does that make sense, or did I just
completely confuse everyone?

Jerry, when you restart Apache and Tomcat, could you send us copies of
the apache error log and the tomcat catalina.out files?  Also, if you
could confirm the directory structure, that would be a big help.

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: Thursday, December 26, 2002 2:00 PM
To: Tomcat Users List
Subject: Re: mod_jk---still trying, getting closer


I use the mod_jk binary obtained from John Turner's how-to page, and the

httpd.conf and server.xml statements are the same as the statements in 
the configurations several other people here have provided as examples, 
I think.  I have also tried to follow John Turner's suggested 
confuguration statements.  

I've tried just about every combination of configurations that have been

suggested. It's possible that by now I have mixed up different people's 
advice, but I don't know what needs to be changed.  

I don't know why JK2 is in there, other than the coyote packages that 
are referenced in sever.xml.  But if I don't use those, what do I use?

I'm beginning to think mod_webapp.so is looking like my only hope of 
getting Tomcat and Apache to work together.

Jerry

Jerry

Milt Epstein wrote:

>On Wed, 25 Dec 2002, Jerry Ford wrote:
>
>  
>
>>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.
>>
>>
>
>One things I don't understand, it seems like you have JK2 running on 
>the Tomcat side, but you refer to workers.properties, which is a JK 
>file, JK2 doesn't use it, I don't believe.  Could that be related to 
>the problem?
>
>
>  
>
>>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.pr
>>operties
>>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

RE: mod_jk---still trying, getting closer

[Justin L. Spies]

Jerry,
Once upon a time, I think you asked where I got the mod_jk binaries
from.  Here is the link:

RPM's:
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1
.2.2/rpms/
(Because I am running Apache 1.3, I grabbed version 1.3 in the file
mod_jk-ap13-1.2.2-1jpp.i386.rpm)

Binaries:
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1
.2.2/bin/linux/i386/
If you are running Apache compiled with SSL support (even if SSL is
disabled), you will need the file:
mod_jk-1.3.eapi.so

If you are running Apache compiled without SSL support (i.e., not using
RedHat RPMS), you will need the file:
mod_jk-1.3-noeapi.so

Again, both of those files are for Apache 1.3 only.

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: Thursday, December 26, 2002 2:00 PM
To: Tomcat Users List
Subject: Re: mod_jk---still trying, getting closer


I use the mod_jk binary obtained from John Turner's how-to page, and the

httpd.conf and server.xml statements are the same as the statements in 
the configurations several other people here have provided as examples, 
I think.  I have also tried to follow John Turner's suggested 
confuguration statements.  

I've tried just about every combination of configurations that have been

suggested. It's possible that by now I have mixed up different people's 
advice, but I don't know what needs to be changed.  

I don't know why JK2 is in there, other than the coyote packages that 
are referenced in sever.xml.  But if I don't use those, what do I use?

I'm beginning to think mod_webapp.so is looking like my only hope of 
getting Tomcat and Apache to work together.

Jerry

Jerry

Milt Epstein wrote:

>On Wed, 25 Dec 2002, Jerry Ford wrote:
>
>  
>
>>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.
>>
>>
>
>One things I don't understand, it seems like you have JK2 running on 
>the Tomcat side, but you refer to workers.properties, which is a JK 
>file, JK2 doesn't use it, I don't believe.  Could that be related to 
>the problem?
>
>
>  
>
>>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.pr
>>operties
>>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.pr
operties
>>
>>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
>>
>&

Re: mod_jk---still trying, getting closer

[Jerry Ford]

Have tried it both ways; added quotes because it wasn't working without 
them and I wanted to see what would happen.

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 nobody
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
   

i
 

es
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
   

i
 

es

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:
   

sysvsem)
 

Jerry


Turner, John wrote:



   

Whoa, 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

  

 

the


   

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. 

Re: mod_jk---still trying, getting closer

[Jerry Ford]

mod_jk.so

Justin L. Spies wrote:


Jerry,
Just to clarify, are you using the mod_jk.so or mod_jk2.so?

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: Thursday, December 26, 2002 2:00 PM
To: Tomcat Users List
Subject: Re: mod_jk---still trying, getting closer


I use the mod_jk binary obtained from John Turner's how-to page, and the

httpd.conf and server.xml statements are the same as the statements in 
the configurations several other people here have provided as examples, 
I think.  I have also tried to follow John Turner's suggested 
confuguration statements.  

I've tried just about every combination of configurations that have been

suggested. It's possible that by now I have mixed up different people's 
advice, but I don't know what needs to be changed.  

I don't know why JK2 is in there, other than the coyote packages that 
are referenced in sever.xml.  But if I don't use those, what do I use?

I'm beginning to think mod_webapp.so is looking like my only hope of 
getting Tomcat and Apache to work together.

Jerry

Jerry

Milt Epstein wrote:

 

On Wed, 25 Dec 2002, Jerry Ford wrote:



   

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.
  

 

One things I don't understand, it seems like you have JK2 running on 
the Tomcat side, but you refer to workers.properties, which is a JK 
file, JK2 doesn't use it, I don't believe.  Could that be related to 
the problem?




   

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.pr
operties
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.pr
 

operties
 

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: sysvsem)
  

 

[ ... ]

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:
   

<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]>

Yes!!! It works!!! (was: Re: mod_jk---still trying, getting closer)

[Jerry Ford]

Justin, I owe you a beer...

I removed the two listener statements that you commented out in my  
server.xml file and now servlets work from Apache without a port setting.  

Thank you thank you thank you.  

(And thanks to everyone else who put up with my whining over the past 
few days and offered help---especially Denise, John, and Jeff :)

(BTW, it's academic now, but, yes, on my box tomcat is a symbolic link 
to jakarta-tomcat-4.1.12-LE-jdk14.)

Jerry

Justin L. Spies wrote:

Jerry,
I've updated and simplified the configuration files that you supplied
previously.  Any changes I made are denoted by the following:
 NOTE NOTE NOTE NOTE

These changes cause your system to have the same config that I first
used to get my system working.  I'm not sure about your directory
structure and whether or not you have symlinks setup, however I did
notice that in some of the configuration files you were using two
different directories that should point to the same directories.  Here
is an example from httpd.conf:

You had the following for the JkWorkersFile:
JkWorkersFile
"/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk/workers.pro
perties"

But just below that you had the following apache directive:
   

These should be the same directory above the /conf directory and above
the /webapps directory.  On my system, I have tomcat installed in
/var/tomcat4, so I have the following directives:

JkWorkersFile "/var/tomcat4/conf/jk/workers.properties"
 --  and  --
   


See how they are the same first two?  /conf and /webapps should be a
subdirectory of /tomcat4 (in my case) or /tomcat (in your case), unless
you have a symlink (in your case) from
/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14 to
/usr/local/webserver/tomcat.  Does that make sense, or did I just
completely confuse everyone?

Jerry, when you restart Apache and Tomcat, could you send us copies of
the apache error log and the tomcat catalina.out files?  Also, if you
could confirm the directory structure, that would be a big help.

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: Thursday, December 26, 2002 2:00 PM
To: Tomcat Users List
Subject: Re: mod_jk---still trying, getting closer


I use the mod_jk binary obtained from John Turner's how-to page, and the

httpd.conf and server.xml statements are the same as the statements in 
the configurations several other people here have provided as examples, 
I think.  I have also tried to follow John Turner's suggested 
confuguration statements.  

I've tried just about every combination of configurations that have been

suggested. It's possible that by now I have mixed up different people's 
advice, but I don't know what needs to be changed.  

I don't know why JK2 is in there, other than the coyote packages that 
are referenced in sever.xml.  But if I don't use those, what do I use?

I'm beginning to think mod_webapp.so is looking like my only hope of 
getting Tomcat and Apache to work together.

Jerry

Jerry

Milt Epstein wrote:

 

On Wed, 25 Dec 2002, Jerry Ford wrote:



   

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.
  

 

One things I don't understand, it seems like you have JK2 running on 
the Tomcat side, but you refer to workers.properties, which is a JK 
file, JK2 doesn't use it, I don't believe.  Could that be related to 
the problem?




   

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.pr
operties
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
Start

RE: Yes!!! It works!!! (was: Re: mod_jk---still trying, getting closer)

[Denise Mangano]

Congrats!! You sound as excited as I was when my setup finally started to
work :)

I do find it strange though how my config works with the Listener directives
uncommented, and yours did not...  

Denise Mangano
Help Desk Analyst
Complus Data Innovations, Inc.


-Original Message-
From: Jerry Ford [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, December 26, 2002 5:31 PM
To: [EMAIL PROTECTED]
Cc: 'Tomcat Users List'; [EMAIL PROTECTED]
Subject: Yes!!! It works!!! (was: Re: mod_jk---still trying, getting closer)


Justin, I owe you a beer...

I removed the two listener statements that you commented out in my  
server.xml file and now servlets work from Apache without a port setting.  

Thank you thank you thank you.  

(And thanks to everyone else who put up with my whining over the past 
few days and offered help---especially Denise, John, and Jeff :)

(BTW, it's academic now, but, yes, on my box tomcat is a symbolic link 
to jakarta-tomcat-4.1.12-LE-jdk14.)

Jerry

Justin L. Spies wrote:

>Jerry,
>I've updated and simplified the configuration files that you supplied 
>previously.  Any changes I made are denoted by the following:
>  NOTE NOTE NOTE NOTE
>
>These changes cause your system to have the same config that I first 
>used to get my system working.  I'm not sure about your directory 
>structure and whether or not you have symlinks setup, however I did 
>notice that in some of the configuration files you were using two 
>different directories that should point to the same directories.  Here 
>is an example from httpd.conf:
>
>You had the following for the JkWorkersFile:
>JkWorkersFile 
>"/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk/workers.pr
>o
>perties"
>
>But just below that you had the following apache directive:
>
>
>These should be the same directory above the /conf directory and above 
>the /webapps directory.  On my system, I have tomcat installed in 
>/var/tomcat4, so I have the following directives:
>
>JkWorkersFile "/var/tomcat4/conf/jk/workers.properties"
>  --  and  --
>
>
>
>See how they are the same first two?  /conf and /webapps should be a 
>subdirectory of /tomcat4 (in my case) or /tomcat (in your case), unless 
>you have a symlink (in your case) from 
>/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14 to 
>/usr/local/webserver/tomcat.  Does that make sense, or did I just 
>completely confuse everyone?
>
>Jerry, when you restart Apache and Tomcat, could you send us copies of 
>the apache error log and the tomcat catalina.out files?  Also, if you 
>could confirm the directory structure, that would be a big help.
>
>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: Thursday, December 26, 2002 2:00 PM
>To: Tomcat Users List
>Subject: Re: mod_jk---still trying, getting closer
>
>
>I use the mod_jk binary obtained from John Turner's how-to page, and 
>the
>
>httpd.conf and server.xml statements are the same as the statements in
>the configurations several other people here have provided as examples, 
>I think.  I have also tried to follow John Turner's suggested 
>confuguration statements.  
>
>I've tried just about every combination of configurations that have 
>been
>
>suggested. It's possible that by now I have mixed up different people's
>advice, but I don't know what needs to be changed.  
>
>I don't know why JK2 is in there, other than the coyote packages that
>are referenced in sever.xml.  But if I don't use those, what do I use?
>
>I'm beginning to think mod_webapp.so is looking like my only hope of
>getting Tomcat and Apache to work together.
>
>Jerry
>
>Jerry
>
>Milt Epstein wrote:
>
>  
>
>>On Wed, 25 Dec 2002, Jerry Ford wrote:
>>
>> 
>>
>>
>>
>>>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.
>>>   
>>>
>>>  
>>>
>>One things I don't understand, it seems like you have JK2 running on
>>the Tomcat side, but you refer to workers.properties, which is a JK 
>>file, JK2 doesn't use it, I don't believe.  Could that be related to 
>>the problem?
>>
>>
>> 
>>
>>
>>
>>>As noted in earlier e-mails, I can get 

RE: Yes!!! It works!!! (was: Re: mod_jk---still trying, getting closer)

[Justin L. Spies]

This was a message I thought I had sent to the list, but I somehow
managed to send it to Jerry directly...



Congratulations Jerry!  Glad to hear that you've got a working system
now!

Just for the benefit of the other list members out there, the pieces we
commented out were the following:
  
  

  ---   AND   ---




Has anyone else out there had good experience setting up the Apache auto
configuration?


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: Thursday, December 26, 2002 5:31 PM
To: Justin L. Spies
Cc: 'Tomcat Users List'; [EMAIL PROTECTED]
Subject: Yes!!! It works!!! (was: Re: mod_jk---still trying, getting
closer)


Justin, I owe you a beer...

I removed the two listener statements that you commented out in my  
server.xml file and now servlets work from Apache without a port
setting.  

Thank you thank you thank you.  

(And thanks to everyone else who put up with my whining over the past 
few days and offered help---especially Denise, John, and Jeff :)

(BTW, it's academic now, but, yes, on my box tomcat is a symbolic link 
to jakarta-tomcat-4.1.12-LE-jdk14.)

Jerry

Justin L. Spies wrote:

>Jerry,
>I've updated and simplified the configuration files that you supplied 
>previously.  Any changes I made are denoted by the following:
>  NOTE NOTE NOTE NOTE
>
>These changes cause your system to have the same config that I first 
>used to get my system working.  I'm not sure about your directory 
>structure and whether or not you have symlinks setup, however I did 
>notice that in some of the configuration files you were using two 
>different directories that should point to the same directories.  Here 
>is an example from httpd.conf:
>
>You had the following for the JkWorkersFile:
>JkWorkersFile 
>"/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk/workers.pr
>o
>perties"
>
>But just below that you had the following apache directive:
>
>
>These should be the same directory above the /conf directory and above 
>the /webapps directory.  On my system, I have tomcat installed in 
>/var/tomcat4, so I have the following directives:
>
>JkWorkersFile "/var/tomcat4/conf/jk/workers.properties"
>  --  and  --
>
>
>
>See how they are the same first two?  /conf and /webapps should be a 
>subdirectory of /tomcat4 (in my case) or /tomcat (in your case), unless

>you have a symlink (in your case) from 
>/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14 to 
>/usr/local/webserver/tomcat.  Does that make sense, or did I just 
>completely confuse everyone?
>
>Jerry, when you restart Apache and Tomcat, could you send us copies of 
>the apache error log and the tomcat catalina.out files?  Also, if you 
>could confirm the directory structure, that would be a big help.
>
>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: Thursday, December 26, 2002 2:00 PM
>To: Tomcat Users List
>Subject: Re: mod_jk---still trying, getting closer
>
>
>I use the mod_jk binary obtained from John Turner's how-to page, and 
>the
>
>httpd.conf and server.xml statements are the same as the statements in
>the configurations several other people here have provided as examples,

>I think.  I have also tried to follow John Turner's suggested 
>confuguration statements.  
>
>I've tried just about every combination of configurations that have 
>been
>
>suggested. It's possible that by now I have mixed up different people's
>advice, but I don't know what needs to be changed.  
>
>I don't know why JK2 is in there, other than the coyote packages that
>are referenced in sever.xml.  But if I don't use those, what do I use?
>
>I'm beginning to think mod_webapp.so is looking like my only hope of
>getting Tomcat and Apache to work together.
>
>Jerry
>
>Jerry
>
>Milt Epstein wrote:
>
>  
>
>>On Wed, 25 Dec 2002, Jerry Ford wrote:
>>
>> 
>>
>>
>>
>>>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.
>>>   
>>>
>>>  
>>>
>>One things I don't understand, it seems like you have JK2 run

RE: Yes!!! It works!!! (was: Re: mod_jk---still trying, getting closer)

[Denise Mangano]

Justin - 

Any thoughts on why that did the trick?  As I mentioned, those directives
are not commented out on my config, but it works?? Just curious is all...

Thanks!

Denise 


-Original Message-
From: Justin L. Spies [mailto:[EMAIL PROTECTED]] 
Sent: Friday, December 27, 2002 10:01 AM
To: 'Tomcat Users List'
Subject: RE: Yes!!! It works!!! (was: Re: mod_jk---still trying, getting
closer)


This was a message I thought I had sent to the list, but I somehow managed
to send it to Jerry directly...



Congratulations Jerry!  Glad to hear that you've got a working system now!

Just for the benefit of the other list members out there, the pieces we
commented out were the following:
  
  

  ---   AND   ---




Has anyone else out there had good experience setting up the Apache auto
configuration?


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: Thursday, December 26, 2002 5:31 PM
To: Justin L. Spies
Cc: 'Tomcat Users List'; [EMAIL PROTECTED]
Subject: Yes!!! It works!!! (was: Re: mod_jk---still trying, getting
closer)


Justin, I owe you a beer...

I removed the two listener statements that you commented out in my  
server.xml file and now servlets work from Apache without a port setting.  

Thank you thank you thank you.  

(And thanks to everyone else who put up with my whining over the past 
few days and offered help---especially Denise, John, and Jeff :)

(BTW, it's academic now, but, yes, on my box tomcat is a symbolic link 
to jakarta-tomcat-4.1.12-LE-jdk14.)

Jerry

Justin L. Spies wrote:

>Jerry,
>I've updated and simplified the configuration files that you supplied
>previously.  Any changes I made are denoted by the following:
>  NOTE NOTE NOTE NOTE
>
>These changes cause your system to have the same config that I first
>used to get my system working.  I'm not sure about your directory 
>structure and whether or not you have symlinks setup, however I did 
>notice that in some of the configuration files you were using two 
>different directories that should point to the same directories.  Here 
>is an example from httpd.conf:
>
>You had the following for the JkWorkersFile:
>JkWorkersFile
>"/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk/workers.pr
>o
>perties"
>
>But just below that you had the following apache directive:
>
>
>These should be the same directory above the /conf directory and above
>the /webapps directory.  On my system, I have tomcat installed in 
>/var/tomcat4, so I have the following directives:
>
>JkWorkersFile "/var/tomcat4/conf/jk/workers.properties"
>  --  and  --
>
>
>
>See how they are the same first two?  /conf and /webapps should be a
>subdirectory of /tomcat4 (in my case) or /tomcat (in your case), unless

>you have a symlink (in your case) from
>/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14 to 
>/usr/local/webserver/tomcat.  Does that make sense, or did I just 
>completely confuse everyone?
>
>Jerry, when you restart Apache and Tomcat, could you send us copies of
>the apache error log and the tomcat catalina.out files?  Also, if you 
>could confirm the directory structure, that would be a big help.
>
>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: Thursday, December 26, 2002 2:00 PM
>To: Tomcat Users List
>Subject: Re: mod_jk---still trying, getting closer
>
>
>I use the mod_jk binary obtained from John Turner's how-to page, and
>the
>
>httpd.conf and server.xml statements are the same as the statements in 
>the configurations several other people here have provided as examples,

>I think.  I have also tried to follow John Turner's suggested
>confuguration statements.  
>
>I've tried just about every combination of configurations that have
>been
>
>suggested. It's possible that by now I have mixed up different people's 
>advice, but I don't know what needs to be changed.
>
>I don't know why JK2 is in there, other than the coyote packages that 
>are referenced in sever.xml.  But if I don't use those, what do I use?
>
>I'm beginning to think mod_webapp.so is looking like my only hope of 
>getting Tomcat and Apache to work together.
>
>Jerry
>
>Jerry
>
>Milt Epstein wrote:
>
>  
>
>>On Wed, 25 Dec 2002, Jerry Ford wrote:
>>
>> 
>>
>>
>>
>>>John:
>>>
>>>Sorry, I

RE: Yes!!! It works!!! (was: Re: mod_jk---still trying, getting closer)

[Justin L. Spies]

Denise,
I'm not sure what the difference is between the two systems.  I'm going
to try this again at home and see what I can come up with.  I'll let you
know.

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: Denise Mangano [mailto:[EMAIL PROTECTED]] 
Sent: Friday, December 27, 2002 10:09 AM
To: 'Tomcat Users List'
Subject: RE: Yes!!! It works!!! (was: Re: mod_jk---still trying, getting
closer)


Justin - 

Any thoughts on why that did the trick?  As I mentioned, those
directives are not commented out on my config, but it works?? Just
curious is all...

Thanks!

Denise 


-Original Message-
From: Justin L. Spies [mailto:[EMAIL PROTECTED]] 
Sent: Friday, December 27, 2002 10:01 AM
To: 'Tomcat Users List'
Subject: RE: Yes!!! It works!!! (was: Re: mod_jk---still trying, getting
closer)


This was a message I thought I had sent to the list, but I somehow
managed to send it to Jerry directly...



Congratulations Jerry!  Glad to hear that you've got a working system
now!

Just for the benefit of the other list members out there, the pieces we
commented out were the following:
  
  

  ---   AND   ---




Has anyone else out there had good experience setting up the Apache auto
configuration?


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: Thursday, December 26, 2002 5:31 PM
To: Justin L. Spies
Cc: 'Tomcat Users List'; [EMAIL PROTECTED]
Subject: Yes!!! It works!!! (was: Re: mod_jk---still trying, getting
closer)


Justin, I owe you a beer...

I removed the two listener statements that you commented out in my  
server.xml file and now servlets work from Apache without a port
setting.  

Thank you thank you thank you.  

(And thanks to everyone else who put up with my whining over the past 
few days and offered help---especially Denise, John, and Jeff :)

(BTW, it's academic now, but, yes, on my box tomcat is a symbolic link 
to jakarta-tomcat-4.1.12-LE-jdk14.)

Jerry

Justin L. Spies wrote:

>Jerry,
>I've updated and simplified the configuration files that you supplied 
>previously.  Any changes I made are denoted by the following:
>  NOTE NOTE NOTE NOTE
>
>These changes cause your system to have the same config that I first 
>used to get my system working.  I'm not sure about your directory 
>structure and whether or not you have symlinks setup, however I did 
>notice that in some of the configuration files you were using two 
>different directories that should point to the same directories.  Here 
>is an example from httpd.conf:
>
>You had the following for the JkWorkersFile:
>JkWorkersFile 
>"/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk/workers.pr
>o
>perties"
>
>But just below that you had the following apache directive:
>
>
>These should be the same directory above the /conf directory and above 
>the /webapps directory.  On my system, I have tomcat installed in 
>/var/tomcat4, so I have the following directives:
>
>JkWorkersFile "/var/tomcat4/conf/jk/workers.properties"
>  --  and  --
>
>
>
>See how they are the same first two?  /conf and /webapps should be a 
>subdirectory of /tomcat4 (in my case) or /tomcat (in your case), unless

>you have a symlink (in your case) from 
>/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14 to 
>/usr/local/webserver/tomcat.  Does that make sense, or did I just 
>completely confuse everyone?
>
>Jerry, when you restart Apache and Tomcat, could you send us copies of 
>the apache error log and the tomcat catalina.out files?  Also, if you 
>could confirm the directory structure, that would be a big help.
>
>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: Thursday, December 26, 2002 2:00 PM
>To: Tomcat Users List
>Subject: Re: mod_jk---still trying, getting closer
>
>
>I use the mod_jk binary obtained from John Turner's how-to page, and 
>the
>
>httpd.conf and server.xml statements are the same as the statements in
>the configurations several other people here have provided as examples,

>I think.  I have also tried to follow John Turner's suggested 
>confuguration statements.
>
>I've tried just about every combination of configurations that have 
>been
>
>suggested. It's possible that by now I have mixed up different people's
>advice, but I don't know what ne

Re: Yes!!! It works!!! (was: Re: mod_jk---still trying, getting closer)

[Jerry Ford]

Just to clarify one point for the benefit of the list:

Justin L. Spies wrote:


This was a message I thought I had sent to the list, but I somehow
managed to send it to Jerry directly...



Congratulations Jerry!  Glad to hear that you've got a working system
now!

Just for the benefit of the other list members out there, the pieces we
commented out were the following:
 
 

 ---   AND   ---
   
   


Has anyone else out there had good experience setting up the Apache auto
configuration?

 

The changes (commenting out the listener directives) make my system work 
when mod_jk directives are manually added to httpd.conf, *not* through 
auto conf.  There is no "include .../conf/auto/mod_jk.conf" statement in 
my httpd.conf, all mod_jk references are inline.

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: Thursday, December 26, 2002 5:31 PM
To: Justin L. Spies
Cc: 'Tomcat Users List'; [EMAIL PROTECTED]
Subject: Yes!!! It works!!! (was: Re: mod_jk---still trying, getting
closer)


Justin, I owe you a beer...

I removed the two listener statements that you commented out in my  
server.xml file and now servlets work from Apache without a port
setting.  

Thank you thank you thank you.  

(And thanks to everyone else who put up with my whining over the past 
few days and offered help---especially Denise, John, and Jeff :)

(BTW, it's academic now, but, yes, on my box tomcat is a symbolic link 
to jakarta-tomcat-4.1.12-LE-jdk14.)

Jerry

Justin L. Spies wrote:

 

Jerry,
I've updated and simplified the configuration files that you supplied 
previously.  Any changes I made are denoted by the following:
NOTE NOTE NOTE NOTE

These changes cause your system to have the same config that I first 
used to get my system working.  I'm not sure about your directory 
structure and whether or not you have symlinks setup, however I did 
notice that in some of the configuration files you were using two 
different directories that should point to the same directories.  Here 
is an example from httpd.conf:

You had the following for the JkWorkersFile:
JkWorkersFile 
"/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk/workers.pr
o
perties"

But just below that you had the following apache directive:
  

These should be the same directory above the /conf directory and above 
the /webapps directory.  On my system, I have tomcat installed in 
/var/tomcat4, so I have the following directives:

JkWorkersFile "/var/tomcat4/conf/jk/workers.properties"
--  and  --
  


See how they are the same first two?  /conf and /webapps should be a 
subdirectory of /tomcat4 (in my case) or /tomcat (in your case), unless
   


 

you have a symlink (in your case) from 
/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14 to 
/usr/local/webserver/tomcat.  Does that make sense, or did I just 
completely confuse everyone?

Jerry, when you restart Apache and Tomcat, could you send us copies of 
the apache error log and the tomcat catalina.out files?  Also, if you 
could confirm the directory structure, that would be a big help.

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: Thursday, December 26, 2002 2:00 PM
To: Tomcat Users List
Subject: Re: mod_jk---still trying, getting closer


I use the mod_jk binary obtained from John Turner's how-to page, and 
the

httpd.conf and server.xml statements are the same as the statements in
the configurations several other people here have provided as examples,
   


 

I think.  I have also tried to follow John Turner's suggested 
confuguration statements.  

I've tried just about every combination of configurations that have 
been

suggested. It's possible that by now I have mixed up different people's
advice, but I don't know what needs to be changed.  

I don't know why JK2 is in there, other than the coyote packages that
are referenced in sever.xml.  But if I don't use those, what do I use?

I'm beginning to think mod_webapp.so is looking like my only hope of
getting Tomcat and Apache to work together.

Jerry

Jerry

Milt Epstein wrote:



   

On Wed, 25 Dec 2002, Jerry Ford wrote:



  

 

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.
 



   

One things I don't understand, it seems like you have JK2 running on
the Tomcat side, but you refer to workers.properties, which is a JK 
file, JK2 doesn't use it, I don't believe.  Could that be related to 

RE: Yes!!! It works!!! (was: Re: mod_jk---still trying, getting closer)

[Turner, John]

That tells me that your virtual hosting configuration was messed up.

That is, the URL you were trying (http://localhost) wasn't the URL that
Apache was using to find JkMount statements, or vice versa, or the virtual
host that Apache was using didn't match the virtual host that Tomcat was
expecting.

John


-Original Message-
From: Jerry Ford [mailto:[EMAIL PROTECTED]] 
Sent: Friday, December 27, 2002 12:07 PM
To: Tomcat Users List
Subject: Re: Yes!!! It works!!! (was: Re: mod_jk---still trying, getting
closer)

Just to clarify one point for the benefit of the list:

Justin L. Spies wrote:

>This was a message I thought I had sent to the list, but I somehow
>managed to send it to Jerry directly...
>
>
>
>Congratulations Jerry!  Glad to hear that you've got a working system
>now!
>
>Just for the benefit of the other list members out there, the pieces we
>commented out were the following:
>  
>  
>
>  ---   AND   ---
>
>
>
>
>Has anyone else out there had good experience setting up the Apache auto
>configuration?
>
>  
>
The changes (commenting out the listener directives) make my system work 
when mod_jk directives are manually added to httpd.conf, *not* through 
auto conf.  There is no "include .../conf/auto/mod_jk.conf" statement in 
my httpd.conf, all mod_jk references are inline.

>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: Thursday, December 26, 2002 5:31 PM
>To: Justin L. Spies
>Cc: 'Tomcat Users List'; [EMAIL PROTECTED]
>Subject: Yes!!! It works!!! (was: Re: mod_jk---still trying, getting
>closer)
>
>
>Justin, I owe you a beer...
>
>I removed the two listener statements that you commented out in my  
>server.xml file and now servlets work from Apache without a port
>setting.  
>
>Thank you thank you thank you.  
>
>(And thanks to everyone else who put up with my whining over the past 
>few days and offered help---especially Denise, John, and Jeff :)
>
>(BTW, it's academic now, but, yes, on my box tomcat is a symbolic link 
>to jakarta-tomcat-4.1.12-LE-jdk14.)
>
>Jerry
>
>Justin L. Spies wrote:
>
>  
>
>>Jerry,
>>I've updated and simplified the configuration files that you supplied 
>>previously.  Any changes I made are denoted by the following:
>> NOTE NOTE NOTE NOTE
>>
>>These changes cause your system to have the same config that I first 
>>used to get my system working.  I'm not sure about your directory 
>>structure and whether or not you have symlinks setup, however I did 
>>notice that in some of the configuration files you were using two 
>>different directories that should point to the same directories.  Here 
>>is an example from httpd.conf:
>>
>>You had the following for the JkWorkersFile:
>>JkWorkersFile 
>>"/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk/workers.pr
>>o
>>perties"
>>
>>But just below that you had the following apache directive:
>>   
>>
>>These should be the same directory above the /conf directory and above 
>>the /webapps directory.  On my system, I have tomcat installed in 
>>/var/tomcat4, so I have the following directives:
>>
>>JkWorkersFile "/var/tomcat4/conf/jk/workers.properties"
>> --  and  --
>>   
>>
>>
>>See how they are the same first two?  /conf and /webapps should be a 
>>subdirectory of /tomcat4 (in my case) or /tomcat (in your case), unless
>>
>>
>
>  
>
>>you have a symlink (in your case) from 
>>/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14 to 
>>/usr/local/webserver/tomcat.  Does that make sense, or did I just 
>>completely confuse everyone?
>>
>>Jerry, when you restart Apache and Tomcat, could you send us copies of 
>>the apache error log and the tomcat catalina.out files?  Also, if you 
>>could confirm the directory structure, that would be a big help.
>>
>>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: Thursday, December 26, 2002 2:00 PM
>>To: Tomcat Users List
>>Subject: Re: mod_jk---still trying, getting closer
>>
>>
>>I use the mod_jk binary obtained from John Turner's how-to page, and 
>>the

RE: Yes!!! It works!!! (was: Re: mod_jk---still trying, getting closer)

[Turner, John]

That's the only way I run it.  I can't imagine that the auto-generation was
the culprit.  If it was, it was due to another problem that compounded the
issue.

John


-Original Message-
From: Justin L. Spies [mailto:[EMAIL PROTECTED]] 
Sent: Friday, December 27, 2002 10:01 AM
To: 'Tomcat Users List'
Subject: RE: Yes!!! It works!!! (was: Re: mod_jk---still trying, getting
closer)

This was a message I thought I had sent to the list, but I somehow
managed to send it to Jerry directly...



Congratulations Jerry!  Glad to hear that you've got a working system
now!

Just for the benefit of the other list members out there, the pieces we
commented out were the following:
  
  

  ---   AND   ---




Has anyone else out there had good experience setting up the Apache auto
configuration?


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: Thursday, December 26, 2002 5:31 PM
To: Justin L. Spies
Cc: 'Tomcat Users List'; [EMAIL PROTECTED]
Subject: Yes!!! It works!!! (was: Re: mod_jk---still trying, getting
closer)


Justin, I owe you a beer...

I removed the two listener statements that you commented out in my  
server.xml file and now servlets work from Apache without a port
setting.  

Thank you thank you thank you.  

(And thanks to everyone else who put up with my whining over the past 
few days and offered help---especially Denise, John, and Jeff :)

(BTW, it's academic now, but, yes, on my box tomcat is a symbolic link 
to jakarta-tomcat-4.1.12-LE-jdk14.)

Jerry

Justin L. Spies wrote:

>Jerry,
>I've updated and simplified the configuration files that you supplied 
>previously.  Any changes I made are denoted by the following:
>  NOTE NOTE NOTE NOTE
>
>These changes cause your system to have the same config that I first 
>used to get my system working.  I'm not sure about your directory 
>structure and whether or not you have symlinks setup, however I did 
>notice that in some of the configuration files you were using two 
>different directories that should point to the same directories.  Here 
>is an example from httpd.conf:
>
>You had the following for the JkWorkersFile:
>JkWorkersFile 
>"/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk/workers.pr
>o
>perties"
>
>But just below that you had the following apache directive:
>
>
>These should be the same directory above the /conf directory and above 
>the /webapps directory.  On my system, I have tomcat installed in 
>/var/tomcat4, so I have the following directives:
>
>JkWorkersFile "/var/tomcat4/conf/jk/workers.properties"
>  --  and  --
>
>
>
>See how they are the same first two?  /conf and /webapps should be a 
>subdirectory of /tomcat4 (in my case) or /tomcat (in your case), unless

>you have a symlink (in your case) from 
>/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14 to 
>/usr/local/webserver/tomcat.  Does that make sense, or did I just 
>completely confuse everyone?
>
>Jerry, when you restart Apache and Tomcat, could you send us copies of 
>the apache error log and the tomcat catalina.out files?  Also, if you 
>could confirm the directory structure, that would be a big help.
>
>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: Thursday, December 26, 2002 2:00 PM
>To: Tomcat Users List
>Subject: Re: mod_jk---still trying, getting closer
>
>
>I use the mod_jk binary obtained from John Turner's how-to page, and 
>the
>
>httpd.conf and server.xml statements are the same as the statements in
>the configurations several other people here have provided as examples,

>I think.  I have also tried to follow John Turner's suggested 
>confuguration statements.  
>
>I've tried just about every combination of configurations that have 
>been
>
>suggested. It's possible that by now I have mixed up different people's
>advice, but I don't know what needs to be changed.  
>
>I don't know why JK2 is in there, other than the coyote packages that
>are referenced in sever.xml.  But if I don't use those, what do I use?
>
>I'm beginning to think mod_webapp.so is looking like my only hope of
>getting Tomcat and Apache to work together.
>
>Jerry
>
>Jerry
>
>Milt Epstein wrote:
>
>  
>
>>On Wed, 25 Dec 2002, Jerry Ford wrote:
>>
>> 
>>
>>
>>
>>>John:
>>>
>>>Sorry, I