Glad you got it working. Lesson learned on both sides...next time I'll ask for config files right away...we would have spotted multiple JkWorkersFile statements in a heartbeat, and saved you a lot of time and frustration.


John

On Tue, 3 Jun 2003 16:09:54 -0400, Denise Mangano <[EMAIL PROTECTED]> wrote:

I was having some Vhost conflicts which I just cleared up (thanks John). I
ran netstat again, with both Tomcat and Apache running, and these are the
results:
tcp 0 0 *:8009 *:* LISTEN



I was still having the "error opening workers" in apache error log, so I
also removed the path to the workers file from inside the VirtualHost
container to be outside all virtual hosts. The errors are now gone, and ...
the problem is SOLVED!!! Phew...


Thank you, Thank you, Thank you :) That's what a newbie gets for messing
with the configuration. But thankfully it works now, and it is working the
way I want it to (have a new "small" issue - will post separately).


The last note on this, is that in my mod_jk.log, after starting apache, it
has the following code:
[Tue Jun 03 15:45:14 2003] [jk_worker.c (118)]: Into wc_close
[Tue Jun 03 15:45:14 2003] [jk_worker.c (199)]: close_workers got -1
workers to destroy
[Tue Jun 03 15:45:14 2003] [jk_worker.c (120)]: wc_close, done
[Tue Jun 03 15:45:14 2003] [jk_uri_worker_map.c (190)]: Into
jk_uri_worker_map_t::uri_worker_map_free
[Tue Jun 03 15:45:14 2003] [jk_uri_worker_map.c (441)]: Into
jk_uri_worker_map_t::uri_worker_map_close


The weird thing is that it has this code repeatedly, every time ... 12 times
to be exact. Is that normal?


Thanks again to both of you for all your help :)
Denise


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



Reply via email to