I think the problem is that, in the .properties files you posted, you have the port as 8080. That's the HTTP port...the JK port is 8009.
John
On Mon, 2 Jun 2003 23:37:04 -0400, Denise Mangano <[EMAIL PROTECTED]> wrote:
I decided to scratch having the second worker since my problems seemed to
start with that approach. I restored everything to the original worker file
and have both default and test virtual hosts pointing to the same
workers.properties.
For some reason, mod_jk is still not working. Its not a problem with Tomcat
itself because I can access everything on port 8080. Apache throws an
internal server error every time I try to access a jsp without the port in
the URL.
The error in the apache error log is:
[Mon Jun 2 23:04:59 2003] [error] Error while opening the workers, jk will
not work
[Mon Jun 2 23:05:01 2003] [error] (2)No such file or directory: Error while
opening the workers, jk will not work
The error in mod_jk.log is:
[Mon Jun 02 23:01:47 2003] [jk_uri_worker_map.c (558)]:
jk_uri_worker_map_t::map_uri_to_worker, Found a suffix match worker -> *.jsp
[Mon Jun 02 23:01:47 2003] [jk_worker.c (132)]: Into wc_get_worker_for_name
worker
[Mon Jun 02 23:01:47 2003] [jk_worker.c (136)]: wc_get_worker_for_name,
done did not found a worker
Content of my worker file is: worker.list = worker worker.worker.type = ajp13 worker.worker.host = localhost worker.worker.port = 8009
My JkMount statements are like this: JkMount /*.jsp worker
I'd appreciate any help on this. It has put me in a pretty serious bind, and I can't for the life of me figure out why it won't work.
Thanks, Denise
-----Original Message-----
From: Denise Mangano [mailto:[EMAIL PROTECTED] Sent: Monday, June 02, 2003 4:56 PM
To: 'Tomcat Users List'
Subject: RE: Strange mod_jk error
By "some configuration changes" I added in virtual hosting. That error
message is gone. I'm not exactly sure what I did to get it to 'go away' but
it did. The problem I am having is that my worker is not being found.
I have two properties files defined. One is workers.properties for use with
the default virtual host, and one is test.workers.properties to use with my
testing virtual host. I tried combining each into one workers.properties
file but still get the same error message. The suffix is matched, but when
it looks for the worker named testWorker it doesn't fin it:
[Mon Jun 02 16:16:57 2003] [jk_worker.c (132)]: Into wc_get_worker_for_name
testWorker [Mon Jun 02 16:16:57 2003] [jk_worker.c (136)]:
wc_get_worker_for_name, done did not found a worker
My test.workers.properties file looks like: worker.list = testWorker worker.testWorker.type = ajp13 worker.testWorker.host = test.mysite.com worker.testWorker.port = 8080
My test.workers.properties file looks like: worker.list = worker worker.worker.type = ajp13 worker.worker.host = www.mysite.com worker.worker.port = 8080
My server.xml, mod_jk.conf and httpd.conf both point to the appropriate
worker properties file within each virtual host. I am in the process of
going over all my config files to see if I missed anything, but it appears
that everything is configured right. Mod_jk is doing its job - but for some
reason it is not finding the definition of the named worker.
Any suggestion? I can post my files if necessary.
Thanks for taking a look! Denise
-----Original Message-----
From: John Turner [mailto:[EMAIL PROTECTED] Sent: Monday, June 02, 2003 4:10 PM
To: Tomcat Users List
Subject: Re: Strange mod_jk error
As far as I know, that error message is socket related, as in the socket is closed, or Apache thinks the socket is closed when it isn't. Its pretty old, from what I know, and should be fixed in recent incarnations of mod_jk. Then again, you are using Apache 1.3.23, so maybe that error still crops up.
Verify that your workers.properties has the right port number, verify that it has the right host, and verify that you don't have any workers configured (like ajp12 or ajp14) that you don't need.
Other than that, you'll have to explain further what you mean by "some configuration changes". ;)
John
On Mon, 2 Jun 2003 16:09:26 -0400, Denise Mangano <[EMAIL PROTECTED]> wrote:
Hi all.
I have not posted in some time as thanks to some great help from this
list my application was running smoothly. However, I needed to make some configuration changes, and now my apps stopped working. Apache (1.3.23) runs fine, and Tomcat (4.1.17) runs fine but the problem is with mod_jk.
I tried searching the archives for this one but had no luck. The error I am
getting in my mod_jk.log is:
In jk_endpoint_t::service, Error sd = -1
And of course the error I am getting in my apache error log shows that it is
looking for the file in the apache web directory. So it appears that mod_jk
is not working and the request is never being interpreted by the JkMount
statements.
Does anyone have any idea what this means? I even tried restoring the original server.xml file, but I still received the error. I can post server.xml, httpd.conf, etc if you need to see it, but I thought first I would send out the error message.
Thanks for your help!
Denise Mangano Help Desk Analyst Complus Data Innovations, Inc.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
