RE: IIS 5.1 and Tomcat 4
> The module that could not be found, it seems like IIS is > talking about > isapi_redirect.dll. I don't know > really how it all works with these isapi filters, but the > file should be downloadable from a browser, so > you should try pointing your browser to > http://locahost/jakarta/isapi_redirect.dll > and make sure you can download the file. If that does not work you > have access problems. The IIS > user can't reach the file. I think we are close to a solution now. Well done - that was indeed the problem! (I still can't download isapi_redirect.dll because I haven't given read access to the directory) but you pointed me in the right direction - I was pointing /jakarta at the tomcat directory rather than the directory underneath it. I've changed that, and it's all working fine now :) I think the reason I didn't check before was that clearly it *was* finding the module at some stage, otherwise I wouldn't have had an isapi.log file - but presumably it needs it in two different ways. Anyway, thank you ever so much - you're a star :) Jon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: IIS 5.1 and Tomcat 4
True, my mistake. ;-) The module that could not be found, it seems like IIS is talking about isapi_redirect.dll. I don't know really how it all works with these isapi filters, but the file should be downloadable from a browser, so you should try pointing your browser to http://locahost/jakarta/isapi_redirect.dll and make sure you can download the file. If that does not work you have access problems. The IIS user can't reach the file. I think we are close to a solution now. Mats Jon Skeet wrote: [Replying to two posts from Mats at once] (About not being able to sniff local packets) Correct, but can't you use a browser on another machine? Yes, but that wouldn't help - it's the IIS->Tomcat communication which is at issue here (I thought, anyway) and that would still be local. I don't have easy access to another machine to test all this with IIS on one box and Tomcat on another - although it's the next step if I can't get anywhere soon. What do you get in the browser when trying to connect? "The specified module could not be found." Jon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: IIS 5.1 and Tomcat 4
The attached TXT file is what I used to get it to work for me. I wrote it
step by step when I was configuring my server here.
I kept getting errors with the ISAPI_Redirector2.dll file, so I went back to
the older version and it worked fine for me with Tomcat 5.0.12
The TXT file is a little sparse and not 100% cleaned up, but you should get
the general idea.
Whenever I tried to use the ISAPI2 redirector, it would just come back with
a Server connection or DNS error, but when I changed it to the older version
of the ISAPI DLL, it worked fine.
See if this helps you at all.
Richard Norman
Web/Application Developer
Original Message Follows
From: "Januski, Ken" <[EMAIL PROTECTED]>
Reply-To: "Tomcat Users List" <[EMAIL PROTECTED]>
To: Tomcat Users List <[EMAIL PROTECTED]>
Subject: RE: IIS 5.1 and Tomcat 4
Date: Tue, 23 Sep 2003 14:31:36 -0400
Jon,
I think that the log is telling you just what it should. Tomcat looks for a
mapping of server name to servlet in web.xml. So it won't find one for
localhost or machine name but that's really not important. It will find
nothing for them and move on. What it should find and does is the mapping
from servlet name to servlet. So it seems to me that it is finding the
mapping correctly. The problem is that nothing is happening after that.
Have you looked at the IIS logs to see what they say? They should include
line for isapi_redirect or isapi_redirecto2.dll and SHOULD have a 200 as
server response, e.g.
POST /jakarta/isapi_redirector2.dll - 200 0 4096 690
When I was trying this it took me forever to get it to change from 400/500
to 200 I believe. Unfortunately this won't solve your problem but it may
move you further toward a solution.
Ken
-Original Message-
From: Jon Skeet [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 23, 2003 5:42 AM
To: Tomcat Users List
Subject: RE: IIS 5.1 and Tomcat 4
> It seems like /mobilizer/mobilizer/ finds its way through,
> but the path /localhost/mobilizer/mobilizer doesn't. Is that correct?
What
> is the path starting with /localhost, is this really your intention?
There shouldn't be any path starting with /localhost. I'm visiting the
URL
http://localhost/mobilizer/mobilizer
but the localhost part is the servername, not the path.
This appears to be consistent with the log I get when I use the name of
the computer rather than localhost, eg:
[Tue Sep 23 10:40:11 2003] [jk_uri_worker_map.c (351)]: Into
jk_uri_worker_map_t::map_uri_to_worker
[Tue Sep 23 10:40:11 2003] [jk_uri_worker_map.c (368)]: Attempting to
map URI '/treebeard/mobilizer/mobilizer/'
[Tue Sep 23 10:40:11 2003] [jk_uri_worker_map.c (456)]:
jk_uri_worker_map_t::map_uri_to_worker, done without a match
My guess is that it's something IIS is doing for the sake of virtual
hosting, but I wouldn't like to say for sure.
The /mobilizer/mobilizer path is the correct one - but I don't know why
it's then not getting any further than it is doing.
Jon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Sincerely,
^
{ Richard Norman }
{ Big Brother "Jazzy"}
{ }
{ "The Brother with the Smooth }
{moves and Mellow grooves"}
{ }
{Kappa Alpha Psi Fraternity, Inc. }
{ Beta Omega Chapter }
{ }
{ Nemesis - "Kan't Be Faded!!!" }
{ Ace Klub - Fall 94 }
#
"Training For Leadership!!!"
"Many are Kalled but Few are Chosen!!"
WebSite (new): http://Jazzynupe.no-ip.com
_
Add MSN 8 Internet Software to your existing Internet access and enjoy
patented spam protection and more. Sign up now!
http://join.msn.com/?page=dept/byoa
Install Tomcat to work with IIS as web server
[EMAIL PROTECTED]
step 1: Install Tomcat
From my example I installed to c:\Tomcat\Tomcat-[version]
Step 2: Copy ISAPI extension to bin\ISAPI folder (you must create the ISAPI
folder)
You can copy both versions if you wish for easy switching
(isapi_redirector2.dll and isapi_redirect.dll)
Step 3: Create this folder as a web virtual directory named "jakarta" with
"Run executables" permissions
*** In conf\server.xml file ***
Step 4: configure host to include IIS root as appBase
*** example ***
***
use forward slashes instead of back slashes for directory
seperation.
Step 5: Include any other Application contexts you wish
*** example ***
***
Step 6: configure the AJP 1.3 listener to listen on the
RE: IIS 5.1 and Tomcat 4
Jon, I think that the log is telling you just what it should. Tomcat looks for a mapping of server name to servlet in web.xml. So it won't find one for localhost or machine name but that's really not important. It will find nothing for them and move on. What it should find and does is the mapping from servlet name to servlet. So it seems to me that it is finding the mapping correctly. The problem is that nothing is happening after that. Have you looked at the IIS logs to see what they say? They should include line for isapi_redirect or isapi_redirecto2.dll and SHOULD have a 200 as server response, e.g. POST /jakarta/isapi_redirector2.dll - 200 0 4096 690 When I was trying this it took me forever to get it to change from 400/500 to 200 I believe. Unfortunately this won't solve your problem but it may move you further toward a solution. Ken -Original Message- From: Jon Skeet [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 23, 2003 5:42 AM To: Tomcat Users List Subject: RE: IIS 5.1 and Tomcat 4 > It seems like /mobilizer/mobilizer/ finds its way through, > but the path /localhost/mobilizer/mobilizer doesn't. Is that correct? What > is the path starting with /localhost, is this really your intention? There shouldn't be any path starting with /localhost. I'm visiting the URL http://localhost/mobilizer/mobilizer but the localhost part is the servername, not the path. This appears to be consistent with the log I get when I use the name of the computer rather than localhost, eg: [Tue Sep 23 10:40:11 2003] [jk_uri_worker_map.c (351)]: Into jk_uri_worker_map_t::map_uri_to_worker [Tue Sep 23 10:40:11 2003] [jk_uri_worker_map.c (368)]: Attempting to map URI '/treebeard/mobilizer/mobilizer/' [Tue Sep 23 10:40:11 2003] [jk_uri_worker_map.c (456)]: jk_uri_worker_map_t::map_uri_to_worker, done without a match My guess is that it's something IIS is doing for the sake of virtual hosting, but I wouldn't like to say for sure. The /mobilizer/mobilizer path is the correct one - but I don't know why it's then not getting any further than it is doing. Jon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: IIS 5.1 and Tomcat 4
> Please excuse my butting in mid-thread as I may have missed > something. I've spent more time than I'd like getting IIS and > Tomcat working in the past but unfortunately don't remember > all the details. One thing I do notice from earlier thread is > that you seem to be calling the host "localhost". See below. > Perhaps you should change it to machine name? It *should* be fine like that (as IIS and Tomcat are on the same machine) - I've used it before with Tomcat 3.2.3 and IIS with localhost. I'll certainly give it a whirl though. Nope. No luck. I've tried 127.0.0.1 and 192.168.0.8 (my IP address), and the results are the same. I don't have DNS running at home (where I am now) but I could try that tomorrow if you think it would be worth it - I'd have thought it should work with numeric addresses though. I've also tried changing the host to 128.0.0.1 - and I *still* don't see anything with Ethereal, which really *does* suggest that IIS isn't trying to connect. (I can see connection attempts with telnet to 128.0.0.1.) Jon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: IIS 5.1 and Tomcat 4
[Replying to two posts from Mats at once] (About not being able to sniff local packets) > Correct, but can't you use a browser on another machine? Yes, but that wouldn't help - it's the IIS->Tomcat communication which is at issue here (I thought, anyway) and that would still be local. I don't have easy access to another machine to test all this with IIS on one box and Tomcat on another - although it's the next step if I can't get anywhere soon. > What do you get in the browser when trying to connect? "The specified module could not be found." Jon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: IIS 5.1 and Tomcat 4
What do you get in the browser when trying to connect? Mats Jon Skeet wrote: I've got a port monitor which just shows connections - and it shows no sign of IIS trying to contact Tomcat. I'll try with Ethereal as well. Darn - Ethereal won't (as far as I can see) let me capture network activity within my own system (ie the loopback, effectively). Any ideas what will? (I've tried various sniffers in the past, and none of them have particularly appealed - I'd welcome recommendations.) Jon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: IIS 5.1 and Tomcat 4
Please excuse my butting in mid-thread as I may have missed something. I've spent more time than I'd like getting IIS and Tomcat working in the past but unfortunately don't remember all the details. One thing I do notice from earlier thread is that you seem to be calling the host "localhost". See below. Perhaps you should change it to machine name? Ken >[workers.properties] >worker.ajp13.port=8009 >worker.ajp13.host=localhost >worker.ajp13.type=ajp13 >worker.ajp13.lbfactor=1 -Original Message- From: Jon Skeet [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 23, 2003 5:42 AM To: Tomcat Users List Subject: RE: IIS 5.1 and Tomcat 4 > It seems like /mobilizer/mobilizer/ finds its way through, > but the path /localhost/mobilizer/mobilizer doesn't. Is that correct? What > is the path starting with /localhost, is this really your intention? There shouldn't be any path starting with /localhost. I'm visiting the URL http://localhost/mobilizer/mobilizer but the localhost part is the servername, not the path. This appears to be consistent with the log I get when I use the name of the computer rather than localhost, eg: [Tue Sep 23 10:40:11 2003] [jk_uri_worker_map.c (351)]: Into jk_uri_worker_map_t::map_uri_to_worker [Tue Sep 23 10:40:11 2003] [jk_uri_worker_map.c (368)]: Attempting to map URI '/treebeard/mobilizer/mobilizer/' [Tue Sep 23 10:40:11 2003] [jk_uri_worker_map.c (456)]: jk_uri_worker_map_t::map_uri_to_worker, done without a match My guess is that it's something IIS is doing for the sake of virtual hosting, but I wouldn't like to say for sure. The /mobilizer/mobilizer path is the correct one - but I don't know why it's then not getting any further than it is doing. Jon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: IIS 5.1 and Tomcat 4
Correct, but can't you use a browser on another machine? Mats Jon Skeet wrote: I've got a port monitor which just shows connections - and it shows no sign of IIS trying to contact Tomcat. I'll try with Ethereal as well. Darn - Ethereal won't (as far as I can see) let me capture network activity within my own system (ie the loopback, effectively). Any ideas what will? (I've tried various sniffers in the past, and none of them have particularly appealed - I'd welcome recommendations.) Jon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: IIS 5.1 and Tomcat 4
> I've got a port monitor which just shows connections - and it > shows no sign of IIS trying to contact Tomcat. I'll try with > Ethereal as well. Darn - Ethereal won't (as far as I can see) let me capture network activity within my own system (ie the loopback, effectively). Any ideas what will? (I've tried various sniffers in the past, and none of them have particularly appealed - I'd welcome recommendations.) Jon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: IIS 5.1 and Tomcat 4
> That explains the localhost part.
It worries me a bit though - I don't like the idea of paths having to
*not* start with the machine name, just in case things get confused :(
> Then I would try with a network
> sniffer (or whatever they are called)
> to find out if IIS tries to contact tomcat at 8009. If you don't have
> one, I suggest Ethereal at
>
> www.ethereal.com/
I've got a port monitor which just shows connections - and it shows no
sign of IIS trying to contact Tomcat. I'll try with Ethereal as well.
> BTW: Do you get a strange stacktrace at startup (MBean
> something...)?
Nope.
> Do the tomcat shutdown take a long time?
No - although to be fair I'm not using the "normal" NT service manager -
we have our own one which calls
org.apache.catalina.startup.Bootstrap.main (new string[]{"stop"})
basically.
It *did* give a stack trace before, but I've patched ChannelSocket to
stop that from misbehaving.
> If so, you can try removing the connector at 8009 and instead use the
> 8081 one at port 8009.
> The org.apache.coyote.tomcat4.CoyoteConnector is a new one used with
> jk2, but I can't imagine that it won't work with jk as well, since the
protocol is the
> same (ajp13).
That's what I was wondering - but I've tried just changing worker port
to 8081, and that doesn't seem to have made any difference.
> Also you can add these rules to uriworkermap.properties, just
> to see if
> anything changes in the log file:
>
> /localhost/mobilizer/mobilizer/*=$(default.worker)
> /mobilizer/mobilizer/*=$(default.worker)
Well, now /localhost/mobilizer/mobilizer matches, but that's the only
real difference. The end of the log looks like this:
[Tue Sep 23 12:11:03 2003] [jk_isapi_plugin.c (555)]: HttpFilterProc
started
[Tue Sep 23 12:11:03 2003] [jk_isapi_plugin.c (600)]: In HttpFilterProc
Virtual Host redirection of /localhost/mobilizer/mobilizer/
[Tue Sep 23 12:11:03 2003] [jk_uri_worker_map.c (351)]: Into
jk_uri_worker_map_t::map_uri_to_worker
[Tue Sep 23 12:11:03 2003] [jk_uri_worker_map.c (368)]: Attempting to
map URI '/localhost/mobilizer/mobilizer/'
[Tue Sep 23 12:11:03 2003] [jk_uri_worker_map.c (391)]:
jk_uri_worker_map_t::map_uri_to_worker, Found a context match ajp13 ->
/localhost/mobilizer/mobilizer/
[Tue Sep 23 12:11:03 2003] [jk_isapi_plugin.c (617)]: HttpFilterProc
[/mobilizer/mobilizer/] is a servlet url - should redirect to ajp13
[Tue Sep 23 12:11:03 2003] [jk_isapi_plugin.c (639)]: HttpFilterProc
check if [/mobilizer/mobilizer/] is points to the web-inf directory
I'll have a look with Ethereal now and see if that gives any more clues.
I'm sure we'll find something really silly in the end - it's just
finding it that's the problem :(
Thanks for helping,
Jon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: IIS 5.1 and Tomcat 4
That explains the localhost part. Then I would try with a network sniffer (or whatever they are called) to find out if IIS tries to contact tomcat at 8009. If you don't have one, I suggest Ethereal at www.ethereal.com/ BTW: Do you get a strange stacktrace at startup (MBean something...)? Do the tomcat shutdown take a long time? If so, you can try removing the connector at 8009 and instead use the 8081 one at port 8009. The org.apache.coyote.tomcat4.CoyoteConnector is a new one used with jk2, but I can't imagine that it won't work with jk as well, since the protocol is the same (ajp13). Also you can add these rules to uriworkermap.properties, just to see if anything changes in the log file: /localhost/mobilizer/mobilizer/*=$(default.worker) /mobilizer/mobilizer/*=$(default.worker) Mats Jon Skeet wrote: It seems like /mobilizer/mobilizer/ finds its way through, but the path /localhost/mobilizer/mobilizer doesn't. Is that correct? What is the path starting with /localhost, is this really your intention? There shouldn't be any path starting with /localhost. I'm visiting the URL http://localhost/mobilizer/mobilizer but the localhost part is the servername, not the path. This appears to be consistent with the log I get when I use the name of the computer rather than localhost, eg: [Tue Sep 23 10:40:11 2003] [jk_uri_worker_map.c (351)]: Into jk_uri_worker_map_t::map_uri_to_worker [Tue Sep 23 10:40:11 2003] [jk_uri_worker_map.c (368)]: Attempting to map URI '/treebeard/mobilizer/mobilizer/' [Tue Sep 23 10:40:11 2003] [jk_uri_worker_map.c (456)]: jk_uri_worker_map_t::map_uri_to_worker, done without a match My guess is that it's something IIS is doing for the sake of virtual hosting, but I wouldn't like to say for sure. The /mobilizer/mobilizer path is the correct one - but I don't know why it's then not getting any further than it is doing. Jon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: IIS 5.1 and Tomcat 4
> It seems like /mobilizer/mobilizer/ finds its way through, > but the path /localhost/mobilizer/mobilizer doesn't. Is that correct? What > is the path starting with /localhost, is this really your intention? There shouldn't be any path starting with /localhost. I'm visiting the URL http://localhost/mobilizer/mobilizer but the localhost part is the servername, not the path. This appears to be consistent with the log I get when I use the name of the computer rather than localhost, eg: [Tue Sep 23 10:40:11 2003] [jk_uri_worker_map.c (351)]: Into jk_uri_worker_map_t::map_uri_to_worker [Tue Sep 23 10:40:11 2003] [jk_uri_worker_map.c (368)]: Attempting to map URI '/treebeard/mobilizer/mobilizer/' [Tue Sep 23 10:40:11 2003] [jk_uri_worker_map.c (456)]: jk_uri_worker_map_t::map_uri_to_worker, done without a match My guess is that it's something IIS is doing for the sake of virtual hosting, but I wouldn't like to say for sure. The /mobilizer/mobilizer path is the correct one - but I don't know why it's then not getting any further than it is doing. Jon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: IIS 5.1 and Tomcat 4
[Tue Sep 23 09:31:04 2003] [jk_isapi_plugin.c (672)]: In HttpFilterProc Virtual Host redirection of /localhost/mobilizer/mobilizer/ [Tue Sep 23 09:31:04 2003] [jk_uri_worker_map.c (351)]: Into jk_uri_worker_map_t::map_uri_to_worker [Tue Sep 23 09:31:04 2003] [jk_uri_worker_map.c (368)]: Attempting to map URI '/localhost/mobilizer/mobilizer/' [Tue Sep 23 09:31:04 2003] [jk_uri_worker_map.c (456)]: jk_uri_worker_map_t::map_uri_to_worker, done without a match [Tue Sep 23 09:31:04 2003] [jk_isapi_plugin.c (678)]: In HttpFilterProc test Default redirection of /mobilizer/mobilizer/ [Tue Sep 23 09:31:04 2003] [jk_uri_worker_map.c (351)]: Into jk_uri_worker_map_t::map_uri_to_worker [Tue Sep 23 09:31:04 2003] [jk_uri_worker_map.c (368)]: Attempting to map URI '/mobilizer/mobilizer/' [Tue Sep 23 09:31:04 2003] [jk_uri_worker_map.c (391)]: jk_uri_worker_map_t::map_uri_to_worker, Found a context match ajp13 -> /mobilizer/ [Tue Sep 23 09:31:04 2003] [jk_isapi_plugin.c (688)]: HttpFilterProc [/mobilizer/mobilizer/] is a servlet url - should redirect to ajp13 [Tue Sep 23 09:31:04 2003] [jk_isapi_plugin.c (737)]: HttpFilterProc check if [/mobilizer/mobilizer/] is points to the web-inf directory It seems like /mobilizer/mobilizer/ finds its way through, but the path /localhost/mobilizer/mobilizer doesn't. Is that correct? What is the path starting with /localhost, is this really your intention? Mats Jon Skeet wrote: Just checking this, my log definitely shows it's found the ajp13 stuff: [Mon Sep 22 16:22:03 2003] [jk_worker.c (82)]: Into wc_open [Mon Sep 22 16:22:03 2003] [jk_worker.c (207)]: Into build_worker_map, creating 1 workers [Mon Sep 22 16:22:03 2003] [jk_worker.c (213)]: build_worker_map, creating worker ajp13 [Mon Sep 22 16:22:03 2003] [jk_worker.c (138)]: Into wc_create_worker [Mon Sep 22 16:22:03 2003] [jk_worker.c (152)]: wc_create_worker, about to create instance ajp13 of ajp13 [Mon Sep 22 16:22:03 2003] [jk_ajp13_worker.c (922)]: Into ajp13_worker_factory [Mon Sep 22 16:22:03 2003] [jk_worker.c (161)]: wc_create_worker, about to validate and init ajp13 [Mon Sep 22 16:22:03 2003] [jk_ajp13_worker.c (443)]: Into jk_worker_t::validate [Mon Sep 22 16:22:03 2003] [jk_ajp13_worker.c (456)]: In jk_worker_t::validate for worker ajp13 contact is localhost:8009 [Mon Sep 22 16:22:03 2003] [jk_ajp13_worker.c (482)]: Into jk_worker_t::init [Mon Sep 22 16:22:03 2003] [jk_worker.c (177)]: wc_create_worker, done [Mon Sep 22 16:22:03 2003] [jk_worker.c (223)]: build_worker_map, removing old ajp13 worker [Mon Sep 22 16:22:03 2003] [jk_worker.c (235)]: build_worker_map, done [Mon Sep 22 16:22:03 2003] [jk_worker.c (102)]: wc_open, done (I assume the "removing old ajp13 worker is okay?) Looking with a TCP viewer, my Tomcat installation is definitely listening on port 8009, but there's no sign of IIS trying to connect to it, which at least suggests that the problem's somewhere there rather than in server.xml. There doesn't seem to be much I could have done wrong - I'm rather confused :( Jon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: IIS 5.1 and Tomcat 4
If you want you may send me your workers.properties uriworkermap.properties and exported registry settings and I will look closer at it. I can send you the dll files for jk and jk2 if you want. I have no idea why they are removed and where they are now. Mats Jon Skeet wrote: Just checking this, my log definitely shows it's found the ajp13 stuff: [Mon Sep 22 16:22:03 2003] [jk_worker.c (82)]: Into wc_open [Mon Sep 22 16:22:03 2003] [jk_worker.c (207)]: Into build_worker_map, creating 1 workers [Mon Sep 22 16:22:03 2003] [jk_worker.c (213)]: build_worker_map, creating worker ajp13 [Mon Sep 22 16:22:03 2003] [jk_worker.c (138)]: Into wc_create_worker [Mon Sep 22 16:22:03 2003] [jk_worker.c (152)]: wc_create_worker, about to create instance ajp13 of ajp13 [Mon Sep 22 16:22:03 2003] [jk_ajp13_worker.c (922)]: Into ajp13_worker_factory [Mon Sep 22 16:22:03 2003] [jk_worker.c (161)]: wc_create_worker, about to validate and init ajp13 [Mon Sep 22 16:22:03 2003] [jk_ajp13_worker.c (443)]: Into jk_worker_t::validate [Mon Sep 22 16:22:03 2003] [jk_ajp13_worker.c (456)]: In jk_worker_t::validate for worker ajp13 contact is localhost:8009 [Mon Sep 22 16:22:03 2003] [jk_ajp13_worker.c (482)]: Into jk_worker_t::init [Mon Sep 22 16:22:03 2003] [jk_worker.c (177)]: wc_create_worker, done [Mon Sep 22 16:22:03 2003] [jk_worker.c (223)]: build_worker_map, removing old ajp13 worker [Mon Sep 22 16:22:03 2003] [jk_worker.c (235)]: build_worker_map, done [Mon Sep 22 16:22:03 2003] [jk_worker.c (102)]: wc_open, done (I assume the "removing old ajp13 worker is okay?) Looking with a TCP viewer, my Tomcat installation is definitely listening on port 8009, but there's no sign of IIS trying to connect to it, which at least suggests that the problem's somewhere there rather than in server.xml. There doesn't seem to be much I could have done wrong - I'm rather confused :( Jon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: IIS 5.1 and Tomcat 4
Just checking this, my log definitely shows it's found the ajp13 stuff: [Mon Sep 22 16:22:03 2003] [jk_worker.c (82)]: Into wc_open [Mon Sep 22 16:22:03 2003] [jk_worker.c (207)]: Into build_worker_map, creating 1 workers [Mon Sep 22 16:22:03 2003] [jk_worker.c (213)]: build_worker_map, creating worker ajp13 [Mon Sep 22 16:22:03 2003] [jk_worker.c (138)]: Into wc_create_worker [Mon Sep 22 16:22:03 2003] [jk_worker.c (152)]: wc_create_worker, about to create instance ajp13 of ajp13 [Mon Sep 22 16:22:03 2003] [jk_ajp13_worker.c (922)]: Into ajp13_worker_factory [Mon Sep 22 16:22:03 2003] [jk_worker.c (161)]: wc_create_worker, about to validate and init ajp13 [Mon Sep 22 16:22:03 2003] [jk_ajp13_worker.c (443)]: Into jk_worker_t::validate [Mon Sep 22 16:22:03 2003] [jk_ajp13_worker.c (456)]: In jk_worker_t::validate for worker ajp13 contact is localhost:8009 [Mon Sep 22 16:22:03 2003] [jk_ajp13_worker.c (482)]: Into jk_worker_t::init [Mon Sep 22 16:22:03 2003] [jk_worker.c (177)]: wc_create_worker, done [Mon Sep 22 16:22:03 2003] [jk_worker.c (223)]: build_worker_map, removing old ajp13 worker [Mon Sep 22 16:22:03 2003] [jk_worker.c (235)]: build_worker_map, done [Mon Sep 22 16:22:03 2003] [jk_worker.c (102)]: wc_open, done (I assume the "removing old ajp13 worker is okay?) Looking with a TCP viewer, my Tomcat installation is definitely listening on port 8009, but there's no sign of IIS trying to connect to it, which at least suggests that the problem's somewhere there rather than in server.xml. There doesn't seem to be much I could have done wrong - I'm rather confused :( Jon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: IIS 5.1 and Tomcat 4
(Thanks for replying, btw :) > I think you must have this row in your workers.properties: > worker.list=ajp13 I'm afraid I already have that - I must have been a bit overenthusiastic when snipping my file down to a manageable file for mailing list purposes. > >o isapi_redirect.dll from > >http://apache.oregonstate.edu/jakarta/tomcat-3/bin/win32/i386/ > >(That's the only place I could find it, and it took a while > to find... > >should I be worried that it's in the Tomcat 3 directory?) > > > Go here instead. Seems better. > http://www.apache.org/dist/jakarta/tomcat-connectors/ Sounds promising, but unfortunately it's empty as far as I can see. (Or rather, there are directories for coyote, jk, jk2 and webapp, but they're all empty.) > >o Registry entries in Jakarta Isapi Redirector\1.0 (which I think are > >okay) > They are, you have the green up Good. One thing less to worry about :) > >server.xml has: > > > > > port="8081" minProcessors="5" maxProcessors="75" > > enableLookups="true" redirectPort="8443" > > acceptCount="10" debug="0" connectionTimeout="0" > > useURIValidationHack="false" > > > >protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"/> > > > > > > > port="8009" minProcessors="5" maxProcessors="75" > > acceptCount="10" debug="0"/> > > > >I was slightly unsure about this - given that I want the first one > >(note the non-default port, by the way) do I actually need > the second? > >Should I just be able to change teh port in workers.properties? > > > > > workers.properties in your configuration tells IIS that your worker > (=tomcat) will listen at port 8009) while the > > Connector declaration in server.xml tells tomcat that it > sould start the AJP13 Connector on port 8009. So, you need both. Sorry - I wasn't clear. What I meant was, can I get rid of the Ajp13Connector part of server.xml, and just use the JkCoyote connector? Or can I get rid of the JkCoyote connector and just use the Ajp13Connector? I can't see why I'd need both, but I'd appreciate any advice on which is better, etc. > >Any clues as to what I'm missing? > IIS does listen on your requests and the dll is registered > ok, but for some reason it can't map the request > to a worker (= a running tomcat instance). I think it is because you > miss the worker.list as I described it above. How I wish that were the case. One thing I'm *not* doing is specifying workers.tomcat_home or workers.java_home - as I'm starting Tomcat up separately, I don't think I need those. Is that right? > I use jk2. Some people say it is not as stable as jk, but I have not > encountered any problems with it yet. > My reason is that the old jk does not support MBeans, don't > ask what it is more precisely, but my tomcat > will generate a (harmless) stacktrace at the beginning telling me this. > Later when I shut my tomcat down, the shutdown process takes a long time, > probably waiting to shut down the jk module in tomcat, which does not support > being shut down like a MBean or something. Have you the same > experience with jk? I haven't seen anything like that, although I needed to patch JK's ChannelSocket class in order to get it to shut down cleanly. (It's fine now though.) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: IIS 5.1 and Tomcat 4
I think you must have this row in your workers.properties: worker.list=ajp13 More comments are embedded in your text below. Please let me know it this helps. /Mats Jon Skeet wrote: I'm trying to get IIS 5.1 and Tomcat 4 to play nicely together. So far I've not got very far. I've got: o isapi_redirect.dll from http://apache.oregonstate.edu/jakarta/tomcat-3/bin/win32/i386/ (That's the only place I could find it, and it took a while to find... should I be worried that it's in the Tomcat 3 directory?) Go here instead. Seems better. http://www.apache.org/dist/jakarta/tomcat-connectors/ o Registry entries in Jakarta Isapi Redirector\1.0 (which I think are okay) They are, you have the green up workers.properties and uriworkermap.properties which I think are okay. Only useful bits in them are: [workers.properties] worker.ajp13.port=8009 worker.ajp13.host=localhost worker.ajp13.type=ajp13 worker.ajp13.lbfactor=1 [uriworkermap.properties] default.worker=ajp13 /mobilizer/*=$(default.worker) server.xml has: protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"/> I was slightly unsure about this - given that I want the first one (note the non-default port, by the way) do I actually need the second? Should I just be able to change teh port in workers.properties? workers.properties in your configuration tells IIS that your worker (=tomcat) will listen at port 8009) while the Connector declaration in server.xml tells tomcat that it sould start the AJP13 Connector on port 8009. So, you need both. The servlets work fine from the HTTP connector. IIS has a jakarta virtual directory with execute script permission, the ISAPI filter is up (green arrow), but I get: "The specified module could not be found." on my web browser. The catalina log has: 2003-09-19 14:02:42 Ajp13Connector[8009] Opening server socket on all host IP addresses 2003-09-19 14:02:42 Ajp13Connector[8009] Starting background thread 2003-09-19 14:02:42 Ajp13Processor[8009][0] Starting background thread 2003-09-19 14:02:42 Ajp13Processor[8009][1] Starting background thread 2003-09-19 14:02:42 Ajp13Processor[8009][2] Starting background thread 2003-09-19 14:02:42 Ajp13Processor[8009][3] Starting background thread 2003-09-19 14:02:43 Ajp13Processor[8009][4] Starting background thread The localhost log doesn't seem to mention anything in particular. The isapi log has lines such as: [Fri Sep 19 14:04:40 2003] [jk_isapi_plugin.c (626)]: HttpFilterProc started [Fri Sep 19 14:04:40 2003] [jk_isapi_plugin.c (672)]: In HttpFilterProc Virtual Host redirection of /localhost/mobilizer/mobilizer [Fri Sep 19 14:04:40 2003] [jk_uri_worker_map.c (351)]: Into jk_uri_worker_map_t::map_uri_to_worker [Fri Sep 19 14:04:40 2003] [jk_uri_worker_map.c (368)]: Attempting to map URI '/localhost/mobilizer/mobilizer' [Fri Sep 19 14:04:40 2003] [jk_uri_worker_map.c (456)]: jk_uri_worker_map_t::map_uri_to_worker, done without a match [Fri Sep 19 14:04:40 2003] [jk_isapi_plugin.c (678)]: In HttpFilterProc test Default redirection of /mobilizer/mobilizer [Fri Sep 19 14:04:40 2003] [jk_uri_worker_map.c (351)]: Into jk_uri_worker_map_t::map_uri_to_worker [Fri Sep 19 14:04:40 2003] [jk_uri_worker_map.c (368)]: Attempting to map URI '/mobilizer/mobilizer' [Fri Sep 19 14:04:40 2003] [jk_uri_worker_map.c (391)]: jk_uri_worker_map_t::map_uri_to_worker, Found a context match ajp13 -> /mobilizer/ [Fri Sep 19 14:04:40 2003] [jk_isapi_plugin.c (688)]: HttpFilterProc [/mobilizer/mobilizer] is a servlet url - should redirect to ajp13 [Fri Sep 19 14:04:40 2003] [jk_isapi_plugin.c (737)]: HttpFilterProc check if [/mobilizer/mobilizer] is points to the web-inf directory [Fri Sep 19 14:19:23 2003] [jk_isapi_plugin.c (626)]: HttpFilterProc started [Fri Sep 19 14:19:23 2003] [jk_isapi_plugin.c (672)]: In HttpFilterProc Virtual Host redirection of /localhost/mobilizer/mobilizer/ [Fri Sep 19 14:19:23 2003] [jk_uri_worker_map.c (351)]: Into jk_uri_worker_map_t::map_uri_to_worker [Fri Sep 19 14:19:23 2003] [jk_uri_worker_map.c (368)]: Attempting to map URI '/localhost/mobilizer/mobilizer/' [Fri Sep 19 14:19:23 2003] [jk_uri_worker_map.c (456)]: jk_uri_worker_map_t::map_uri_to_worker, done without a match [Fri Sep 19 14:19:23 2003] [jk_isapi_plugin.c (678)]: In HttpFilterProc test Default redirection of /mobilizer/mobilizer/ [Fri Sep 19 14:19:23 2003] [jk_uri_worker_map.c (351)]: Into jk_uri_worker_map_t::map_uri_to_worker [Fri Sep 19 14:19:23 2003] [jk_uri_worker_map.c (368)]: Attempting to map URI '/mobilizer/mobilizer/' [Fri Sep 19 14:19:23 2003] [jk_uri_worker_map.c (391)]: jk_uri_worker_map_t::map_uri_to_worker, Found a context match ajp13 -> /mobilizer/ [Fri Sep 19 14:19:23 2003] [jk_isapi_plugin.c (688)]: HttpFilterProc [/mobilizer/mobilizer/] is a servlet url - should redirect to ajp13 [Fri Sep 19 14:19:23 2003] [jk_isapi_plugin.c (737)]: HttpFilt
RE: IIS 5.1 and Tomcat 4
> I'm trying to get IIS 5.1 and Tomcat 4 to play nicely together. Did this question not get answered because: a) I didn't provide enough information b) Few people on the list have hooked IIS up to Tomcat c) A more interesting question (OutOfMemoryError) came in soon afterwards ? If you can spare a minute and know about hooking IIS and Tomcat together, I'd be grateful if you'd have a look - I don't think I can make much more headway on my own. Jon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
IIS 5.1 and Tomcat 4
I'm trying to get IIS 5.1 and Tomcat 4 to play nicely together. So far I've not got very far. I've got: o isapi_redirect.dll from http://apache.oregonstate.edu/jakarta/tomcat-3/bin/win32/i386/ (That's the only place I could find it, and it took a while to find... should I be worried that it's in the Tomcat 3 directory?) o Registry entries in Jakarta Isapi Redirector\1.0 (which I think are okay) workers.properties and uriworkermap.properties which I think are okay. Only useful bits in them are: [workers.properties] worker.ajp13.port=8009 worker.ajp13.host=localhost worker.ajp13.type=ajp13 worker.ajp13.lbfactor=1 [uriworkermap.properties] default.worker=ajp13 /mobilizer/*=$(default.worker) server.xml has: I was slightly unsure about this - given that I want the first one (note the non-default port, by the way) do I actually need the second? Should I just be able to change teh port in workers.properties? The servlets work fine from the HTTP connector. IIS has a jakarta virtual directory with execute script permission, the ISAPI filter is up (green arrow), but I get: "The specified module could not be found." on my web browser. The catalina log has: 2003-09-19 14:02:42 Ajp13Connector[8009] Opening server socket on all host IP addresses 2003-09-19 14:02:42 Ajp13Connector[8009] Starting background thread 2003-09-19 14:02:42 Ajp13Processor[8009][0] Starting background thread 2003-09-19 14:02:42 Ajp13Processor[8009][1] Starting background thread 2003-09-19 14:02:42 Ajp13Processor[8009][2] Starting background thread 2003-09-19 14:02:42 Ajp13Processor[8009][3] Starting background thread 2003-09-19 14:02:43 Ajp13Processor[8009][4] Starting background thread The localhost log doesn't seem to mention anything in particular. The isapi log has lines such as: [Fri Sep 19 14:04:40 2003] [jk_isapi_plugin.c (626)]: HttpFilterProc started [Fri Sep 19 14:04:40 2003] [jk_isapi_plugin.c (672)]: In HttpFilterProc Virtual Host redirection of /localhost/mobilizer/mobilizer [Fri Sep 19 14:04:40 2003] [jk_uri_worker_map.c (351)]: Into jk_uri_worker_map_t::map_uri_to_worker [Fri Sep 19 14:04:40 2003] [jk_uri_worker_map.c (368)]: Attempting to map URI '/localhost/mobilizer/mobilizer' [Fri Sep 19 14:04:40 2003] [jk_uri_worker_map.c (456)]: jk_uri_worker_map_t::map_uri_to_worker, done without a match [Fri Sep 19 14:04:40 2003] [jk_isapi_plugin.c (678)]: In HttpFilterProc test Default redirection of /mobilizer/mobilizer [Fri Sep 19 14:04:40 2003] [jk_uri_worker_map.c (351)]: Into jk_uri_worker_map_t::map_uri_to_worker [Fri Sep 19 14:04:40 2003] [jk_uri_worker_map.c (368)]: Attempting to map URI '/mobilizer/mobilizer' [Fri Sep 19 14:04:40 2003] [jk_uri_worker_map.c (391)]: jk_uri_worker_map_t::map_uri_to_worker, Found a context match ajp13 -> /mobilizer/ [Fri Sep 19 14:04:40 2003] [jk_isapi_plugin.c (688)]: HttpFilterProc [/mobilizer/mobilizer] is a servlet url - should redirect to ajp13 [Fri Sep 19 14:04:40 2003] [jk_isapi_plugin.c (737)]: HttpFilterProc check if [/mobilizer/mobilizer] is points to the web-inf directory [Fri Sep 19 14:19:23 2003] [jk_isapi_plugin.c (626)]: HttpFilterProc started [Fri Sep 19 14:19:23 2003] [jk_isapi_plugin.c (672)]: In HttpFilterProc Virtual Host redirection of /localhost/mobilizer/mobilizer/ [Fri Sep 19 14:19:23 2003] [jk_uri_worker_map.c (351)]: Into jk_uri_worker_map_t::map_uri_to_worker [Fri Sep 19 14:19:23 2003] [jk_uri_worker_map.c (368)]: Attempting to map URI '/localhost/mobilizer/mobilizer/' [Fri Sep 19 14:19:23 2003] [jk_uri_worker_map.c (456)]: jk_uri_worker_map_t::map_uri_to_worker, done without a match [Fri Sep 19 14:19:23 2003] [jk_isapi_plugin.c (678)]: In HttpFilterProc test Default redirection of /mobilizer/mobilizer/ [Fri Sep 19 14:19:23 2003] [jk_uri_worker_map.c (351)]: Into jk_uri_worker_map_t::map_uri_to_worker [Fri Sep 19 14:19:23 2003] [jk_uri_worker_map.c (368)]: Attempting to map URI '/mobilizer/mobilizer/' [Fri Sep 19 14:19:23 2003] [jk_uri_worker_map.c (391)]: jk_uri_worker_map_t::map_uri_to_worker, Found a context match ajp13 -> /mobilizer/ [Fri Sep 19 14:19:23 2003] [jk_isapi_plugin.c (688)]: HttpFilterProc [/mobilizer/mobilizer/] is a servlet url - should redirect to ajp13 [Fri Sep 19 14:19:23 2003] [jk_isapi_plugin.c (737)]: HttpFilterProc check if [/mobilizer/mobilizer/] is points to the web-inf directory Any clues as to what I'm missing? I haven't worked out the difference between jk and jk2, and which I should be using - I've seen different registry entries available for jk2, but I'd like to know whether or not the above *should* work first - and why (if at all) I should change to use jk2. Any help gratefully received. Jon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
